focus
Skill258 starsChanged 28 days agoMITView on GitHub
Use this skill when a solo founder wants a gut check on how to spend time or money: 'is this worth my time,' 'should I keep doing X,' 'I'm not getting results from X,' '80/20,' 'should I sign up for this,' 'should I buy this,' 'should I run ads,' 'should I hire someone,' 'should I raise money,' or 'which feature should I build next.' Returns one verdict and a plan for this week. Not for testing whether an idea has demand (use validate) or for finding the founder's overall stage (use journey).
10 other projects use a version of this.
Adopted by
Most recently taken up by
- whawkinsiv/solo-founder-skillsword for word, first seen Oct 25, 2026
- wheslleyrimar/BuildCLI-Agentstheir own version, first seen Oct 22, 2026
- chrdrk/claude-focustheir own version, first seen Oct 13, 2026
- yanfeid/claude-ambertheir own version, first seen Oct 13, 2026
- Haumer/claude-skillstheir own version, first seen Oct 11, 2026
- devinat1/skillstheir own version, first seen Oct 6, 2026
Other versions10 projects use a version of this.
Word for word · 1
- whawkinsiv/solo-founder-skills★ 260100% same
Edited · 0
None found.
Wrote their own version · 9
- kennethleungty/claude-music★ 23same name
- wheslleyrimar/BuildCLI-Agents★ 3same name
- yanfeid/claude-amber★ 2same name
- devinat1/skills★ 1same name
- vishk23/screenblock-mcp★ 1same name
- breethomas/bette-os★ 0same name
- chrdrk/claude-focus★ 0same name
- Haumer/claude-skills★ 0same name
- markbaindesign/bain-studio★ 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 repository20 other files it gives its agents.
- about-meSkill
- beautifySkill
- buildSkill
- contentSkill
- domain-nameSkill
- emailSkill
- financesSkill
- first-customersSkill
- go-liveSkill
- humanizeSkill
- is-this-an-appSkill
- journeySkill
- landing-pageSkill
- legalSkill
- paymentsSkill
- pricingSkill
- retentionSkill
- secureSkill
- seoSkill
- validateSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask only what you cannot infer.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Focus
Judge one activity, one decision, or one feature choice against the founder's stage. Return one verdict and one plan for this week.
Step 1: Get the facts
Ask only what you cannot infer. Two or three questions:
- What exactly is it? Not "marketing", but "50 cold emails a week to dental offices."
- How many paying customers do you have?
- For an activity: hours per week, and results so far. For a decision: the cost, and whether you can undo it.
Then use the mode that fits.
Mode A: An ongoing activity
Apply two tests.
- Ceiling. Could this activity move the business at this stage, even if done perfectly? SEO with zero customers, ads without a known conversion rate, and integrations for a product nobody uses all have a low ceiling.
- Execution. Is the founder doing the strong 20%, or spreading effort across all of it? Examples: 100 generic emails instead of 10 researched ones, or four platforms instead of one.
Verdict:
- Kill: low ceiling, or a much better alternative exists.
- Refine: right activity, spread too thin. Cut to the 20%.
- Pivot: right goal, wrong tactic for this stage. Name the tactic to switch to.
Mode B: A one-time decision
Examples: a yearly contract, a large purchase, a first contractor, a paid course, ads, raising money.
Ask five questions:
- Did a paying customer ask for this, or need it?
- Can the founder do it by hand or for free first?
- Can it be undone? Yearly contracts, hires, and investor terms are hard to undo.
- What does it do to monthly profit?
- Does it bring the next customer milestone (10, then 100) closer?
Verdict: Do it, Do a smaller version (name it), or Do not do it. For raising money, also use finances.
Mode C: Which feature next
- Name the one problem each candidate solves, and how many paying customers have it.
- Build what 3 or more paying customers need. One loud request is an anecdote.
- Pick one. Cut it to what ships in a week, and use build.
Say no when a feature serves fewer than 1 in 10 customers, adds complexity for the rest, or a good-enough workaround exists.
What pays off at each stage
| Activity | Before 10 customers | 10–100 | 100+ |
| Direct outreach | High | Medium | Low |
| Being useful in communities | High | High | Medium |
| Content and SEO | Low: too slow | Medium: start | High: compounds |
| Paid ads | Low: unknown conversion | Low to medium: small tests | High: scale what converts |
| Referrals | Low: too few users | High | High |
| New features | Only if customers ask | Low: fix what exists | Medium |
| Bug fixes | High | High | High |
| Onboarding polish | Low: onboard by hand | High | Medium |
| Automation and tooling | Low: manual is fine | Medium | High |
| Pricing changes | High: most founders underprice | High | Medium |
| Hiring | Low | Low to medium | Medium |
The common trap: choosing what feels scalable (SEO, ads, automation) before anything works by hand.
Output
Verdict: <Kill / Refine / Pivot, or Do it / Smaller version / Do not, or the chosen feature>
Why: <2-3 sentences: the ceiling, the cost, the alternative>
This week:
- Stop: <specific>
- Start: <specific, with the 20% version>
- Time or money freed: <amount, redirected to what>
Trap to avoid: <one>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.

