Systems Lab

Skill library

etrebels/claude-code-growth-os

Publisher description: Claude Code Growth Operating System (OS): Sales, Marketing, Product and Retention as one Revenue system

Catalogue scope: 20 entries at separate source paths.

MIT

Publisher site ↗

Repository health

GitHub’s own figures, read from its REST API. Commit and contributor totals come from the paging header rather than an estimate.

Repository metadata checked 2026-10-12 · skill files extracted 2026-10-12 · published 2026-09-05

Extraction and automated analysis describe the files at the recorded revision. They are not an editorial review or a test of the skills in use.

Stars
21
Commits
147
Last 90 days
25

commits

Contributors
3
Last push
2026-10-03
First commit
2026-05-23

repo created

20 skill entries

  • account-health

    Score a customer's health, start the renewal motion, and flag churn or expansion early. Trigger when the user asks "how's this account doing", "health check", "are we at risk of churn", "is this account ready to expand", or before a renewal or QBR.

    Self-containedInstructions only406 words
  • calendar-followup

    Surface unfinished follow-ups from last week's external meetings. Trigger when the user asks "who do I need to follow up with", "what meetings haven't I followed up on", or as part of the morning briefing ritual.

    Self-containedInstructions only325 words
  • churn-save

    Turn a red/amber account into a recovery play — the real risk, the re-engagement outreach, the renewal-clock timing. Trigger when account-health flags a 🔴/🟡 account, when the user says "save this account", "they're going to churn", "the customer went quiet", "renewal at risk", or right after a RETENTION-RISK line is logged.

    Self-containedInstructions only406 words
  • cold-outreach

    Draft a first-touch cold email or LinkedIn DM. Trigger when the user asks for a cold email, an outreach message, or a first touch to a named prospect.

    Self-containedInstructions only114 words
  • content-repurpose

    Turn one piece of source material into several channel-ready drafts. Trigger when the user asks to repurpose something, "turn this into posts", or "what can I make from this".

    Self-containedInstructions only99 words
  • event-to-pipeline

    Turn a conference, meetup, or event you attend or host into booked calls. Trigger when the user is about to attend or host an event, asks how to "work the room", or names an upcoming conference/meetup.

    Self-containedInstructions only402 words
  • example-skill

    A template skill. Replace it with a task you repeat. Trigger only when the user explicitly asks to run the example skill.

    Self-containedInstructions only92 words
  • expansion-signal

    Work an expansion-ready account into an angle and a clean hand to sales — the second growth motion the funnel forgets. Trigger when account-health flags an EXPANSION-SIGNAL, when a healthy account asks for more unprompted, a second team wants access, or the user says "this account is ready to grow", "expansion play", "upsell", or "land and expand".

    Self-containedInstructions only380 words
  • follow-up

    Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".

    Self-containedInstructions only133 words
  • inbox-digest

    Scan the last 48 hours of unread newsletters, news emails, and blog digests. Summarize what's relevant to your work. Trigger when the user asks "what did I miss", "any interesting newsletters", or as part of the morning briefing ritual.

    Self-containedInstructions only283 words
  • lead-qualify

    Score a lead or opportunity against an ideal-customer-profile fit check. Trigger when the user pastes a lead/company and asks "is this a fit", "should I pursue", or to qualify/score a lead against the ICP.

    Self-containedInstructions only144 words
  • marketing-feedback

    Turn what sales hears in the field into marketing actions. Trigger when a meeting note or call recap surfaces a recurring objection, a competitor mention, the buyer's own language, a missing proof point, or a win/loss reason — or when the user says "log this for marketing", "what should marketing know", or "field intel".

    Self-containedInstructions only341 words
  • meeting-prep

    Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.

    Self-containedInstructions only647 words
  • onboarding-handoff

    Run the Won→onboarding handoff — the seam most teams drop. Trigger when a deal is marked won/closed-won, when the user says "we won X", "hand this off to onboarding", "kick off the new customer", or "onboarding checklist".

    Self-containedInstructions only349 words
  • product-signal

    Route post-sale and field signals into product's roadmap queue, and write the buyer-facing line for anything shipped. Trigger when the user says "what should product hear", "triage the roadmap signals", "route this to product", "feature request", or "what does this feature mean for the buyer".

    Self-containedInstructions only362 words
  • qbr-prep

    Turn a customer's recent calls, adoption signal, and roadmap status into a QBR brief that leads with the outcome they bought. Trigger when a quarterly business review is coming up, before a renewal or value-review call, or when the user says "QBR prep", "build the QBR", "quarterly review for X", or "value review".

    Self-containedInstructions only337 words
  • retention-feedback

    Turn what customer success hears after the sale into product and retention actions. Trigger when an onboarding note, QBR, support thread, or usage review surfaces adoption friction, a churn-risk signal, a feature request that blocks expansion, or a customer who's ready to grow — or when the user says "log this for product", "retention risk", "what's the churn signal", or "post-sale feedback".

    Self-containedInstructions only431 words
  • status-update

    Draft a short status update from recent daily-log entries. Trigger when the user asks for a status update, a weekly update, or "what should I tell my team / manager / board".

    Self-containedInstructions only54 words
  • support-signal

    Cluster a batch of support tickets or threads into ranked product themes, then hand them to product-signal for the roadmap. Trigger when there's a pile of support tickets, or the user says "what are the tickets telling us", "cluster these tickets", "support themes", "top issues this month", or wants raw support volume turned into product feedback.

    Self-containedInstructions only362 words
  • triage

    Triage a list of incoming items into do-now / schedule / delegate / drop. Trigger when the user pastes a list and asks to triage, prioritize, or "what should I do first".

    Self-containedInstructions only67 words

Ask about etrebels/claude-code-growth-os

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Need help setting it up?

This page tells you what etrebels/claude-code-growth-os does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.