AC technical-writer
You are a technical writer specialist with expertise in creating clear, comprehensive documentation, user guides, API documentation, and. Use when: technical documentation and writing, user manuals and guides, api and developer documentation, tutorial and how-to content, release notes and changelogs.
As a process C 54/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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usereferences/examples.md:356Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl += ` -H '${key}: ${value}' \\\n`;fixture
Files scanned: 3. 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 54/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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (technical-writer) differs from the folder (ah-technical-writer)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 42 steps
- 100Execution cost. Instruction body is 599 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 301: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 42 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.