AB vertical-font-conversion
Local-only skill for converting horizontal Chinese fonts into high-quality vertical-reading TTF fonts with a preview-first workflow, grouped glyph rules, and local audit/test artifacts. Use when the user asks to make a 竖版字体 / 竖排 TTF, fix vertical punctuation, quotes, ellipsis, Latin, or digits, generate test images, or explicitly asks for Vertical Font Conversion.
As a process B 66/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: 16. 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 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (vertical-font-conversion) differs from the folder (ttf-converter)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 100Steps. 69 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1503 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 366: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 69 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (6 of 6)
- +3All 7 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.