gtm-metrics
When the user wants to define GTM metrics, build a metrics dashboard, measure pipeline efficiency, or track AI product performance. Also use when the user mentions 'GTM metrics,' 'revenue latency,' 'pipeline metrics,' 'TTFV,' 'time-to-first-value,' 'data health,' 'attribution,' 'conversion rate,' 'CAC,' 'LTV,' 'NRR,' 'GTM dashboard,' 'magic number,' 'pipeline velocity,' or 'funnel metrics.' This skill covers GTM measurement from metric selection through dashboard design, including AI-specific cost metrics, attribution models, and weekly review cadences. Do NOT use for technical implementation, code review, or software architecture.
Best use case
gtm-metrics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to define GTM metrics, build a metrics dashboard, measure pipeline efficiency, or track AI product performance. Also use when the user mentions 'GTM metrics,' 'revenue latency,' 'pipeline metrics,' 'TTFV,' 'time-to-first-value,' 'data health,' 'attribution,' 'conversion rate,' 'CAC,' 'LTV,' 'NRR,' 'GTM dashboard,' 'magic number,' 'pipeline velocity,' or 'funnel metrics.' This skill covers GTM measurement from metric selection through dashboard design, including AI-specific cost metrics, attribution models, and weekly review cadences. Do NOT use for technical implementation, code review, or software architecture.
Teams using gtm-metrics should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gtm-metrics/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gtm-metrics Compares
| Feature / Agent | gtm-metrics | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to define GTM metrics, build a metrics dashboard, measure pipeline efficiency, or track AI product performance. Also use when the user mentions 'GTM metrics,' 'revenue latency,' 'pipeline metrics,' 'TTFV,' 'time-to-first-value,' 'data health,' 'attribution,' 'conversion rate,' 'CAC,' 'LTV,' 'NRR,' 'GTM dashboard,' 'magic number,' 'pipeline velocity,' or 'funnel metrics.' This skill covers GTM measurement from metric selection through dashboard design, including AI-specific cost metrics, attribution models, and weekly review cadences. Do NOT use for technical implementation, code review, or software architecture.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# GTM Metrics, Dashboards & Measurement for AI Products
You are an expert in GTM measurement, dashboard architecture, and performance analytics for AI-native products. You understand the critical differences between traditional SaaS metrics and AI product metrics, including usage-based consumption tracking, AI cost-of-revenue dynamics, and outcome-based pricing measurement. You help founders and revenue leaders select the right metrics, build actionable dashboards, design attribution models, and run weekly review cadences that drive decisions. You know that the median B2B SaaS growth rate has settled to 26% in 2025-2026 while CAC has risen 14% to $2.00 per new ARR dollar, making measurement discipline the difference between efficient growth and cash burn.
## Before Starting
Gather this context before building any metrics framework, dashboard, or measurement plan:
- What is the current sales motion? PLG, sales-led, agent-led, or hybrid.
- What is the pricing model? Per-seat, usage-based, outcome-based, or hybrid.
- What is the current ARR or MRR? Stage determines which benchmarks apply.
- What CRM and data tools are in use? HubSpot, Salesforce, Attio, or spreadsheets.
- What analytics/BI tools are available? Metabase, Looker, Mode, or Google Sheets.
- How many reps or GTM team members exist? Solo founder vs. team of 50 require different metric depth.
- What does the buyer journey look like today? Touches, average sales cycle, primary channels.
- Is there a weekly review cadence in place? If yes, what gets reviewed and by whom.
---
## 1. Core GTM Metrics Dashboard
### Revenue Metrics
| Metric | Definition | How to Calculate | Target |
|---|---|---|---|
| ARR / MRR | Recurring revenue | Sum of active subscription revenue | Growth rate benchmarks below |
| Net New ARR | New minus churned | New ARR + Expansion - Churned ARR | Positive every quarter |
| Revenue Latency | Days from first signal to closed deal | Median days first-touch to closed-won | <30d SMB, <90d mid-market, <180d enterprise |
| Expansion Revenue % | New ARR from existing customers | Expansion ARR / Total New ARR | >40% at scale ($50M+ ARR companies ~60%) |
### Efficiency Metrics
| Metric | How to Calculate | Target |
|---|---|---|
| CAC | Total S&M spend / New customers | Varies by segment |
| CAC Payback | CAC / (ARR per customer * Gross Margin) | <8 months (median 8.6; top performers 5-7) |
| Magic Number | Net New ARR (qtr) / S&M Spend (prior qtr) | >0.75 efficient, >1.0 excellent, <0.5 red flag |
| LTV:CAC Ratio | (ARPA * Margin * Lifetime) / CAC | >3:1 healthy, >5:1 may be under-investing |
| Burn Multiple | Net Burn / Net New ARR | <2x good, <1x excellent, >3x concerning |
### Pipeline Metrics
| Metric | How to Calculate | Target |
|---|---|---|
| Pipeline Coverage | Pipeline value / Period quota | 3-4x sales-led, 2-3x PLG |
| Pipeline Velocity | (Qualified Opps * Deal Size * Win Rate) / Cycle Length | Increasing QoQ |
| Pipeline per Rep | Total pipeline / Quota-carrying reps | Track trend, not absolute |
| Slippage Rate | Deals moved out / Total deals in forecast | <15% weekly |
### Retention Metrics
| Metric | How to Calculate | Target |
|---|---|---|
| NRR | (Start MRR + Expansion - Contraction - Churn) / Start MRR | >106% median; >120% best-in-class |
| GRR | (Start MRR - Contraction - Churn) / Start MRR | >90%; >94% at scale |
| Logo Churn | Customers lost / Customers at start | <2% monthly SMB, <1% mid-market |
| TTFV | Median time from signup to first value event | <15 min self-serve, <1 day sales-led |
### NRR Benchmarks by Stage
| ARR Band | Median NRR | Top Quartile | Notes |
|---|---|---|---|
| $1-3M | ~90% | 94% | Focus on finding high-retention segments |
| $3-15M | ~95% | 99% | Expansion motions starting |
| $15-30M | ~100% | 105%+ | Expansion should offset churn |
| $50-100M | ~110% | 120%+ | Expansion revenue exceeds new logos |
| $100M+ | ~115% | 130%+ | Aggressive expansion expected |
### Growth Rate Benchmarks
| ARR Band | Median Growth | Top Quartile |
|---|---|---|
| <$1M | 100%+ | 200%+ |
| $1-5M | 80-100% | 150%+ |
| $5-20M | 50-80% | 100%+ |
| $20-50M | 30-50% | 70%+ |
| $100M+ | 20-30% | 40%+ |
---
## 2. Funnel Metrics by GTM Motion
### PLG Funnel
```
Visitor --> Signup (3-5%) --> Activation (30-40%) --> Conversion (5-8%) --> Expansion (NRR 110-120%)
```
PLG-specific metrics: PQL conversion rate, time-to-activation (<15 min target), feature adoption breadth (core features used in first 14 days), viral coefficient (>0.3 target).
### Sales-Led Funnel
```
Signal --> Outreach (3-5% reply) --> Meeting (50%) --> Demo (60%) --> Pilot (40%) --> Close (30%)
```
Sales-led specific: ACV trend, sales cycle length (median days), win rate by segment, pipeline created per rep per month, quota attainment distribution.
### Agent-Led Funnel (AI SDR)
```
Signal --> AI Qualification (10-15%) --> Human Meeting (50%) --> Close (35%)
```
Agent-led specific: cost per meeting booked, cost per qualified lead, AI outreach ROI (revenue from AI pipeline / AI cost), send-to-reply ratio, human-to-AI leverage ratio.
---
## 3. AI Product-Specific Metrics
AI products carry cost structures that traditional SaaS metrics miss. These supplementary metrics are essential for AI-native businesses.
### AI Cost Metrics
| Metric | How to Calculate | Target |
|---|---|---|
| AI Cost of Revenue | Inference + compute cost / Revenue | <20% of revenue |
| Cost per AI Action | Total AI compute / Actions generated | Decreasing over time |
| ROAI | AI-attributed revenue / (Inference + compute overhead) | >10x for high performers |
| Gross Margin after AI | (Revenue - COGS - AI compute) / Revenue | >70% (vs. ~80% pure SaaS) |
### Usage-Based Pricing Metrics
42% of SaaS companies use consumption-based pricing in 2025 (up from 29% in 2023). When pricing is usage-based, supplement ARR metrics with:
| Metric | Why It Matters |
|---|---|
| Committed vs. Consumed ARR | Gap indicates pricing misalignment or under-adoption |
| Usage Growth Rate | Leading indicator of expansion revenue |
| Overage Frequency | Signals pricing tier design quality |
| Unit Economics per Consumption Unit | Revenue minus cost per unit; must be positive and improving |
| NRR by Cohort (usage-based only) | Separates usage-driven expansion from seat expansion |
### SaaS vs. AI Product Metrics Differences
| SaaS Metric | AI Difference | Additional AI Metric |
|---|---|---|
| Gross margin (~80%) | AI inference lowers to 60-75% | Track AI cost of revenue separately |
| DAU/MAU | Usage is task-driven, not session-driven | Task completion rate, actions per session |
| Feature adoption | AI features are singular and deep | Outcome success rate per AI action |
| Time-on-platform | Less time can mean more value | Time-saved-per-task |
| Per-seat revenue | Consumption pricing varies by user | Revenue per consumption unit |
---
## 4. Data Health Scoring
Bad CRM data makes every other metric unreliable. Quantify data trustworthiness before trusting pipeline reports.
### Data Health Score
```
Data Health Score = (Completeness * 0.35) + (Accuracy * 0.30) + (Recency * 0.20) + (Consistency * 0.15)
```
| Component | Weight | What It Measures |
|---|---|---|
| Completeness | 35% | % of required fields populated per record |
| Accuracy | 30% | % of data points verified against enrichment sources |
| Recency | 20% | % of records updated within 90 days |
| Consistency | 15% | % of records matching format standards |
### Health Score Targets
| Score | Grade | Action |
|---|---|---|
| 90-100% | A | Maintain current enrichment cadence |
| 80-89% | B | Schedule enrichment refresh for lowest-scoring segments |
| 70-79% | C | Pipeline metrics may be unreliable; run enrichment sprint |
| Below 70% | F | Stop trusting pipeline reports; full data cleanup required |
B2B data decays at 2.1% monthly on average. Required enrichment refresh cadence: contact email/phone every 90 days, firmographics every 90 days, intent signals weekly or real-time, ICP scores recalculated on any underlying data refresh.
---
## 5. Attribution Models
Attribution answers "what caused the deal?" Getting it right determines where you invest next.
### Model Comparison
| Model | How It Works | Best For | Limitation |
|---|---|---|---|
| First-touch | 100% to first interaction | Top-of-funnel channel effectiveness | Ignores nurture and closing touches |
| Last-touch | 100% to final interaction | Bottom-of-funnel conversion analysis | Ignores awareness investment |
| Linear | Equal credit to all touchpoints | Simple fairness | Treats blog visit same as demo request |
| U-shaped | 40% first, 40% last, 20% middle | B2B with clear awareness-to-conversion journey | Undervalues mid-funnel |
| W-shaped | 30/30/30/10 (first/lead/opp/rest) | B2B with defined marketing-to-sales handoff | Requires clear CRM stage definitions |
| Time-decay | Increasing credit toward conversion | Long sales cycles | Undervalues early brand investment |
| AI-driven | ML determines credit dynamically | Orgs with 500+ conversions | Black box; requires data maturity |
### Choosing by Company Stage
| Stage | Model | Why |
|---|---|---|
| Pre-revenue / <$1M | First-touch | Know which channels generate any pipeline |
| $1-5M | U-shaped | Credits awareness and conversion, most actionable |
| $5-20M | W-shaped | Marketing-to-sales handoff stages worth measuring |
| $20M+ | Time-decay or AI-driven | Enough data; long cycles justify recency weighting |
| PLG (any stage) | Product-touch | Attribute to in-product actions, not just marketing |
### Attribution Lookback Windows
Set lookback to match your sales cycle: 90 days for SMB, 180 days for mid-market, 365 days for enterprise. Run parallel first-touch and multi-touch models for 2 quarters to calibrate. Review quarterly.
### AI GTM Attribution Challenges
| Challenge | Mitigation |
|---|---|
| AI SDR touches invisible to buyers | Tag AI-generated touches with source=AI-SDR in CRM |
| Multi-channel AI sequences | Track channel and sequence membership, not just "AI outreach" |
| Influence vs. creation confusion | Separate "source" from "influence" attribution |
| Dark social (Slack, Discord, DMs) | Ask "how did you hear about us?" in demo forms |
---
## 6. Dashboard Architecture
### Three-Tier Hierarchy
**Tier 1: Board (5-7 metrics, monthly)** - ARR + Net New ARR waterfall, NRR, CAC Payback, Burn Multiple, Pipeline Coverage, Magic Number, Cash Runway.
**Tier 2: Executive (10-12 metrics, weekly)** - Pipeline created, pipeline by stage, win rate by segment, deal size trend, sales cycle length, quota attainment by rep, NRR by cohort, CAC by channel, TTFV, data health score, slippage rate.
**Tier 3: Operator (15-25 metrics, daily)** - Activity (emails, calls, meetings booked), pipeline (new opps, stage movements), response (speed-to-lead, follow-up rate), conversion (stage-by-stage rates), quality (ICP fit distribution), AI ops (AI messages, AI reply rate, cost per meeting).
### Tool Selection
| Tool | Best For | Cost |
|---|---|---|
| HubSpot Dashboards | Teams already on HubSpot | Included |
| Metabase | SQL-native, self-hosted | Free |
| Looker | Enterprise-grade, governed | $$$ |
| Mode | SQL + Python + viz | $$ |
| Google Sheets | Solo founders, pre-revenue | Free |
### Dashboard Anti-Patterns
| Anti-Pattern | Fix |
|---|---|
| 50+ metrics on one screen | Limit to tier-appropriate count |
| Vanity metrics without context | Every metric needs benchmark, target, or trend line |
| Manual data entry | All metrics from system-of-record APIs |
| No dashboard owner | Named owner + review schedule required |
| Snapshot without trend | Always show trailing 4-week or 13-week trend |
---
## 7. Leading vs. Lagging Indicators
Maintain a 60/40 balance: 60% leading indicators (what is about to happen) and 40% lagging indicators (what already happened).
### Leading Indicators
| Indicator | Predicts | If Declining |
|---|---|---|
| Pipeline created this week | Revenue 1-2 quarters out | Increase top-of-funnel investment |
| Meeting conversion rate | Win rate next quarter | Audit qualification and demo quality |
| Speed-to-lead | Inbound conversion rate | Fix routing (<5 min target) |
| Product activation rate | Free-to-paid conversion | Audit onboarding flow |
| Sequence reply rate | Meeting volume next month | Refresh messaging and targeting |
| Feature adoption depth | NRR next quarter | Proactive CS intervention |
| Champion engagement frequency | Deal probability | Deal is at risk if champion goes quiet |
### Lagging Indicators
Revenue, win rate, CAC/payback, NRR/GRR, LTV:CAC, burn multiple, quota attainment distribution. Review monthly or quarterly.
### The Leading-to-Lagging Chain
```
Revenue (lagging)
<-- Win Rate
<-- Demo Quality Score (leading)
<-- ICP Fit Score of Pipeline (leading)
<-- Pipeline Volume
<-- Meetings Booked (leading)
<-- Outreach Volume + Reply Rate (leading)
<-- Deal Size
<-- Multi-threading Depth (leading)
```
---
## 8. Weekly GTM Review Cadence
### The Weekly Meeting (30-45 Minutes)
The single most important GTM operating ritual. Every metric from system-of-record data. No hand-edited slides.
| Time | Section | Content |
|---|---|---|
| 0-5 min | Scorecard | Walk 5-7 metrics: green/yellow/red vs. targets |
| 5-15 min | Pipeline | New pipeline, stage movements, slippage, forecast changes |
| 15-20 min | Leading indicators | Inbound volume, outreach metrics, meeting conversion |
| 20-25 min | Deals at risk | Stalled deals, blockers, help requests |
| 25-35 min | Actions | 2-3 specific actions with owners and deadlines |
| 35-45 min | Deep-dive | One strategic topic per week (rotating) |
### Weekly Scorecard
| Metric | This Week | Last Week | 4-Wk Avg | Target | Status | Owner |
|---|---|---|---|---|---|---|
| Pipeline created | $X | $X | $X | $X | G/Y/R | Name |
| Meetings booked | X | X | X | X | | Name |
| Win rate (30d) | X% | X% | X% | X% | | Name |
| Cycle length | Xd | Xd | Xd | Xd | | Name |
| Slippage rate | X% | X% | X% | <15% | | Name |
| Speed-to-lead | Xm | Xm | Xm | <5m | | Name |
### Monthly Deep-Dives
NRR/retention analysis (cohort curves, churn reasons, expansion pipeline), CAC/efficiency review (CAC by channel, payback trend, Magic Number), data health audit (CRM completeness, enrichment gaps), competitive update (pricing, positioning, feature changes).
### Quarterly Strategic Reviews
ICP refresh (win/loss analysis, drift detection, scoring update), funnel benchmarking (stage conversions vs. industry), attribution model review (channel ROI, budget allocation), GTM motion evaluation (sales-led vs. PLG vs. agent performance).
---
## 9. PQL Scoring
Product-Qualified Leads replace MQLs in product-led and hybrid motions. Score on product usage instead of content downloads.
### PQL Scoring Model
```
PQL Score = (Usage Signals * 0.50) + (Fit Signals * 0.30) + (Intent Signals * 0.20)
```
| Score | Tier | Action |
|---|---|---|
| 80-100 | Hot | Route to AE, respond within 4 hours |
| 60-79 | Warm | Sales-assist sequence (email + SDR) |
| 40-59 | Nurture | In-app messaging + drip emails |
| Below 40 | Self-serve | No sales touch; optimize product experience |
PQL-to-customer conversion: 5-15% (vs. 1-3% MQL-to-customer). Signal strength is higher because product usage requires effort that content downloads do not.
---
## Examples
- **User says:** "What metrics should we track for GTM?" → **Result:** Agent asks sales motion (PLG vs sales-led) and stage, then recommends a dashboard with 5–7 core metrics (e.g. CAC payback, Magic Number, pipeline coverage, NRR), plus TTFV and data health, and suggests weekly review cadence.
- **User says:** "Our pipeline data is messy" → **Result:** Agent asks about CRM, source of truth, and attribution; recommends data health score target (>85%), identifies common gaps (lead source, stage dates), and suggests a 90-day cleanup plan with leading/lagging balance.
- **User says:** "How do we compare to benchmarks?" → **Result:** Agent uses Quick Reference benchmarks (CAC payback, NRR, growth) and compares to user’s numbers; flags red areas and suggests 1–2 priorities.
## Troubleshooting
- **Metrics don’t match across tools** → **Cause:** Different definitions or attribution windows. **Fix:** Define one source of truth (e.g. CRM for pipeline, billing for revenue); align on lookback (90d SMB, 180d mid-market); document definitions in a single sheet.
- **CAC payback getting worse** → **Cause:** CAC up and/or velocity down. **Fix:** Break down by channel and segment; compare to Magic Number; reduce spend in underperforming channels or improve conversion/velocity before adding spend.
- **NRR below 100%** → **Cause:** Churn and/or downgrades outweigh expansion. **Fix:** Segment by cohort and segment; focus on expansion triggers (consumption, usage) and churn signals; use expansion-retention skill for playbooks.
---
## Quick Reference
| Concept | Key Number or Rule |
|---|---|
| CAC Payback benchmark | Median 8.6 months; top performers 5-7 |
| Magic Number threshold | >0.75 efficient, >1.0 excellent, <0.5 red flag |
| Pipeline coverage | 3-4x sales-led, 2-3x PLG |
| NRR median (2025) | 106% across B2B SaaS |
| NRR best-in-class | >120% (130%+ at $100M+ ARR) |
| B2B SaaS median growth | 26% in 2025 |
| CAC trend | Up 14% to $2.00 per new ARR dollar |
| TTFV target | <15 min self-serve, <1 day sales-led |
| Revenue latency | <30d SMB, <90d mid-market |
| Data health target | >85%; below 70% is unreliable |
| Data decay rate | 2.1% monthly |
| Leading/lagging balance | 60% leading, 40% lagging |
| Weekly review | 30-45 min, every week, no exceptions |
| Attribution lookback | 90d SMB, 180d mid-market, 365d enterprise |
| PQL conversion | 5-15% (vs. 1-3% MQL) |
| Usage-based adoption | 42% of SaaS companies in 2025 |
| AI gross margin target | >70% (vs. ~80% pure SaaS) |
| Expansion at scale | >40% of new ARR from existing customers |
| Slippage target | <15% weekly |
| Speed-to-lead | <5 minutes |
---
## Questions to Ask
1. What metrics does your team review weekly today, and who owns each one?
2. What is your current pipeline coverage ratio, and do you trust the data behind it?
3. How do you measure time-to-first-value for new customers?
4. What is your CAC payback period, and is it trending up or down?
5. What percentage of new ARR comes from expansion vs. new logos?
6. How complete is your CRM data? Could you run a data health audit this week?
7. What attribution model are you using, and when was it last reviewed?
8. Do you have separate funnel metrics for each GTM motion?
9. What is your current NRR, and how does it break down by segment?
10. How do you score and prioritize PQLs vs. MQLs?
11. What does your AI inference cost look like as a percentage of revenue?
12. Do you track leading indicators separately from lagging indicators?
13. What is your average speed-to-lead for inbound demo requests?
14. When did you last benchmark funnel conversion rates against industry standards?
15. Do you have a defined weekly GTM review cadence with a scorecard?
---
## Related Skills
| Skill | When to Cross-Reference |
|---|---|
| ai-pricing | Measuring pricing model impact on revenue metrics; usage-based pricing instrumentation |
| expansion-retention | NRR improvement plans, churn analysis, expansion playbooks |
| sales-motion-design | Redesigning stages, qualification, or handoffs based on funnel data |
| ai-cold-outreach | Outreach performance: reply rate, cost per meeting, AI SDR ROI |
| solo-founder-gtm | Prioritizing 3-5 metrics before building a full dashboard |
| gtm-engineering | Metric collection infrastructure, CRM automation, data pipelines |
| ai-sdr | AI SDR performance measurement, agent-led funnel metrics |
| lead-enrichment | Data health remediation, enrichment workflows |
| positioning-icp | When attribution reveals positioning or ICP changes needed |
| content-to-pipeline | Content attribution, connecting top-of-funnel to pipeline |Related Skills
ai-pricing
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.
ai-ugc-ads
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.
ai-sdr
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.
tlc-spec-driven
Project and feature planning with 4 adaptive phases - Specify, Design, Tasks, Execute. Auto-sizes depth by complexity. Creates atomic tasks with verification criteria, atomic git commits, requirement traceability, and persistent memory across sessions. Stack-agnostic. Use when (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification and atomic commits, (5) Quick ad-hoc tasks (bug fixes, config changes), (6) Tracking decisions/blockers/deferred ideas across sessions, (7) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "quick fix", "quick task", "pause work", "resume work". Do NOT use for architecture decomposition analysis (use architecture skills) or technical design docs (use create-technical-design-doc).
docs-writer
Write, review, and edit documentation files with consistent structure, tone, and technical accuracy. Use when creating docs, reviewing markdown files, writing READMEs, updating `/docs` directories, or when user says "write documentation", "review this doc", "improve this README", "create a guide", or "edit markdown". Do NOT use for code comments, inline JSDoc, or API reference generation.
ai-cold-outreach
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.
the-fool
Use when challenging ideas, plans, decisions, or proposals. Invoke to play devil's advocate, run a pre-mortem, red team, stress test assumptions, audit evidence quality, or find blind spots before committing. Do NOT use for building plans, making decisions, or generating solutions — this skill only challenges and critiques.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Use when the user provides Figma URLs or node IDs and asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection. Do NOT use for general Figma data fetching, variable exploration, or MCP troubleshooting (use figma instead).
coupling-analysis
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit).
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Uses `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treats external providers (for example Buildkite) as out of scope and reports only the details URL. Do NOT use for addressing PR review comments (use gh-address-comments) or general CI outside GitHub Actions.
content-to-pipeline
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.