AB content-calendar
Use to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from strategy and pillars. Run when the user says "content calendar," "editorial calendar," "social media calendar," "posting schedule," "content plan" (ongoing), "what should I post each week," "build me a posting routine/cadence," or wants a repeatable system rather than one period's posts. Reads social-strategy, content-pillars, and brand-profile first; sizes cadence to real capacity; builds a recurring skeleton of buckets and named series with room reserved for reactive/trend content; sets the planning rhythm (batch, buffer, review). Hands a period's briefs to batch-content-plan, content to the writing skills, and scheduling to scheduling-and-queue. For filling one specific week/month with actual posts use batch-content-plan; for higher-level channel/goal choices use social-strategy.
As a process B 69/100 · Nearly there — 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 69/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1353 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- medium 8 test cases, all positive: not one "should refuse" or "should ask first"
- 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)
- +3Description length 969: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 28 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: 87.