AF skill-generator
Interactive wizard for creating a brand-new OpenClaw skill folder that contains a required SKILL.md file and optional helper scripts. Trigger this skill ONLY when a human user explicitly asks to create a new skill in this conversation, for example: "我想生成一个skill", "帮我创建一个skill", "新建一个skill", "I want to build a skill", "create a skill for X", "turn this workflow into a skill". Do NOT trigger when the message is a routed system message, a request to read or display files, a request about an existing skill, or a follow-up inside an already running skill-generator session.
As a process F 36/100 · Will not run — References files that are not bundled: scripts/*.js, scripts/*.py, scripts/fetch_weather.js
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/*.js - warning
missing-refreference to a missing file: scripts/*.py - warning
missing-refreference to a missing file: scripts/fetch_weather.js - warning
missing-refreference to a missing file: scripts/generate_report.js
Process rating: all ten parameters 36/100
- 0Tools and files. 4 referenced file(s) missing: scripts/*.js, scripts/*.py, scripts/fetch_weather.js
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (skill-generator) differs from the folder (miemie-le-skills)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 72 steps
- 100Execution cost. Instruction body is 2733 tokens
- 100Progress reporting. Reports progress
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (13 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 574: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (21 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.