New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Build a scalable outbound B2B sales machine with specialized

Predictable Revenue Framework

by wondelai · MIT license · ★ 2,235 on GitHub · updated Sep 10

Predictable Revenue Framework cover

Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an…

---
name: predictable-revenue
description: 'Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B SaaS sales team from scratch or building a lead-qualification framework to improve close rates. Covers the three lead types (seeds/nets/spears), role specialization, the referral-email method, ANUM qualification, and pipeline math. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.'
license: MIT
metadata:
  author: wondelai
  version: "1.4.0"
---

# Predictable Revenue Framework

A systematic approach to building a scalable, predictable B2B sales machine — the outbound prospecting system that helped Salesforce add $100M in recurring revenue.

## Core Principle

**Predictable lead generation drives predictable revenue.** The biggest mistake in sales is having the same people prospect AND close — specialization creates a repeatable, scalable machine. Traditional cold calling is dead; Cold Calling 2.0 (mass, personalized cold emails that generate referrals to the right person) is the new outbound.

## Scoring

Overview

A systematic approach to building a scalable, predictable B2B sales machine — the outbound prospecting system that helped Salesforce add $100M in recurring revenue.

Manual install (npx, ZIP)
Claude Codenpx skills add wondelai/skills --skill predictable-revenue -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wondelai/skills/tar.gz/c172996495be \ | tar -xz -C ~/.claude/skills --strip-components=4 skills-c172996495be/plugins/sales-influence/skills/predictable-revenue
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/77183d2d4265940dde78/predictable-revenue.zip" -OutFile "$env:TEMP\predictable-revenue.zip"; Expand-Archive "$env:TEMP\predictable-revenue.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md12.1 KB
  • references/8 files · 102.5 KB
Read the files here
wondelai/c1729969 files
SKILL.md
Show the full text209 lines

Predictable Revenue Framework

A systematic approach to building a scalable, predictable B2B sales machine — the outbound prospecting system that helped Salesforce add $100M in recurring revenue.

Core Principle

Predictable lead generation drives predictable revenue. The biggest mistake in sales is having the same people prospect AND close — specialization creates a repeatable, scalable machine. Traditional cold calling is dead; Cold Calling 2.0 (mass, personalized cold emails that generate referrals to the right person) is the new outbound.

Scoring

Goal: 10/10. Score a sales process 0-10 by awarding 2 points for each of the five Quick Diagnostic rows it satisfies (prospecting/closing separated, defined outbound process, 3-month pipeline predictability, known lead-type mix, standardized SDR→AE handoff). Bands: 9-10 = role separation plus a repeatable process that predicts pipeline; 5-6 = some specialization but ad-hoc prospecting or unpredictable pipeline; ≤3 = one person prospects and closes, revenue depends on heroics. Always give the current score and the specific diagnostic rows blocking 10/10.

The Three Types of Leads

Not all leads are equal — treat them differently.

Type Source Conversion Cost Example
Seeds Word of mouth, referrals, organic Highest Lowest (takes time) Customer referral, NPS-driven
Nets Marketing campaigns, inbound Medium Medium Content, SEO, webinars
Spears Outbound prospecting Lower but predictable Higher (people-intensive) Cold Calling 2.0

Key insight: Most companies over-invest in nets and under-invest in spears; seeds are the best but can't be manufactured quickly. Invest accordingly — customer success and referral programs (seeds), content and paid acquisition (nets), SDR team (spears).

See references/lead-types.md when deciding where to invest — it sizes the seeds/nets/spears budget split by company stage.

Sales Role Specialization

The #1 principle: separate prospecting from closing. When AEs prospect and close, they hate prospecting and pipeline becomes feast-or-famine.

Role Focus Metrics
SDR (Sales Development Rep) Outbound prospecting → qualified opportunities Qualified meetings/month
MDR (Market Development Rep) Inbound lead qualification Qualified leads/month
AE (Account Executive) Close deals Revenue closed, win rate
CSM (Customer Success Manager) Retain and grow accounts Retention, expansion revenue
SDR (Sales Development Rep)

