BC meetings
Plan, organize, facilitate, and document meetings and relationship-sensitive one-on-ones, including invitees, decision processes, proactive accessibility, private preference memory, agreed actions, and follow-through. Use for the meeting lifecycle or deciding whether to meet; do not substitute for formal performance procedures, specialist incident response, therapy, or memo writing.
Plan, organize, facilitate, and document meetings and relationship-sensitive one-on-ones, including invitees, decision processes, proactive accessibility…
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 12. 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 56/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1901 tokens
- low No test case covers injection arriving through data
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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 385: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 9 items
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.