AC batch-content-plan
Use to plan and produce a full batch of social media content for a period — a week or a month — in one session: strategically balanced, on-brand, mapped to a calendar, and ready to schedule. Run when the user says "plan my content," "a month of posts," "batch my content," "plan the week," "fill my calendar," or wants many posts planned at once in one sitting. Reads brand-profile, voice, and content-pillars first, and produces a brief for each post that the content skills (caption-writer, reels-script, hook-writer) execute. As a BRIDGE skill it then confirms and hands the batch to scheduling-and-queue. Builds a balanced mix — never all-promotion — matched to the user's real capacity. Suggests cadence but does not claim analytics-based timing (WoopSocial has no analytics surface yet). For the ongoing recurring system — which pillars/formats post on which days, the living "content calendar" — use content-calendar; this skill fills one specific period of that system with actual post briefs.
Use to plan and produce a full batch of social media content for a period — a week or a month — in one session: strategically balanced, on-brand, mapped to a…
As a process C 62/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 62/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. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1590 tokens
- 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 1001: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 35 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.