sell
Skill4 starsChanged 2 days agoMITView on GitHub
Run the sales pipeline for a startup idea: account research, outreach and follow-up drafts, call prep, post-call summaries, and pipeline status tracked in a founder hub folder. Use when turning interested prospects into pilots, design partners or paying customers, when asked to prep for a sales call, draft a follow-up, research an account, or show where deals stand.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jtmuller5/small-business-skillstheir own version, first seen Oct 20, 2026
- AetherCore-Dev/ag402their own version, first seen Mar 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- AetherCore-Dev/ag402★ 9same name
- jtmuller5/small-business-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- agent-writingSkill
- arenaSkill
- blast-radiusSkill
- bun-playwright-runner-selectionSkill
- cinematic-shotSkill
- clean-ui-shotSkill
- codebase-designSkill
- debug-loopSkill
- dep-upgradeSkill
- diagnosing-bugsSkill
- discoverSkill
- domain-modelingSkill
- earshotSkill
- eval-judgeSkill
- flaky-testSkill
- grillingSkill
- grillSkill
- idea-scoutSkill
- improve-codebase-architectureSkill
- interrogateSkill
- make-mediaSkill
- migrate-to-rustSkill
- migration-planSkill
- multi-agent-windows-hazardsSkill
- perf-loopSkill
- postmortemSkill
- prototypeSkill
- prSkill
- real-soundSkill
- recallSkill
- release-notesSkill
- repo-mapSkill
- researchSkill
- retroSkill
- secure-diffSkill
- subagent-report-recoverySkill
- tasteSkill
- taste-skillSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- wayfinderSkill
- weeklySkill
- windows-bash-backslash-halvingSkill
- wizardSkill
- writing-for-agentsSkill
- ycSkill
- ystack-upgradeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Read bottleneck.md and the idea's evidence files first.
- Distinctive: line 40
If sales skills are installed (for example account research, outreach drafting, call prep or call summary skills), use them for the step, …
- Distinctive: line 59
Never overstate the product.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/sell: turn interest into pilots and payments
The founder hub
This skill reads and writes a founder hub: one folder holding the startup's truth.
- Location: the
FOUNDER_HUBenvironment variable, default~/founder. Below,<hub>means that folder. - Files this skill uses:
| File | What it holds |
<hub>/README.md | The decision and evidence rules (the discover skill writes defaults). Read it if present |
<hub>/bottleneck.md | The current bet, this week's single bottleneck, the goal and its deadline |
<hub>/evidence/<idea>.md | Conversation log, signed pilots and payments for one idea |
<hub>/evidence/<idea>-prospects.md | Researched prospects and outreach status (from discover) |
<hub>/evidence/<idea>-pipeline.md | The pipeline: one row per account, its stage, and a dated log of stage changes |
Pipeline stages: contacted → talked → pilot offered → pilot live → paying.
If the hub or a file is missing, say so and offer to create it: the folder, an empty
bottleneck.md (current bet, bottleneck, goal, deadline), evidence/, and a pipeline file seeded from
the prospects and evidence files if they exist, or empty with the stage columns if not. Never skip a
write silently because a file wasn't there.
Read bottleneck.md and the idea's evidence files first.
Commands
If sales skills are installed (for example account research, outreach drafting, call prep or call summary skills), use them for the step, then write the result back into the hub. They're optional; everything below works with web search alone.
research <company>: what they do, size and stage, recent news, who owns the problem, and a concrete signal that they have it. Cite sources. Add the result to the pipeline file.prep <person>: a one-page call brief: their context, what the log already says, the 3 questions that matter most, the commitment to ask for (pilot, data access, paid trial), and likely objections with honest answers.followup <person>: a short follow-up that restates their problem in their words and makes one clear, small ask. Paste notes from a call and it also logs the call (asdiscover logdoes) before drafting.status(the default): pipeline counts by stage, deals stuck for more than 5 days, and today's 3 highest-value actions.
Rules
- The human sends every message. Draft only. Never send, post or email anything yourself, even if a tool for it is available.
- Never overstate the product. A pilot offer describes what exists today, plus what will be built for them, with a date.
- Pricing: propose a concrete paid pilot. Even a small payment is strong evidence; "free forever" isn't.
- Log every stage change with a date in the pipeline file, and any payment or signed pilot in
evidence/<idea>.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.