Generate qualified pipeline: research target accounts, send Cold Calling 2.0 emails, get referred to the right person, qualify with ANUM, pass to AEs. Not their job: closing, inbound leads, or existing customers. One SDR typically generates 10-20 qualified opportunities per month — measure opportunities, response rate, meetings booked, and pipeline value.

AE (Account Executive)

Close deals from qualified pipeline: run discovery, demo, negotiate, close, hand off to CSM. Not their job: prospecting (SDR), inbound qualification (MDR), or post-sale management (CSM). Measure revenue closed, win rate, average deal size, and sales cycle length.

CSM (Customer Success Manager)

Retain and grow accounts: onboard, drive adoption, surface expansion opportunities, prevent churn. Measure net revenue retention, churn rate, expansion revenue, and NPS/CSAT.

The virtuous cycle: SDR generates pipeline → AE closes → CSM retains/grows → happy customer refers (Seeds).

See references/roles.md when defining a new role or org chart — it has full charters, career paths, and hiring profiles for each role.

Cold Calling 2.0

Outbound prospecting that replaces traditional cold calling, which fails on every front: 1-3% connection rate, gatekeepers, brand damage, no scalability.

1. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify
Step 1: Build Target Account List

Define your Ideal Customer Profile (company size, industry, tech stack, geography, pain points), then build the list via LinkedIn Sales Navigator, ZoomInfo/Apollo/Clearbit, or industry directories. Target 200-500 accounts per SDR per quarter.

Step 2: The Referral Email

The core innovation: don't email the decision maker — email above them and ask for a referral down. Senior people forward emails, and referrals get 3-5x higher response because the introduction comes from inside the company. The email asks one thing — "who is the right person?" — under 100 words, no pitch, no attachments, no links, easy to forward. Response rate: 9-15% vs. 1-3% for traditional cold emails. For the verbatim template, subject-line open-rate table, and the full Day 1/3/7/14/30 sequence bodies, open references/cold-calling-2.md.

Step 3: Follow Up
Day Action
1 Send referral email
3 Follow up if no response
7 Second follow-up (different angle)
14 Break-up email ("Should I close your file?")
30 Re-engage (new trigger event or content)

The break-up email on Day 14 often draws the highest response in the sequence — people respond to losing the opportunity (scarcity).

Step 4: Qualify with ANUM
Criteria Question Strong Signal Weak Signal
Authority Can this person decide? Decision maker or strong influencer No buying power
Need Do they have the problem you solve? Active pain, seeking solutions "Nice to have"
Urgency When must they solve it? This quarter, budget allocated "Someday"
Money Can they afford it? Budget exists, within range No budget, too expensive

Call structure: rapport (2 min) → set agenda ("understand your situation, see if there's a fit") → discovery questions with ANUM built in (10-15 min) → next steps (if qualified, schedule AE demo).

Step 5: Hand Off to AE

Include account background and ICP match, contact details and role, pain points, ANUM notes, agreed next steps, and competitive intel. SDR introduces AE on a brief 3-way call or email, then drops off.

Ethical boundary: Comply with spam laws (CAN-SPAM, GDPR) and honor opt-outs immediately — including removing a hostile "stop emailing me" from the sequence on the spot, not at the next scheduled touch.

See references/qualification.md when running the ANUM discovery call — it has the full discovery question bank per criterion.

Pipeline Math

Work backward from the revenue goal:

Revenue Goal ÷ Average Deal Size = Deals Needed
Deals Needed ÷ Win Rate = Opportunities Needed
Opportunities Needed ÷ SDR Conversion = Prospects Needed
Prospects Needed ÷ Response Rate = Emails Needed

Example: $1M ARR ÷ $20K deals = 50 deals; ÷ 25% win rate = 200 opportunities; at 10% response rate and 10% response-to-qualified conversion = 20,000 emails ≈ 2-3 SDRs (each sends 300-500/month).

Metric Benchmark
Emails per SDR per day 50-100
Response rate 9-15%
Qualified opportunities per SDR per month 10-20
AE demo-to-close rate 20-30%
Average sales cycle 30-90 days

See references/pipeline-math.md when sizing the SDR team to a revenue target — it has the full capacity-planning and revenue-modeling templates.

Building the Sales Development Team

See references/case-studies.md when you want a worked precedent for standing up or scaling the machine — it walks through Salesforce, HubSpot, and other implementations with starting state, results, and failure modes.

