AC meeting-agenda
This skill should be used when the user provides meeting-related information (title, venue, time, agenda items, participants, etc.) and wants to generate a formatted meeting agenda document. It produces both a Word (.docx) and PDF file following a standardized Chinese government/enterprise meeting agenda format with correct fonts: Heiti for headings, FangSong GB2312 for body text, and Kaiti GB2312 for organizational unit headers.
This skill should be used when the user provides meeting-related information (title, venue, time, agenda items, participants, etc.) and wants to generate a…
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 · 0
✓ No critical or high findings
Files scanned: 4. 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 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (meeting-agenda) differs from the folder (meeting-agenda-tool)
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 30 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 922 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (4 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 433: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.