first-win
Skill25 starsChanged 7 days agoMITView on GitHub
Offer three starter tasks that produce usable artifacts. Use when seeking a first win, a day-one task, or something useful to try first.
In this repository71 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- agent-fitnessSkill
- body-checkSkill
- briefSkill
- capsule-compactSkill
- closeSkill
- codex-adapterSkill
- cognitive-updateSkill
- comms-summarizeSkill
- compact-noteSkill
- context-capsuleSkill
- context-hygieneSkill
- critique-planSkill
- decideSkill
- deep-reconSkill
- DiagnoseSkill
- digestSkill
- dreamSkill
- EnvelopeSkill
- find-weaknessSkill
- First 10 MovesSkill
- frontend-slidesSkill
- Honesty CheckSkill
- humanize-docsSkill
- impeccableSkill
- learn-from-failureSkill
- LearnSkill
- memory-bridgeSkill
- meta-improveSkill
- meta-improve-vaultSkill
- nightly-close-paritySkill
- nightly-ledger-captureSkill
- nightlySkill
- openSkill
- operator-setupSkill
- orientSkill
- pauseSkill
- ponytailSkill
- port-specSkill
- PromoteSkill
- reconcileSkill
- research-deepSkill
- resumeSkill
- Sandbox RoutingSkill
- scout-vaultSkill
- Self-ReviewSkill
- semantic-searchSkill
- setupSkill
- ship-adapterSkill
- Skill AuditSkill
- skill-huntSkill
- skill-recallSkill
- solution-huntSkill
- sprite-specSkill
- startSkill
- statusSkill
- StuckSkill
- supersedeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 19
Ask them to paste their most recent newsletter, blog post, or even a few sentences about what they do.
- Distinctive: line 25
Ask for the idea in a sentence.
- Distinctive: line 29
If an inbox connector is set up, summarize their inbox into three priorities for today.
- Distinctive: line 47
Every task ends with a real artifact in hand.
- Distinctive: line 50
No em-dashes. No emoji. No filler.
≈ “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
/first-win: ship something real, today
The operator has just met you (via /operator-setup). Now give them proof of work: a real
artifact they can use today. This is what satisfies the "ship something real, fast" promise
on day one, instead of making them wait for a longer pipeline.
The menu
Offer these three. Lead with the two zero-dependency tasks so the win never stalls waiting on an inbox connection or any login beyond their Claude account:
- Turn your last post into a week of social posts. (zero-dependency, default) Ask them to paste their most recent newsletter, blog post, or even a few sentences about what they do. Produce five to seven platform-ready posts in their voice, each with a clear hook. If they have nothing to paste, use the known-good example below so they still get a result.
- Turn a rough idea into a structured plan. (zero-dependency, default) Ask for the idea in a sentence. Produce a structured plan: the outcome, the steps in order, the first action they can take today, and what "done" looks like. Concrete, not generic.
- Today's three priorities from your inbox. (only if connected) If an inbox connector is set up, summarize their inbox into three priorities for today. If not, they paste a handful of emails or notes and you do the same thing. Never block on OAuth or a connector. This task always has the paste-in fallback.
Delivery
- Produce the artifact directly in the session, formatted cleanly, ready to use or copy.
- Then ask: "Want to tweak it, or save it and move on?" Keep it conversational.
Known-good example inputs (so a blank-page operator always gets a result)
- For task 1: a short sample post about a local trades bookkeeping practice, which you turn into a week of social posts as a demonstration, then offer to redo it with their real content.
- For task 2: "I want to start a weekly email for my customers" as the rough idea, which you turn into a structured plan.
Rules
- Every task ends with a real artifact in hand. No "here's how you could do it" without actually doing it.
- Plain-English voice. Show the artifact, not a lecture about how to make one.
- No em-dashes. No emoji. No filler.
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.