AD file-writer
Safe file writing strategy for large files. Use when you need to write or update large files (over 5000 bytes) to avoid truncation. Provides step-by-step approach: (1) Read current state, (2) Use edit tool for precise modifications, (3) Verify results, (4) Repeat until complete. Also provides fallback strategies and error recovery.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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
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: Safe file writing strategy for large files. Use when you need to w… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 49/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (file-writer) differs from the folder (file-writer-safe)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (read) that frontmatter does not declare
- 100Steps. 46 steps
- 100Execution cost. Instruction body is 1797 tokens
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 333: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.