content-to-pipeline
# Content-to-Pipeline This Claude Code skill helps founders and marketers design systems that convert content into measurable revenue by mapping distribution channels, reverse-engineering successful content strategies, and repurposing assets across platforms. Use it when building content-led go-to-market strategies, establishing newsletters, planning organic growth, or connecting content creation to pipeline attribution. The skill covers the full content flywheel from creation through measurement and explicitly excludes technical implementation and code review.
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/content-to-pipeline && cp -r /tmp/content-to-pipeline/packages/skills-catalog/skills/(gtm)/content-to-pipeline ~/.claude/skills/content-to-pipelineSKILL.md
# Content-to-Pipeline: Turning Content Into Revenue
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.
## Before Starting
Gather this context before building any content-to-pipeline deliverable:
- What does the business sell, and who is the buyer? Get the core offer, price range, and the job title of the person who signs.
- What content exists today? Ask for volume (posts/week), platforms, and engagement baselines.
- What is the current content-to-revenue path? How do strangers become customers? Map every step.
- Which platform drives the most pipeline today? If unknown, flag measurement as a prerequisite.
- What is the founder's content comfort level? Video, writing, audio, or a mix. This determines the pillar format.
- Is there a newsletter? If yes, get subscriber count, open rate, and click rate. If no, flag as a high-priority gap.
- What tools are in the stack? CRM, email platform, scheduling tools, analytics.
- How much time per week can the founder dedicate to content? This caps the system design.
- What does the competitive content landscape look like? Who in the space creates content that generates visible engagement?
- Is there a community (Slack, Discord, Circle, or similar)? Communities are distribution multipliers.
---
## 1. The Content Flywheel
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.
### The Five-Stage Flywheel
```
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 |
### Why Flywheels Beat Funnels
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.
---
## 2. Distribution Reverse Engineering
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.
### The Reverse Engineering Process
| 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 |
### What to Look For in Top-Performing Content
| 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 authority | Pull from your product data, customer results, or industry reports |
| Step-by-step frameworks | High save rate because of perceived utility | Turn your actual processes into numbered frameworks |
| Before/after transformations | Visual proof of value | Use customer screenshots, metric changes, workflow comparisons |
### Audience Research Stack
| Tool | What It Reveals | Cost |
|---|---|---|
| SparkToro | Which accounts, podcasts, and sites your audience follows | Free tier available |
| Social Blade | Growth trends for competitor accounts (anomalies signal viral content) | Free |
| Viral Findr | Aggregated top-performing content by account | Paid |
| Taplio | LinkedIn-specific analytics and content discovery | Paid |
| X Advanced Search | Filter by engagement threshAudit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).