Vertical Creator
Domain-knowledge primer for the marketing & creator vertical (creators, newsletter writers, podcasters, course sellers) so architect/pm don't spec naively against incumbents (Substack ~10%, Patreon 8–12%, Kajabi $149+, beehiiv, Buffer/Hootsuite/Later). Supplies the vocabulary, the non-obvious take-rate/red-ocean rules, the entities a real scheduler/analytics/monetization/sponsorship product must model, and the per-product wedge — with sponsorship-crm flagged as the white-space wedge. Applied by architect/pm during spec authoring for any of the four products in this vertical — content-scheduler
Install
npx skills add jeremybrasher/grokbot-skills --skill vertical-creatorgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/vertical-creator ~/.claude/skills/vertical-creatorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Vertical: marketing & creator — undercut the take-rate, own the white space Creators monetize an audience across channels they don't control. Their economics are dominated by **take-rate** (the platform's cut) and by **brand sponsorships** that most creators still manage in spreadsheets. Two of the four products here (scheduling, analytics) sit in **red oceans** owned by entrenched incumbents; one (**sponsorship-crm**) sits in genuine **white space**. Spec against that asymmetry — don't lead with the commodity. ## 1. Domain vocabulary - **CPM (cost per mille)** — ad/sponsor price per 1,000 impressions. The supply side. - **RPM (revenue per mille)** — revenue the creator actually earns per 1,000 views/opens, net of platform cut. RPM < CPM; the gap is fees and unfilled inventory. - **Sponsorship / brand deal** — a brand pays a creator to promote a product. The unit of white-space revenue here. - **Fee model** — how a deal pays: **flat fee** (fixed $ per deliverable), **affiliate** (% of referred sales), or **CPA** (cost-per-action — $ per signup/install). A single deal can mix them (flat + affiliate). - **Deliverables** — the concrete asset(s) owed: posts, stories, dedicated email, video **integration** (a segment inside a longer video), etc. Each has a channel and a due date. - **Usage rights** — whether/how long the brand may reuse the creator's content (e.g. "whitelisting" to run as paid ads). Priced separately; easy to give away by accident.
Details
- Skill name
vertical-creator- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/vertical-creator/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Vertical Creator skill do?
Domain-knowledge primer for the marketing & creator vertical (creators, newsletter writers, podcasters, course sellers) so architect/pm don't spec naively against incumbents (Substack ~10%, Patreon 8–12%, Kajabi $149+, beehiiv, Buffer/Hootsuite/Later). Supplies the vocabulary, the non-obvious take-rate/red-ocean rules, the entities a real scheduler/analytics/monetization/sponsorship product must model, and the per-product wedge — with sponsorship-crm flagged as the white-space wedge. Applied by architect/pm during spec authoring for any of the four products in this vertical — content-scheduler
How do I install the Vertical Creator skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill vertical-creator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vertical Creator popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Vertical Logistics
38jeremybrasher/grokbot-skills
Domain knowledge for the logistics & supply-chain vertical (SMB shipping & inventory) so architect and pm don't spec naively. Covers the vocabulary (TMS vs WMS, multi-carrier rate shopping, dimensional weight, BOL/ASN, lot/batch, reorder point), the non-obvious rules incumbents get right, what a naive build gets wrong, and the entities each of the four products (shipment-tracking, warehouse-lite, route-optimization, po-mgmt) must model. Applied by architect when writing ARCH-{slug}.md and by pm when writing PLAN-{slug}.md for any logistics product.
Unslop
38jeremybrasher/grokbot-skills
Cut AI tells from any writing. Must always apply. Observe required inputs first; HOLD when they are missing rather than guessing.
Accelerator Application
39lionelsimai/claude-skills-collection
Write accelerator applications. TRIGGERS - Use when user needs help with accelerator-application related tasks.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.