BC content-calendar
Plans and writes a week or month of dated social posts (LinkedIn, X, newsletter, Reddit, short video), checked against the saved calendar so topics don't repeat, and queued for approval. Use whenever someone wants a content calendar, a posting schedule, or the next week's or month's posts, even for one launch week.
Plans and writes a week or month of dated social posts (LinkedIn, X, newsletter, Reddit, short video), checked against the saved calendar so topics don't…
As a process C 59/100 · Has gaps — References files that are not bundled: references/brand-voice.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/brand-voice.md
Process rating: all ten parameters 59/100
- 0Tools and files. 1 referenced file(s) missing: references/brand-voice.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 5 branches
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3965 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 316: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.