first-win — Claude Code skill: tasks and installation
This Claude Code skill offers three starter tasks that end with a usable artifact. Run /first-win to turn a post into social content, shape an idea into a plan, or sort email into priorities.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill first-win -a claude-codeWhat first-win does
first-win offers three tasks and creates the result in the session. It can reshape a post or a few sentences into social posts written in the author’s voice, or turn a short idea into a plan with an outcome, ordered steps, a first action for today, and a definition of done. The output is ready to use or copy.
The email task picks three priorities for today. It can use a connected inbox, or work from emails and notes pasted into the session. The first two tasks need no extra connections. If there is no source material, the skill can demonstrate the task with a sample post or an idea for a weekly customer email.
What it helps with
- turn a post or newsletter into social posts
- break an idea into steps and choose a first action
- pull three priorities from emails or notes
Example prompts for the agent
- Run
/first-winand turn my latest post into social posts. - Run
/first-winand make a plan for my idea of a weekly customer email. - Run
/first-winand pull three priorities from these emails.
How to install first-win
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill first-win -a claude-code2Manually: put the files in place
~/.claude/skills/first-win/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/first-win/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill first-win -a codex2Manually: put the files in place
.agents/skills/first-win/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill first-win -a cursor2Manually: put the files in place
.cursor/skills/first-win/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/first-win2Manually: put the files in place
.github/skills/first-win/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill first-win -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/first-winManually: put the files in place
.devin/skills/first-win/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill first-win -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about first-win
How do I install first-win in Claude Code?
Run npx skills add wrg32786/aigent-os --skill first-win -a claude-code. The skill file is at ~/.claude/skills/first-win/SKILL.md.
What does first-win do?
It offers three starter tasks: create social posts from existing content, make a structured plan from an idea, or find priorities in email. It produces the artifact in the session.
Does first-win need an inbox connector?
No. For the email task, paste emails or notes into the session instead. A connected inbox is another way to provide the material.
Source text
SKILL.md · MIT
--- name: first-win description: "Offer three starter tasks that produce usable artifacts. Use when seeking a first win, a day-one task, or something useful to try first." trigger: /first-win --- # /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: 1. **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. 2. **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. 3. **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.
© wrg32786 · MIT · wrg32786/aigent-os