AB meeting-ops-router
Route meeting notes, transcripts, Feishu docs, wiki pages, or minutes links into concrete execution channels. Use when the user wants post-meeting follow-through, including extracting action items, assigning owners, writing back to Feishu docs, storing tasks in Bitable, sending follow-up messages, creating reminders, or delegating work to same-gateway OpenClaw sessions or sub-agents.
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Concealment
en-hide-from-userSKILL.md:140Instruction to hide actions from the user (negated — the text forbids it)Never silently send external messages or create a large number of records.
negated
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (meeting-ops-router) differs from the folder (meeting-ops-agent)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 73 steps
- 100Execution cost. Instruction body is 1320 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 386: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 73 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.