AB reson8-activate
The meta-skill that knows its own activation surface. Use this skill whenever the user wants to "activate" a capability, asks "what can you do", wants to chain multiple skills together, needs help finding the right tool for a task, asks about available integrations or connectors, wants to publish to a marketplace, or says "activate", "inventory", "compose", "what tools", "what skills", "what can we use", "show me everything", or "tapestry". Also triggers when another agent (Grok, Gemini) needs to understand what capabilities exist and how to invoke them. This is the Tapestry of Skills — the self-aware orchestration layer.
As a process B 75/100 · Nearly there — weak spots: 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: 5. 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 75/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (reson8-activate) differs from the folder (reson8-activator)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 1327 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +3Description length 629: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.