Imported from recoupable/skills (
skills/recoup-internal-consulting-content-drafter/SKILL.md). Install upstream withnpx skills add recoupable/skills --skill recoup-internal-consulting-content-drafter. Copyright stays with the author.
Consulting Content Drafter
Workspace: use the selected project and its AGENTS.md; keep existing entity folders and
Reality headings. Business paths below are relative to that project. Bundled resources are relative
to this installed skill; sibling capabilities resolve by their installed names. Never search another
private checkout for missing inputs. Use workspace identity, audience, pricing, and DESIGN.md fonts.
Steps
- Take the signal (from
signals/) — read itssource/relatedand traverse to the raw for context. - Ground research-derived drafts (pull the wiki). If the idea cites
[[wiki pages]](it came fromrecoup-internal-consulting-research-miner) or the topic is agent/skill/AI-engineering-shaped, followintegrations/research/AGENTS.mdto read the relevant whole wiki pages (incl.## What we'd steal) and pull concrete, cited specifics to build the draft on — carry the[[citations]]so every claim stays traceable. Out-of-domain topic? Skip this — the wiki is silent on generic app/business, so don't force it. - Choose a clear title naming the subject and reader benefit. Use numbers only when supported; no mandatory headline formula.
- Choose the structure that fits the material: essay, briefing, demonstration, interview or Q&A. AIDA is optional. A newsletter can include industry interpretation, useful product developments, field notes and reader questions without forcing every item into a sales case study.
- Place it on the specificity ladder (generic → category → specific → targeted) and match it to the business stage.
- Save the draft to
content/03-drafts/with a clear title; note the target audience (IC vs. leadership).
Output: a draft ready for review. Sources: Ch. 5 + (for agent/skill topics) the research wiki via integrations/research/AGENTS.md.
Newsletter and distribution work
Read the selected workspace’s approved publishing system and current status through its AGENTS.md before drafting. Keep private strategy and customer proof in that workspace, not in this public skill.
Treat a newsletter as one publication with channel variants. Preserve its core value across email and native newsletter editions; adapt formatting and the next action for the audience. A blog is a durable reference, and a feed post is a standalone discovery piece. Neither automatically requires another email. Use one primary action without banning useful source links. Human-review discussion is conditional on the topic, not a required section.
Keep editorial broadcasts separate from welcome/sales sequences and customer adoption messages. CRM membership or a social subscription is not email consent. Resolve active subscriptions and suppressions before dispatch; never automatically enroll scraped contacts or reset an unsubscribe. Stop redundant acquisition pitches for current customers.
Record edition ID, audience, source evidence, approved claims, primary action/destination, per-channel review and release state, live URL or send ID, and follow-up owner. Verify destination and fulfillment before release. Track qualified responses and customer outcomes separately from audience growth. A draft, API acceptance and delivered message are different states. Existing authorization boundaries still apply.
