Marketing Os
A complete marketing department in one skill.
Install
npx skills add Yuzzyuk/marketing-os --skill marketing-os -g -a claude-code -y- Repository
- Yuzzyuk/marketing-os566
- Category
- Design
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Mediumabout 2,197 tokens
- Runs scripts
- No, instructions only
What it does
A complete marketing department in one skill. Website and landing-page audits with weighted 0-100 scores, copywriting with panel scoring and AI-slop removal, an 18-tactic ad hook engine, GEO/AEO for getting cited by ChatGPT/Perplexity/AI Overviews, paid-ads creative diagnosis and production briefs, email sequences, LinkedIn/X writing, launch playbooks, positioning and offer design, competitor teardowns, app store optimization, honest analytics and test design. Use for ANY marketing task, audit, write, rewrite, diagnose, score, plan, launch, position, price, analyze, whenever the user mentions marketing, growth, conversion, copy, ads, hooks, CPM, ROAS, SEO, GEO, email, social, landing pages, funnels, launches, competitors, brand, positioning, pricing, or app stores, or says "my landing page sucks", "nobody's converting", "why are my CPMs up", "AI doesn't recommend us", "write me 20 hooks". Route via the table inside; fan out subagents for multi-dimensional work. Not for pure engineering, legal, or finance.
Marketing OS
One skill, fourteen modules, the full surface a working marketer touches. Built by tearing down the most-starred marketing skill repos on GitHub (44K-star collections down to 100-star craft pieces), keeping what worked, and fixing what every one of them got wrong.
Three rules hold across every module, because they are what the existing ecosystem uniformly lacks:
- Score everything. Findings without a number are hard to act on and easy to argue with. Every audit ends in a weighted 0-100.
- Ship artifacts, not advice. Write the replacement headline, the JSON-LD block, the email, the screenshot caption. "Your headline is vague" is worthless; the rewritten headline is the deliverable.
- State what you couldn't determine. Every report ends with an explicit gaps section. A stated gap is credible; a silently filled one destroys the document.
Setup, always do this first
Read brand-context.md if it exists (working directory, .claude/, or .agents/). It holds the product, ICP, positioning, proof, voice and constraints, and it changes nearly every judgement below. If absent: proceed, say the output is un-contextualised, and offer to generate the file from what you learn, brand-context.template.md in this skill is the blank.
Identify the task type, then open ONLY the module file(s) needed. Do not load all references, the routing below exists so you load ~1 file, not 13.
