CC handdraw-style-prompter
Turn a 001–365 hand-drawn and realistic style number and image theme into bilingual prompts, using model capability data to decide when core traits and a numbered reference image are required.
Turn a 001–365 hand-drawn and realistic style number and image theme into bilingual prompts, using model capability data to decide when core traits and a…
As a process C 61/100 · Has gaps — References files that are not bundled: references/model_capabilities.json, references/styles.json
The same skill appears in 1 more place: handraw-style
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5343 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/model_capabilities.json - warning
missing-refreference to a missing file: references/styles.json
Process rating: all ten parameters 61/100
- 0Tools and files. 2 referenced file(s) missing: references/model_capabilities.json, references/styles.json
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 10 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5343 tokens
- 100Steps. 75 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 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)
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 75 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.