AC writing-style-and-tone
The writing-craft skill — style and tone as applied technique: rhythm, specificity, tone modulation, and the edit passes that make writing read as human. Use when someone's posts "sound like ChatGPT," a draft needs a style edit, they ask how to write differently per platform or moment without losing the brand voice, writing is grammatically perfect but exhausting, a manager wants em dashes banned or detector scores chased, or any AI-assisted draft needs its mandatory quality pass. Uses the STYLE framework. Reads voice-builder + brand-profile + the format skill first. Tells must be read as a cluster with judgment — no single marker proves AI, and detectors misflag real writers; the winning move is substance so owned the question never arises. Voice is identity; tone is register. The agent drafts; the HUMAN supplies lived specifics and final say; never invents anecdotes or staged typos. Distinct from voice-builder, hook-writer, the format skills, and content-research-and-sourcing.
The writing-craft skill — style and tone as applied technique: rhythm, specificity, tone modulation, and the edit passes that make writing read as human.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 1. 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 56/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. 4 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1820 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low No test case covers injection arriving through data
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)
- +3Description length 993: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 9 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.