← ClaudeAtlas

monetization-auditlisted

Use when asked how a project could make money, whether monetization opportunities are being missed, to research pricing or competitors for an existing codebase, or to turn a project into a revenue plan with concrete executable next steps.
succtorlin/monetization-audit · ★ 2 · AI & Automation · score 65
Install: claude install-skill succtorlin/monetization-audit
# Monetization Audit ## Overview Scan what a project actually is, research what its market actually pays for, diff the two, and emit **action specs an agent can execute** — not advice. Core principle: every claim traces to either a file in the repo or a dated source on the internet. Analysis that cites neither is opinion and gets cut. ## When to use - "How can this project make money?" / "What monetization are we missing?" - Pricing, packaging, or competitor research for something that already exists - Turning an audit's findings into work an agent can start immediately When NOT to use: picking which *skill* to productize (use skill-productizer — its 13-forms taxonomy is the vocabulary for Phase 4 here); inventorying personal assets across projects (use productize-real-assets). ## Two modes - **Solo** (default): one agent runs Phases 1–4. Right for a first pass or a bounded question. - **Team** (consulting-grade): the four phases are decomposed into specialist workstreams run by recruited agents, with a mandatory adversarial pass and a real synthesis. Invoke when the user asks for depth ("extensive", "thorough", "like McKinsey/BCG", "recruit a team"), when a solo pass was judged too shallow, or when the findings will drive a real investment decision. Team mode is expensive — each specialist is a full agent run; say so and get the user's go-ahead before dispatching a full engagement. ## Team mode — the engagement model Structure it like a consulting eng