AC engagement-routine
Use to design a sustainable engagement routine — the operating system that turns the engagement craft into a daily/weekly habit. Run when the user asks how to keep up with comments/DMs, how much time to spend engaging, when to engage, how to build an engagement habit/system/cadence, or how to engage without burning out. Reads brand-profile/social-strategy. Covers time-boxed daily/weekly engagement windows built around the golden hour after posting, triage order, mapping engagement to a goal, and anti-burnout boundaries. The flywheel: batch and schedule content (scheduling-and-queue, batch-content-plan) to free the time, then spend it engaging. Advisory and honest — WoopSocial has no comment/DM/inbox surface and no analytics, so the human engages in-app and the agent drafts via reply-and-comment-writer; never automates or fakes engagement. Pairs with reply-and-comment-writer (the craft), the growth skills, community-management, and crisis-and-moderation.
Use to design a sustainable engagement routine — the operating system that turns the engagement craft into a daily/weekly habit.
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. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1254 tokens
- low 10 top-level sections: this looks like several domains in one skill
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 967: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Structure: 11 headings
- +3Step-by-step instructions: 21 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: 82.