skillboss-marketing
B2B/B2C marketing operating system for AI startups. Covers onboarding, customer segmentation, competitor boards, X/Twitter growth, cold email, content planning, and weekly KPI review.
What this skill does
# SkillBoss Marketing Operating System Run growth and GTM work for AI startups with one consistent operating model. This skill is optimized for AI-native products that need positioning, audience mapping, social content, cold outbound, and weekly operating cadence. ## Core Objective Turn vague marketing asks into a repeatable system: 1. classify the customer correctly 2. identify market position and competitors 3. set up the operating stack 4. build a social + outbound motion 5. review metrics weekly and adjust Do not jump straight to content production. Start with classification and operating constraints first. ## Customer Classification Classify the company into one of four buckets before making any plan: | Type | Definition | Primary Motion | |------|------------|----------------| | Outbound to C | China team selling to overseas consumers | X/Twitter + Reddit + Product Hunt | | Outbound to B | China team selling to overseas businesses | Cold email + LinkedIn + case studies | | Silicon Valley to C | Silicon Valley consumer AI startup | Social narrative + product demos + community | | Silicon Valley to B | Silicon Valley B2B AI startup | Founder-led GTM + outbound + events + proof | Then adjust by product type: - `to C`: focus on community, product demos, creator distribution, launch velocity - `to B`: focus on ICP clarity, proof, use cases, meetings, and sales assets - `China outbound`: include infra setup, English profile quality, and credibility bootstrapping - `Silicon Valley local`: assume some GTM basics already exist; move faster into execution ## Required Deliverables For a new client or new project, produce these in order: 1. **Customer classification** - one sentence on who they sell to - one sentence on why buyers care - one sentence on what motion should dominate 2. **Competitor intelligence board** Track at least: - company name - website - founder or main account - X/Twitter followers - community size if relevant - Similarweb traffic estimate if available - content frequency - recent launches or product changes - your note on positioning 3. **Positioning** Output: - current positioning line - problems with it - 3 sharper alternatives - one recommended line 4. **Channel plan** Must choose primary, secondary, and optional channels. 5. **Weekly execution plan** A concrete plan for: - content - outreach - list building - KPI review ## Operating Stack Standard tools: - Notion for operating docs and competitor board - X/Twitter for public narrative - LinkedIn for B2B founder credibility - Google Workspace for outbound email - Calendly for meetings - Typefully or equivalent for post drafting When working through SkillBoss, prefer these APIs: - **Search / market research**: `perplexity/sonar-pro` - **Website and competitor scrape**: `firecrawl/scrape` - **Contact enrichment**: `hunter/domain-search`, `hunter/email-finder`, `hunter/email-verifier` - **Cold email execution**: `aws/send-email` or `skillboss-cold-email` - **Asset generation**: `fal/flux-dev`, `vertex/gemini-3-pro-image-preview` (use SkillBoss Image auto-select) - **Narrative drafting**: `openai/gpt-5`, `claude-4-6-sonnet` ## Twitter / X Strategy Treat X/Twitter as an operating system, not a posting queue. ### Profile requirements - clear founder photo - one-line bio with exact product positioning - link to primary product URL - pinned post with best demo or narrative post - location and identity should reduce trust friction ### Feed training Before content planning: - follow competitors, adjacent builders, target users, and distribution accounts - build lists by: - competitors - potential customers - industry operators - aggressively hide irrelevant content ### Content ratio Default ratio: - 4 parts personal insight - 3 parts market or trend analysis - 2 parts product or customer proof - 1 part direct company promotion Do not default to product ads. Founder trust comes first. ### Reply strategy Focus on replies that create visibility: - sharp joke or contrarian angle - useful summary - concrete question - first-hand operator insight Do not write generic AI-sounding compliments. ## Cold Email Strategy Use for `to B` when buyer identification is clear. ### Rules - find 3-5 contacts per target company - write different angles, not repeated nudges - keep emails short - include one CTA - do not overstuff links - use domain and inbox hygiene seriously ### Sequence 1. email A: problem / positioning angle 2. email B: proof / customer case angle 3. email C: founder or strategic relevance angle Then rotate to the next contact if no response. ### What good output looks like For every outreach batch, produce: - target company - target persona - reason this company fits - personalization hooks - subject line - email body - follow-up angle ## Weekly Review Cadence Every week review: - new followers from relevant people - profile visits - top content by reach and saves - meetings booked - email open and reply rate - number of qualified targets added - competitor moves worth reacting to Output should end with: - what worked - what did not - what to change next week ## Execution Rules When using this skill: 1. Always start by classifying the customer. 2. Never recommend all channels equally. 3. Never generate content before the positioning is stated clearly. 4. Prefer proof, specificity, and audience fit over “viral” language. 5. If data is missing, call it out and request or gather it. ## Output Templates ### 1. GTM Snapshot ```md ## GTM Snapshot - Customer type: - Product category: - Primary audience: - Recommended primary channel: - Recommended secondary channel: - Main positioning risk: - Recommended next action: ``` ### 2. Competitor Board Summary ```md ## Competitor Board Summary | Company | Positioning | Audience | Main channel | Signal worth copying | Signal worth avoiding | |---|---|---|---|---|---| ``` ### 3. Weekly Operating Plan ```md ## Weekly Marketing Plan - Narrative theme: - Posts to publish: - Outbound batch: - Companies to research: - Assets to create: - KPI review block: ``` ## More Capabilities - For full model, image, video, email, and deployment support, see `../skillboss/SKILL.md` - For automated outreach execution, see `../skillboss-cold-email/SKILL.md`
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".