agentsclimarketplace

Delegate

Skill nocodework/growth-os/core/skills/delegate

NoCodeWork Growth OS — open-source Growth OS for any AI agent: point it at a business URL, persist USP/UVP/ICP context, run a growth audit (SEO, speed, GEO/AI-visibility, competitors, live GA4/GSC), then delegate to marketing skills. Runs on Claude Code, Codex, Hermes & MCP.

Install
npx -y skills add nocodework/growth-os --skill delegate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Route a growth task to the right skill. Maps a job (get more signups, reduce churn, rank a page, write ads) to Growth OS's native skills first, and — only if the user has a marketing skill pack installed — points to it by reference without copying any of its content. Uses core/knowledge/atomic-skills-map.md. Use when someone runs /growth-os:delegate, says "help me with X growth task," "what should I use for this," or when an audit finding needs an owner.

SKILL.md

4.6 KB, 988 tokens by cl100k_base, as published. Nobody here has run it

delegate

The router. Growth OS does diagnosis and context extremely well, but "growth" is a huge surface — copywriting, paid ads, lifecycle email, pricing, referrals, retention. delegate takes a concrete task and points it at the right executor: a Growth OS native skill when one fits, or an external marketing skill pack by reference when the user has one installed and it's the better tool.

What it does

  • Interprets the growth task and locates it on the AARRR funnel (acquisition, activation, retention, revenue, referral).
  • Looks up the task in core/knowledge/atomic-skills-map.md.
  • Recommends the native Growth OS skill if one covers it.
  • If the task falls outside Growth OS's native set and the user has an external marketing skill pack installed, notes that "a pack you have can handle this" and names the category of capability — never reproducing, quoting, or paraphrasing that pack's content.
  • Passes along the relevant context from the hub so whatever executes the task starts informed.

When to use

  • An audit finding needs action and it's not obvious which skill owns it.
  • The user has a specific growth job and wants the fastest right tool.
  • Someone asks "can Growth OS do X?" — delegate answers honestly (native / via a pack / not covered).

Steps

  1. Clarify the task in one line. "Improve the pricing page's conversion," "get more email signups," "win back churned users." If it's fuzzy, ask one sharpening question.

  2. Place it on the funnel. Which AARRR stage — and which sub-job. This is the lookup key into the skills map.

  3. Look it up in atomic-skills-map.md. The map lists common growth jobs and, for each, the native Growth OS skill (if any) plus a neutral note about delegating to an installed pack.

  4. Recommend, in priority order:

    • a) Native Growth OS skill — if context, audit, geo-audit, geo-content, connect, or dashboard covers it, route there. Growth OS's own house first.
    • b) External marketing pack (by reference only) — if it's a job Growth OS doesn't natively do (write ad variations, build a cold-email sequence, design a paywall, plan an A/B test) and the user has a compatible pack installed, tell them: "This is a job for a dedicated marketing skill pack — if you have one installed, it can take this, and Growth OS will feed it your context." Name the capability type, point to their pack, and stop there. Do not copy, summarize, or restate anything from that pack. Growth OS links; it never redistributes.
    • c) Not covered — if nothing fits, say so plainly rather than forcing a bad match.

  5. Hand off context. Whatever executes the task, make sure it gets the positioning from .agents/product-marketing.md and any relevant audit findings, so it doesn't start cold.

Which adapters / CLI it calls

None directly. delegate is pure routing. It reads core/knowledge/atomic-skills-map.md and the hub, then points at an executor. Any data pulls happen inside the skill it routes to.

How it delegates

That's the whole job. Two lanes:

  • Native — invoke the matching Growth OS skill.
  • External — reference an installed pack without touching its content. Growth OS and marketing packs are designed to sit side by side: Growth OS owns context + diagnosis + GEO + data plumbing; a pack owns deep execution of a given marketing craft. delegate is the seam between them.

Guardrails — licensing, non-negotiable

  • Reference, never redistribute. When pointing at an external pack, Growth OS names the capability and defers to the user's own installed copy. It never bundles, copies, quotes, paraphrases, or reproduces any third-party pack's prompts, skill text, or structure. If a pack isn't installed, Growth OS does not supply its content as a substitute — it says "install a pack for that" or offers the native alternative.
  • Honest coverage. Don't oversell. If Growth OS can't do something natively and the user has no pack, say it's out of scope rather than improvising a weak version.
  • Context flows one way. Growth OS shares the user's own context with the executor; it never pulls content back from a pack into Growth OS's files.

Gives 0 of the 12 instructions most product growth skills give in 988 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 24 of 728, across 15 files
  • define the ideal customer profilein 21 of 728, across 3 files
  • document a rollback plan before deploymentin 21 of 728, across 12 files
  • analyze the codebase to understand the productin 19 of 728, across 1 file
  • ask clarifying questions about the value propositionin 19 of 728, across 1 file
  • search for companies matching the criteriain 19 of 728, across 1 file
  • look for signals of immediate needin 19 of 728, across 1 file
  • assign a fit score from one to tenin 19 of 728, across 1 file
  • identify the target decision maker rolein 19 of 728, across 1 file
  • suggest a personalized contact strategyin 19 of 728, across 1 file
  • provide conversation starters for outreachin 19 of 728, across 1 file
  • format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

  • Clarify the requested growth task in one line
  • Map the clarified task to an AARRR funnel stage
  • Look up the task in the atomic skills map
  • Recommend the native skill if one fits
  • Name the capability category of an external pack
  • Pass product positioning and audit findings to the executor

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.