Hiring SDRs

Hire for coachability (the most important trait), curiosity, strong writing, resilience, and organization — experience is optional. Source recent graduates, career changers, and internal transfers. Career path: SDR (6-18 months) → Senior SDR → AE or SDR Manager.

SDR Ramp Time
Phase Timeline Expectations
Training Weeks 1-2 Product knowledge, tools, process
Shadowing Weeks 3-4 Observe experienced SDRs, practice
Ramping Months 2-3 50% of quota
Full quota Month 4+ 100% of quota

Expect 3-4 months to full productivity.

SDR Compensation

Base + variable, typically 60/40 or 70/30. Pay variable per qualified opportunity generated, with bonuses for opportunities that close and for exceeding quota.

See references/team-building.md when hiring or building the comp plan — it has interview scorecards, the onboarding curriculum, and detailed compensation structures.

Metrics and Dashboards

Leading Indicators (Predictive)

Emails sent per SDR per day, response rate, meetings booked per week, qualified opportunities per month, pipeline value generated.

Lagging Indicators (Results)

Revenue closed, win rate, average deal size, sales cycle length, customer acquisition cost (CAC).

Efficiency Metrics

Cost per qualified opportunity, SDR:AE ratio (typically 2-3 SDRs per AE), LTV:CAC (target >3:1), payback period.

Cadence: daily activity metrics → weekly pipeline → monthly revenue → quarterly efficiency.

See references/metrics.md when building the sales dashboard — it has KPI definitions, formulas, and dashboard layouts by cadence.

Common Mistakes

Mistake Why It Fails Fix
AEs prospecting Feast-or-famine pipeline Hire dedicated SDRs
Long, pitchy emails Low response rate Short, referral-focused emails
No ICP definition Effort wasted on wrong accounts Define ICP before hiring SDRs
Too few SDRs Not enough pipeline Work backward from revenue goal
No hand-off process Leads fall through cracks Standardize SDR→AE handoff
Measuring activity, not results Busy but not productive Track qualified opportunities, not emails

Quick Diagnostic

Audit any B2B sales process:

Question If No Action
Are prospecting and closing separated? SDRs doing both = bottleneck Create dedicated SDR role
Is there a defined outbound process? Ad-hoc prospecting Implement Cold Calling 2.0
Can you predict pipeline 3 months out? Revenue is unpredictable Build pipeline math model
Do you know your lead type mix? Over-reliance on one source Balance seeds, nets, spears
Is SDR→AE handoff standardized? Leads lost in transition Create handoff checklist

Further Reading

For the complete system:

About the Author

Aaron Ross built the outbound sales process at Salesforce.com that added $100M+ in recurring revenue, and co-founded Predictable Revenue Inc. His book Predictable Revenue — known as "The Bible of Outbound Sales" — made Cold Calling 2.0 the standard for B2B outbound prospecting.

