AC email-and-newsletter
Email and newsletter strategy for creators and brands — the owned-audience layer that social feeds. Use when someone wants to "start/grow a newsletter," "build an email list," "turn followers into subscribers," "should I use Substack/beehiiv/LinkedIn," "repurpose my newsletter into social (or vice versa)," or build the audience layer social can't take away. Runs email (habit) + a web archive (discovery) off the same work and loops content social<->email. Uses the INBOX framework. Reads brand-profile + voice-builder + content-pillars first. WoopSocial does NOT send email — the agent strategizes and drafts, the ESP is external and human-run, WoopSocial publishes only the social side; metrics come from the ESP + GA4, never fabricated; consent + unsubscribe required. Distinct from link-in-bio-and-traffic (capture), cross-platform-repurposing (same-moment), and lead-magnets-and-funnels (the magnet).
Email and newsletter strategy for creators and brands — the owned-audience layer that social feeds.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 56/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1269 tokens
- 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 907: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 9 headings
- +3Step-by-step instructions: 11 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.