AB content-strategy
Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.
Promises to build a content strategy: topic clusters, editorial roadmap, content mix for traffic, authority, and leads. Three files with instructions, no scripts, no critical errors. Quality score 91 out of 100, but process score 75—logic works, reproducibility doesn't. No model runs or sandbox tests on record.
Real value depends on how well the AI grasps your niche. You get a framework, not a guarantee the output beats an hour of your own thinking. Install if you need a starting sketch or a second opinion—treat it as a sparring partner, not a solution.
Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation.
As a process B 75/100 · Nearly there — weak spots: running it twice, progress reporting
The same skill appears in 1 more place: agentic-awesome-skills
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: 2. 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 75/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 133 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2992 tokens
- low 13 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 221: enough signal without eating the budget
- +4Structure: 43 headings
- +3Step-by-step instructions: 133 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.