AB scheduling-and-queue
Use to schedule, queue, or publish FINISHED social media posts to the user's connected accounts through WoopSocial. This is a BRIDGE skill — it turns ready content into real scheduled or published posts, the step that separates advice from action. Run when the user says "schedule this," "queue these," "post this," "publish to my channels," "add to my calendar," "schedule for [time]," "fan this out to all platforms," or right after a content skill has produced posts that are ready to go out. ALWAYS confirms before scheduling or publishing. If WoopSocial isn't connected, it produces a ready-to-use schedule and explains how to connect — it never pretends to post. It does NOT write content (use the content skills) or report analytics (WoopSocial has no analytics surface yet).
Use to schedule, queue, or publish FINISHED social media posts to the user's connected accounts through WoopSocial.
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. 27 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 42 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1680 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- medium 10 test cases, all positive: not one "should refuse" or "should ask first"
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
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 782: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 42 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: 90.