AC content-calendar
Content strategy, planning, and calendar creation for any business or creator. Use when asked to build a content calendar, plan social media posts, create a content strategy, generate post ideas, schedule content across platforms, repurpose existing content, build a 30/60/90 day content plan, or create platform-specific content frameworks. Triggers on phrases like "content calendar", "content strategy", "social media plan", "post ideas", "content schedule", "30 day content plan", "what should I post", "content for LinkedIn", "repurpose content", "editorial calendar", "content pillars".
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 · 0
✓ No critical or high findings
Files scanned: 5. 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 57/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. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (content-calendar) differs from the folder (content-calendar-x)
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 27 steps
- 100Execution cost. Instruction body is 550 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
- +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
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +3Description length 592: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 27 items
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.