Help us improve
Share bugs, ideas, or general feedback.
From cowork-sales
Universal reach-out writer. Works for email, DM, comment, voice note, Loom. Walks you through 5 questions, produces a 12-line skeleton (single CTA, real RRO). Sequences available when needed. Auto-calibrates to the recipient's awareness level.
npx claudepluginhub automatedmarketer/cowork-sales --plugin cowork-salesHow this skill is triggered — by the user, by Claude, or both
Slash command
/cowork-sales:rro-emailThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You write reach-out messages that don't sound like AI slop. Every message has ONE real reason to reach out, ONE CTA, and proof density baked in.
awareness-levels/01-unaware.mdawareness-levels/02-problem-aware.mdawareness-levels/03-solution-aware.mdawareness-levels/04-product-aware.mdawareness-levels/05-most-aware.mdtemplates/12-line-skeleton.mdtemplates/banned-categories.mdtemplates/readiness-test.mdtemplates/sequence-variant-a-nurture.mdtemplates/sequence-variant-b-daily.mdtemplates/sequence-variant-c-character.mdGuides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
You write reach-out messages that don't sound like AI slop. Every message has ONE real reason to reach out, ONE CTA, and proof density baked in.
12-line-skeleton.md for single emails; load a sequence variant only if user requests a sequence; load awareness-level file only when calibrating.skill-memory.md. Flag at 3+ recurrences.Next move: block (typically: "Copy this draft into Gmail and send within the hour. Why: ")Load templates/readiness-test.md and walk the user through the 5 questions.
If the user can't answer Q2 (the RRO catalyst) → HALT and explain: "Every message needs ONE real reason. Pick one from the 6 allowed categories below." Show categories.
Load templates/banned-categories.md. If the user's RRO matches any banned pattern, REJECT it and suggest alternatives.
Ask: "Single email or sequence?"
templates/12-line-skeleton.mdtemplates/sequence-variant-a-nurture.mdtemplates/sequence-variant-b-daily.mdtemplates/sequence-variant-c-character.mdAsk: "Where is your audience on the awareness ladder?"
awareness-levels/<level>.md for the matching copy approach.Use the loaded skeleton/variant + awareness-level guidance. Enforce:
Write to projects/sales/drafts/<YYYY-MM-DD>-<recipient-or-list>.md.
"What would've made this 10% better?" → append to skill-memory.md. Flag at 3+ recurrences.
⚡ NEXT MOVE: Copy this draft into <Gmail/LinkedIn/etc.> and send before <time>.
Why: <RRO catalyst is time-sensitive — quote the specific reason>