AC format-flow
Seamless multi-format document conversion toolkit supporting Word ↔ PDF ↔ Markdown conversion, web page to Markdown, text formatting, Excel to JSON, and image processing (compression, format conversion, resizing). Use when user mentions converting documents, extracting text, formatting notes, converting Excel to JSON, or processing images. Keywords: format flow, convert, Word to PDF, Word to Markdown, PDF to Markdown, Markdown to Word, web to Markdown, text formatting, Excel to JSON, image compression, image conversion, image resizing, document conversion, format conversion, extract text, 文档转换, 格式转换, 格式流转, Word转PDF, Word转Markdown, PDF转Markdown, Markdown转Word, 网页转Markdown, 文本格式化, Excel转JSON, 图片压缩, 图片转换, 图片调整.
As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Seamless multi-format document conversion toolkit supporting Word … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 78 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2334 tokens
- 100Running it twice. No mutating operations
- low 12 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)
- -2147 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 717: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 78 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.