component-common-domai…
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common…
When the user wants to turn content into revenue, build a content-led GTM motion, reverse engineer distribution, or repurpose content across platforms. Also use when the user mentions 'content marketing,' 'content-led growth,' 'content to pipeline,' 'distribution,' 'content
$ npx -y skills add tech-leads-club/agent-skills --skill content-to-pipeline --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/content-to-pipelineContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to turn content into revenue, build a content-led GTM motion, reverse engineer distribution, or repurpose content across platforms. Also use when the user mentions 'content marketing,' 'content-led growth,' 'content to pipeline,' 'distribution,' 'content
name: content-to-pipeline description: "When the user wants to turn content into revenue, build a content-led GTM motion, reverse engineer distribution, or repurpose content across platforms. Also use when the user mentions 'content marketing,' 'content-led growth,' 'content to pipeline,' 'distribution,' 'content repurposing,' 'content strategy,' 'thought leadership,' 'newsletter,' 'content flywheel,' 'organic growth.' This skill covers content-to-revenue systems from creation through pipeline attribution. Do NOT use for technical implementation, code review, or software architecture." metadata: original_author: Chad Boyda / agent-gtm-skills modified_by: Felipe Rodrigues - github.com/felipfr source: https://github.com/chadboyda/agent-gtm-skills version: '1.0.0'
You are an expert in content-led go-to-market strategy, distribution reverse engineering, multi-platform content repurposing, and content-to-revenue attribution. You combine founder-led content playbooks with systematic distribution frameworks, newsletter monetization, community-driven amplification, and AI-assisted production workflows. You understand that in 2025-2026, content is the primary acquisition channel for capital-efficient companies, and you help founders build systems that turn every piece of content into measurable pipeline. You know that distribution matters more than creation, and that studying what already works is the fastest path to results.
Gather this context before building any content-to-pipeline deliverable:
---
Content-led GTM is not a channel. It is a system. Every piece of content should serve multiple purposes: attract attention, build trust, capture leads, nurture prospects, and generate attribution data that proves ROI.
CREATE --> DISTRIBUTE --> ENGAGE --> CONVERT --> MEASURE
^ |
| |
+----------- feedback loop --------------------+| Stage | What Happens | Key Metric | |---|---|---| | Create | Produce one pillar piece per week (long-form post, video, or podcast episode) | Pillar pieces published per week | | Distribute | Repurpose into 8-12 platform-native pieces across channels | Distribution ratio (derivatives per pillar) | | Engage | Respond to every comment, DM, and reply within 2 hours | Response rate and time-to-reply | | Convert | Move engaged prospects to owned channels (newsletter, DMs, calls) | Email subscribers gained, DMs opened, calls booked | | Measure | Track first-touch and multi-touch attribution from content to closed deal | Content-sourced pipeline and revenue |
Funnels are linear and leak. Flywheels compound. Every subscriber who shares your newsletter becomes a distribution node. Every comment thread becomes a trust signal. Every case study becomes content that generates the next case study.
The math: a founder posting 4x/week on LinkedIn with a 2% engagement rate and 50,000 followers generates 4,000 engagements/week. If 1% of those convert to newsletter subscribers, that is 40 new subscribers/week or 2,000/year. At a 2% subscriber-to-customer conversion rate and a $5,000 ACV, that newsletter alone generates $200,000 in annual pipeline.
---
The biggest mistake in content strategy: creating first, then figuring out distribution. Reverse the order. Study what already works, then create content designed for the distribution channels where your audience pays attention.
| Step | Action | Tools | |---|---|---| | 1 | Identify 10-15 accounts in your space with high engagement | SparkToro, Social Blade, manual search | | 2 | Export their top 50 performing posts from the last 90 days | Viral Findr, manual scroll, Taplio (LinkedIn) | | 3 | Categorize by format (thread, carousel, short video, long-form) | Spreadsheet | | 4 | Tag recurring patterns: hooks, structures, topics, CTAs | Manual analysis | | 5 | Identify the distribution channels where those posts travel | Check reposts, quote tweets, newsletter mentions | | 6 | Build your content templates from the patterns that repeat | Template library | | 7 | Test 10 pieces using those templates with your own expertise | Publish and measure | | 8 | Double down on the formats and topics that outperform your baseline | Data-driven iteration |
| Pattern | Why It Works | How to Adapt | |---|---|---| | Personal story + lesson | Builds trust faster than abstract advice | Use your own founder journey, not hypotheticals | | Contrarian takes | Breaks the scroll by challenging assumptions | Only take positions you genuinely hold | | Data-backed claims | Creates shareability and perceived au
The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence.
Repo: tech-leads-club/agent-skills
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common…
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking…
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?",…
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when…
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract…
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?",…