The day-one first-win menu. Three dead-simple, high-value tasks (two zero-dependency) that each put a real, usable artifact in the operator's hands in minutes, so the "ship something real" promise is met on day one and never waits on a connector or OAuth.
Installs into .claude/skills of the current project.
Are you the author of First Win?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wrg32786-first-win)
---
name: first-win
description: The day-one first-win menu. Three dead-simple, high-value tasks (two zero-dependency) that each put a real, usable artifact in the operator's hands in minutes, so the "ship something real" promise is met on day one and never waits on a connector or OAuth.
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.