Genesys Newsletter

Skill of the Week Newsletter

Write and publish the weekly "Skill of the Week" newsletter for Genesys Growth. Each edition features one Claude Code skill with a deep-dive article explaining the methodology, a before/after ASCII chart for Carbon.now.sh formatting, and a companion LinkedIn post. The featured skill publishes to the public genesys-skills repo BEFORE drafting, so the CTA URL is live when the article needs it.

For the full process (selection / publish / draft / charts / LinkedIn / Notion / output / Substack draft) → the premium reference.

Doctrine inherited (Step 7 — 0626 rollout, locked 2026-06-04)

Output complies with output-tenets.md, output-simplicity.md, ai-speak-anti-patterns.md. Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]].

Refinements applied: R1 (newsletter is end-customer-facing — sources convert to inline links), R2 (newsletter + LinkedIn post + ASCII chart ship as one multi-asset deliverable with toggles), R3 (skill-feature framing capability-led), R5 (newsletter article opener anchors the LinkedIn post verbatim), R6 (newsletter close → sign-up to Genesys mailing primary, GTM-E cohort as fallback), R9 (verb-led section headings).

Process at a glance

┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Phase 1 │───▶│ Phase 1b │───▶│ Phase 2 │───▶│ Phase 3 │
│ Skill │ │ Public │ │ Newsletter │ │ ASCII │
│ Selection │ │ Repo Pub. │ │ Draft │ │ Charts │
└─────────────┘ └─────────────┘ └─────────────┘ └──────┬──────┘
                                                                │
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌──────▼──────┐
│ Phase 7 │◀───│ Phase 6 │◀───│ Phase 5 │◀───│ Phase 4 │
│ Substack │ │ Output + │ │ Notion │ │ LinkedIn │
│ Draft ⌥ │ │ Tracker │ │ Publish │ │ Post │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
                    ⌥ = post-approval only — Matteo presses send

Triggers

Invoke when user says:

• "skill of the week"
• "write newsletter for [skill]"
• "next newsletter"
• "Genesys newsletter"

Do NOT invoke when:

• User wants GTM Engineer Pulse → use /gtme-pulse
• User wants a generic newsletter on a topic → write directly
• User wants only a LinkedIn post about a skill → use /linkedin-expert-posts

Voice & quality rules

Worked-example doctrine ("See it in action")

1. First preference — self-applied. If the skill can plausibly run on Genesys's own business or workspace (most can), write the example as "I ran this on my own X" — the audit-on-myself shape (C23 ran /level on the workspace; C24 ran /win-loss on Genesys's own client book). Source real patterns from the matching projects/genesys/{folder} locked outputs when they exist.
2. Confidentiality gate. Public content never names clients, prospects, people, or deal values, and never reproduces verbatim client quotes — generalize to role/stage shapes ("a client", "a funding cycle", "their first in-house hire"). The lesson and the process are shareable; identities and quotes are not.
3. Fallback. A fictional company clearly framed as illustrative, or a named public B2B SaaS company — but never present invented numbers as real results.

Anti-Hallucination Guardrails

1. Use real, named B2B SaaS examples — concrete data points, specific findings. No generic "a typical company" framing.
2. Time estimates must be realistic — don't inflate manual-process times to make the skill look better.
3. GitHub URLs must resolve — verify the SKILL.md path in .claude/skills/[category]/[skill-name]/SKILL.md.
4. No invented Slack messages — the actual Slack notification is sent via the Slack MCP, not transcribed.

Integration with Other Skills

Cloud routine

The weekly cadence runs via a cloud Routine — see .claude/automation/skill-newsletter/. The routine's prompt body is at prompt.md in that folder; manual-registration handoff at REGISTER-IN-CLOUD-UI.md.

The routine (v2, June 2026) runs the same pipeline as this SKILL.md — publish-first, both charts, Notion publish — under one framing rule: autonomous production, human-gated publication. Matteo is the final reviewer and judge; the routine ships review-ready drafts to Notion with run-linked Slack + email notifications, and the newsletter send + LinkedIn post wait for his approval (the GitHub skill publish stays autonomous behind the public-repo-publish cleaning gates). Phase 7 (Substack draft) is manual-session only — the cloud routine has no browser. Edit prompt.md first when tuning the routine, then re-paste into the cloud UI — the disk edit alone changes nothing live.

Final ship gate

Run /premortem --output before ship. See /premortem skill for the 5 execution domains (will-it-resonate / will-it-convert / will-it-stay-on-brand / will-stakeholder-push-back / will-it-degrade-over-time) and output template.

Trivial-case escape: ## Premortem\nNo failure modes — trivial change satisfies the contract for genuinely trivial outputs.

Persuasion & stickiness pass

Output complies with persuasion-and-stickiness.md — Cialdini's 7 persuasion levers + Heath's SUCCESs. Deploy the 1-2 Cialdini levers that fit the reader's barrier (never all seven; every lever must be TRUE), run the SUCCESs diagnostic (Simple / Unexpected / Concrete / Credible / Emotional / Stories) over the near-final draft, then the rule's pre-ship gate.