1---
2name: predictable-revenue
3description: 'Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B SaaS sales team from scratch or building a lead-qualification framework to improve close rates. Covers the three lead types (seeds/nets/spears), role specialization, the referral-email method, ANUM qualification, and pipeline math. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.'
4license: MIT
5metadata:
6 author: wondelai
7 version: "1.4.0"
8---
9 
10# Predictable Revenue Framework
11 
12A systematic approach to building a scalable, predictable B2B sales machine — the outbound prospecting system that helped Salesforce add $100M in recurring revenue.
13 
14## Core Principle
15 
16**Predictable lead generation drives predictable revenue.** The biggest mistake in sales is having the same people prospect AND close — specialization creates a repeatable, scalable machine. Traditional cold calling is dead; Cold Calling 2.0 (mass, personalized cold emails that generate referrals to the right person) is the new outbound.
17 
18## Scoring
19 
20**Goal: 10/10.** Score a sales process 0-10 by awarding 2 points for each of the five [Quick Diagnostic](#quick-diagnostic) rows it satisfies (prospecting/closing separated, defined outbound process, 3-month pipeline predictability, known lead-type mix, standardized SDR→AE handoff). Bands: **9-10** = role separation plus a repeatable process that predicts pipeline; **5-6** = some specialization but ad-hoc prospecting or unpredictable pipeline; **≤3** = one person prospects and closes, revenue depends on heroics. Always give the current score and the specific diagnostic rows blocking 10/10.
21 
22## The Three Types of Leads
23 
24**Not all leads are equal — treat them differently.**
25 
26| Type | Source | Conversion | Cost | Example |
27|------|--------|------------|------|---------|
28| **Seeds** | Word of mouth, referrals, organic | Highest | Lowest (takes time) | Customer referral, NPS-driven |
29| **Nets** | Marketing campaigns, inbound | Medium | Medium | Content, SEO, webinars |
30| **Spears** | Outbound prospecting | Lower but predictable | Higher (people-intensive) | Cold Calling 2.0 |
31 
32**Key insight:** Most companies over-invest in nets and under-invest in spears; seeds are the best but can't be manufactured quickly. Invest accordingly — customer success and referral programs (seeds), content and paid acquisition (nets), SDR team (spears).
33 
34See [references/lead-types.md](references/lead-types.md) when deciding where to invest — it sizes the seeds/nets/spears budget split by company stage.
35 
36## Sales Role Specialization
37 
38**The #1 principle: separate prospecting from closing.** When AEs prospect and close, they hate prospecting and pipeline becomes feast-or-famine.
39 
40| Role | Focus | Metrics |
41|------|-------|---------|
42| **SDR (Sales Development Rep)** | Outbound prospecting → qualified opportunities | Qualified meetings/month |
43| **MDR (Market Development Rep)** | Inbound lead qualification | Qualified leads/month |
44| **AE (Account Executive)** | Close deals | Revenue closed, win rate |
45| **CSM (Customer Success Manager)** | Retain and grow accounts | Retention, expansion revenue |
46 
47### SDR (Sales Development Rep)
48 
49Generate qualified pipeline: research target accounts, send Cold Calling 2.0 emails, get referred to the right person, qualify with ANUM, pass to AEs. Not their job: closing, inbound leads, or existing customers. One SDR typically generates 10-20 qualified opportunities per month — measure opportunities, response rate, meetings booked, and pipeline value.
50 
51### AE (Account Executive)
52 
53Close deals from qualified pipeline: run discovery, demo, negotiate, close, hand off to CSM. Not their job: prospecting (SDR), inbound qualification (MDR), or post-sale management (CSM). Measure revenue closed, win rate, average deal size, and sales cycle length.
54 
55### CSM (Customer Success Manager)
56 
57Retain and grow accounts: onboard, drive adoption, surface expansion opportunities, prevent churn. Measure net revenue retention, churn rate, expansion revenue, and NPS/CSAT.
58 
59**The virtuous cycle:** SDR generates pipeline → AE closes → CSM retains/grows → happy customer refers (Seeds).
60 
61See [references/roles.md](references/roles.md) when defining a new role or org chart — it has full charters, career paths, and hiring profiles for each role.
62 
63## Cold Calling 2.0
64 
65**Outbound prospecting that replaces traditional cold calling**, which fails on every front: 1-3% connection rate, gatekeepers, brand damage, no scalability.
66 
67```
681. Build list → 2. Send mass email → 3. Get referral → 4. Call the referral → 5. Qualify
69```
70 
71### Step 1: Build Target Account List
72 
73Define your Ideal Customer Profile (company size, industry, tech stack, geography, pain points), then build the list via LinkedIn Sales Navigator, ZoomInfo/Apollo/Clearbit, or industry directories. Target 200-500 accounts per SDR per quarter.
74 
75### Step 2: The Referral Email
76 
77**The core innovation: don't email the decision maker — email above them and ask for a referral down.** Senior people forward emails, and referrals get 3-5x higher response because the introduction comes from inside the company. The email asks one thing — "who is the right person?" — under 100 words, no pitch, no attachments, no links, easy to forward. Response rate: 9-15% vs. 1-3% for traditional cold emails. For the verbatim template, subject-line open-rate table, and the full Day 1/3/7/14/30 sequence bodies, open [references/cold-calling-2.md](references/cold-calling-2.md).
78 
79### Step 3: Follow Up
80 
81| Day | Action |
82|-----|--------|
83| 1 | Send referral email |
84| 3 | Follow up if no response |
85| 7 | Second follow-up (different angle) |
86| 14 | Break-up email ("Should I close your file?") |
87| 30 | Re-engage (new trigger event or content) |
88 
89The **break-up email** on Day 14 often draws the highest response in the sequence — people respond to losing the opportunity (scarcity).
90 
91### Step 4: Qualify with ANUM
92 
93| Criteria | Question | Strong Signal | Weak Signal |
94|----------|----------|---------------|-------------|
95| **A**uthority | Can this person decide? | Decision maker or strong influencer | No buying power |
96| **N**eed | Do they have the problem you solve? | Active pain, seeking solutions | "Nice to have" |
97| **U**rgency | When must they solve it? | This quarter, budget allocated | "Someday" |
98| **M**oney | Can they afford it? | Budget exists, within range | No budget, too expensive |
99 
100Call structure: rapport (2 min) → set agenda ("understand your situation, see if there's a fit") → discovery questions with ANUM built in (10-15 min) → next steps (if qualified, schedule AE demo).
101 
102### Step 5: Hand Off to AE
103 
104Include account background and ICP match, contact details and role, pain points, ANUM notes, agreed next steps, and competitive intel. SDR introduces AE on a brief 3-way call or email, then drops off.
105 
106**Ethical boundary:** Comply with spam laws (CAN-SPAM, GDPR) and honor opt-outs immediately — including removing a hostile "stop emailing me" from the sequence on the spot, not at the next scheduled touch.
107 
108See [references/qualification.md](references/qualification.md) when running the ANUM discovery call — it has the full discovery question bank per criterion.
109 
110## Pipeline Math
111 
112Work backward from the revenue goal:
113 
114```
115Revenue Goal ÷ Average Deal Size = Deals Needed
116Deals Needed ÷ Win Rate = Opportunities Needed
117Opportunities Needed ÷ SDR Conversion = Prospects Needed
118Prospects Needed ÷ Response Rate = Emails Needed
119```
120 
121**Example:** $1M ARR ÷ $20K deals = 50 deals; ÷ 25% win rate = 200 opportunities; at 10% response rate and 10% response-to-qualified conversion = 20,000 emails ≈ 2-3 SDRs (each sends 300-500/month).
122 
123| Metric | Benchmark |
124|--------|-----------|
125| Emails per SDR per day | 50-100 |
126| Response rate | 9-15% |
127| Qualified opportunities per SDR per month | 10-20 |
128| AE demo-to-close rate | 20-30% |
129| Average sales cycle | 30-90 days |
130 
131See [references/pipeline-math.md](references/pipeline-math.md) when sizing the SDR team to a revenue target — it has the full capacity-planning and revenue-modeling templates.
132 
133## Building the Sales Development Team
134 
135See [references/case-studies.md](references/case-studies.md) when you want a worked precedent for standing up or scaling the machine — it walks through Salesforce, HubSpot, and other implementations with starting state, results, and failure modes.
136 
137### Hiring SDRs
138 
139Hire for coachability (the most important trait), curiosity, strong writing, resilience, and organization — experience is optional. Source recent graduates, career changers, and internal transfers. Career path: SDR (6-18 months) → Senior SDR → AE or SDR Manager.
140 
141### SDR Ramp Time
142 
143| Phase | Timeline | Expectations |
144|-------|----------|-------------|
145| Training | Weeks 1-2 | Product knowledge, tools, process |
146| Shadowing | Weeks 3-4 | Observe experienced SDRs, practice |
147| Ramping | Months 2-3 | 50% of quota |
148| Full quota | Month 4+ | 100% of quota |
149 
150Expect 3-4 months to full productivity.
151 
152### SDR Compensation
153 
154Base + variable, typically 60/40 or 70/30. Pay variable per qualified opportunity generated, with bonuses for opportunities that close and for exceeding quota.
155 
156See [references/team-building.md](references/team-building.md) when hiring or building the comp plan — it has interview scorecards, the onboarding curriculum, and detailed compensation structures.
157 
158## Metrics and Dashboards
159 
160### Leading Indicators (Predictive)
161 
162Emails sent per SDR per day, response rate, meetings booked per week, qualified opportunities per month, pipeline value generated.
163 
164### Lagging Indicators (Results)
165 
166Revenue closed, win rate, average deal size, sales cycle length, customer acquisition cost (CAC).
167 
168### Efficiency Metrics
169 
170Cost per qualified opportunity, SDR:AE ratio (typically 2-3 SDRs per AE), LTV:CAC (target >3:1), payback period.
171 
172**Cadence:** daily activity metrics → weekly pipeline → monthly revenue → quarterly efficiency.
173 
174See [references/metrics.md](references/metrics.md) when building the sales dashboard — it has KPI definitions, formulas, and dashboard layouts by cadence.
175 
176## Common Mistakes
177 
178| Mistake | Why It Fails | Fix |
179|---------|-------------|------|
180| **AEs prospecting** | Feast-or-famine pipeline | Hire dedicated SDRs |
181| **Long, pitchy emails** | Low response rate | Short, referral-focused emails |
182| **No ICP definition** | Effort wasted on wrong accounts | Define ICP before hiring SDRs |
183| **Too few SDRs** | Not enough pipeline | Work backward from revenue goal |
184| **No hand-off process** | Leads fall through cracks | Standardize SDR→AE handoff |
185| **Measuring activity, not results** | Busy but not productive | Track qualified opportunities, not emails |
186 
187## Quick Diagnostic
188 
189Audit any B2B sales process:
190 
191| Question | If No | Action |
192|----------|-------|--------|
193| Are prospecting and closing separated? | SDRs doing both = bottleneck | Create dedicated SDR role |
194| Is there a defined outbound process? | Ad-hoc prospecting | Implement Cold Calling 2.0 |
195| Can you predict pipeline 3 months out? | Revenue is unpredictable | Build pipeline math model |
196| Do you know your lead type mix? | Over-reliance on one source | Balance seeds, nets, spears |
197| Is SDR→AE handoff standardized? | Leads lost in transition | Create handoff checklist |
198 
199## Further Reading
200 
201For the complete system:
202 
203- [*"Predictable Revenue"*](https://www.amazon.com/Predictable-Revenue-Business-Practices-Salesforce-com/dp/0984380213?tag=wondelai00-20) by Aaron Ross & Marylou Tyler
204- [*"From Impossible to Inevitable"*](https://www.amazon.com/Impossible-Inevitable-Hyper-Growth-Companies-Predictable/dp/1119166713?tag=wondelai00-20) by Aaron Ross & Jason Lemkin (scaling to $100M+ ARR)
205 
206## About the Author
207 
208**Aaron Ross** built the outbound sales process at Salesforce.com that added $100M+ in recurring revenue, and co-founded Predictable Revenue Inc. His book *Predictable Revenue* — known as "The Bible of Outbound Sales" — made Cold Calling 2.0 the standard for B2B outbound prospecting.
209 
View all files on GitHub →

Details

Updated
Sep 10, 2026
License
MIT
Stars on the repo
★ 2,235
Checked
Source
wondelai/skills ↗
Creator
wondelai · 320 listings
View creator

Similar skills

See all →
MCPGet from zero to orchestrated multi-agent pipeline in 5⚡ NEXUS Quick-Start Guidemsitarzewski/agency-agents · by msitarzewski> Get from zero to orchestrated multi-agent pipeline in 5 minutes.★ 154k GitHub starsSkillStep 1 of the AI Video Editor pipelineclean-cut — the step-1 cut pipelinehassancs91/claude-youtube-editor · by hassancs91Step 1 of the AI Video Editor pipeline — turn raw talking-head footage into a clean master cut. Use when the user wants to "clean cut", "cut the raw footage", "remove filler / dead air / bad takes", "tighten the pacing", produce cuts.json, run the cut editor, or render a cleaned preview/master for a video-N project in this repo. Covers audio extraction, AssemblyAI transcription, authoring cuts.json (keeps/cuts/fluff categorized), the cut policy (content-aggressive, pause-natural ~0.5s), QA + review docs, the local cut-editor UI, tight/natural previews, the final 4K60 render, and producing edited-transcript.json as the handoff to /make-tsx. Not for building TSX overlays (that is /make-tsx) or the raw TSX authoring rules (that is vidtsx-2d-generator).★ 330 GitHub starsSkillMake an original animated music videoVocaloid-style MV pipeline (手書き / 文字PV)EGSECDA/vocaloid-style-mv-pipeline · by EGSECDAMake an original animated music video (MV / PV) for a song from its audio file plus lyrics, in the Vocaloid / J-pop lyric-video tradition: 手書き/tegaki (V家手书, 手描きMV, ボカロPV), 文字PV and kinetic typography (リリックモーション, リリックビデオ, 歌詞動画, 歌词视频, 动态歌词), anime-illustration MVs with an original character — for any mood, from dark ballads to bright upbeat summer pop. Renders to MP4 with a deterministic Canvas2D/WebGL2 engine in a headless browser: JIZURA lyric motion, AI-generated art, optional Blender toon 3D, beat-locked editing, 9:16 vertical/Shorts version. Use it whenever the user wants a music video, MV, PV, lyric video or beat-synced animation for a song, e.g. make an MV for my song", "turn this track into a lyric video", "给这首歌做个MV/PV", "做个V家手书", "この曲のMVを作って", ボカロPV作って", "縦型ショートも" — even if they only give a .wav/.mp3 and say "make a cool video for it". Not for editing existing footage or clip compilations.★ 169 GitHub starsSkillConstruction company AI agentConstruction Agent — Email → Project Management Pipelinehewi333/Mom-n-Pop-Skills · by hewi333Construction company AI agent — orchestrates email (Google Workspace), project management (JobTread Pave API), and file routing for a construction business. Handles email triage, attachment routing to JobTread, project status, task management, and daily briefings via Telegram. Reference implementation for a construction/trades business with an existing email→Drive→PM pipeline.★ 122 GitHub starsSkillTracking customer interactions, managing leadsCRM-Lite — Lightweight SQLite CRM for Small Businesshewi333/Mom-n-Pop-Skills · by hewi333Use when tracking customer interactions, managing leads, or building a lightweight CRM for small businesses without dedicated CRM software. Stores contacts, leads, activities, estimates, and communications in local SQLite.★ 122 GitHub starsSkillOrchestrates one narrated vertical short from ideask-pipeline: one video, idea to hand-offhowznguyen/shorts-kit · by howznguyenOrchestrates one narrated vertical short (TikTok, YouTube Shorts, Reels) from idea to upload-ready hand-off files, in the fixed order idea, facts, flow and visual choice, brief, narration, TTS, lint, scenes, still review, render, cover, normalize, encode, hand-off. Use when the user says "make a video about X", "start a new short", "take this idea to a finished video", "what's the next step", "where was I on this video", or asks how the whole pipeline fits together. Also when the user gives a video or audio file (or a folder of clips) to edit: "edit this video", "dựng video này", a .mov/.mp4 path. Points at the skill and the SOUL section that governs each step.★ 69 GitHub stars

More from wondelai

SkillManage software complexity through deep modulesA Philosophy of Software Design Frameworkwondelai/skills · by wondelaiManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.★ 2.2k GitHub starsSkillMetrics are the language of validated learningActionable metrics guidewondelai/skills · by wondelaiMetrics are the language of validated learning. The wrong metrics create the illusion of progress while the startup drifts toward failure.…★ 2.2k GitHub starsSkillAdvertising media is the vehicle that carries your messagewondelai/skills · by wondelaiAdvertising media is the vehicle that carries your message to your target market. Choosing the right media is not about what is trendy — it…★ 2.2k GitHub starsSkillAn affordance is a relationship between an objectAffordances: Designing for Actionwondelai/skills · by wondelaiAn affordance is a relationship between an object and a person that determines how the object could possibly be used. A chair affords…★ 2.2k GitHub starsSkillLean UX was designed to work inside Agile development teamsAgile integration for lean UXwondelai/skills · by wondelaiLean UX was designed to work inside Agile development teams, not alongside them. The central mechanism is dual-track agile, where a…★ 2.2k GitHub starsSkillThis reference translates the AMP framework from theoryAMP Applied: Practical Applications of Autonomy, Mastery, and Purposewondelai/skills · by wondelaiThis reference translates the AMP framework from theory into practice across six domains: product gamification, team management,…★ 2.2k GitHub stars