AC content-pillars
Use to define a brand's content pillars — the 3–5 recurring themes it posts about — the strategic backbone between the brand profile and the content calendar. Run when the user says "content pillars," "content buckets," "what should I post about," "content themes," "content strategy," "pillars," or before planning a batch or calendar. Reads brand-profile first and derives pillars from positioning, point of view, audience, and proof — real ownable themes, never generic "educational / behind-the-scenes / promotional" buckets (those are intents and formats, not pillars). Produces a content-pillars.md that batch-content-plan and the content skills read. Works for any business: B2B, ecommerce, local, personal brand, nonprofit.
Use to define a brand's content pillars — the 3–5 recurring themes it posts about — the strategic backbone between the brand profile and the content calendar.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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: 6. 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
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1539 tokens
- low 12 top-level sections: this looks like several domains in one skill
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 731: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 36 items
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.