AB skill_hunter
ALWAYS invoke this skill FIRST, BEFORE writing any code or taking any implementation step, whenever the user asks to "write", "build", "create", "implement", "make", "set up", "scaffold", "generate", "scrape", "parse", "convert", "deploy", "automate", "integrate", or "extract" anything. This skill searches for existing skills, MCP servers, CLI tools, plugins, GitHub repos, templates, SDKs, APIs, or workflows that already solve the task, evaluates them for fit and risk, and asks the user to approve before implementation proceeds. Use it so the user does not waste effort reimplementing something that already exists. Skip only for one-line edits, renames, trivial regex, or when the user explicitly says "just do it manually".
As a process B 70/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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (skill_hunter) differs from the folder (openclaw-skill-hunter)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 35 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 987 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +3Description length 731: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.