empty-state-writer
Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (first-use, user-cleared, no-results, error/permission), so a blank screen guides instead of confuses.
npx skills add mohitagw15856/pm-claude-skills --skill empty-state-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Empty State Writer Skill An empty state is the most-missed onboarding moment: the user arrives and there's nothing there. Done well, it explains the value, removes confusion, and offers the one action that fills the screen. This skill writes empty states that teach and activate — not blank voids or generic "No data" labels. ## Working from a brief Given "the empty state for a projects list", **write it anyway** — infer why the screen is empty, the value of the feature, and the best first action, labelling assumptions. Cover the distinct empty-state *types* that apply. Never hand back a question instead of copy. ## Required Inputs Ask for these only if they aren't already provided (else infer and label): - **The screen/feature** — what normally lives here and its value to the user. - **Why it's empty** — first use, the user cleared/completed everything, a search/filter returned nothing, or no access. - **The primary action** — what you want them to do (create, connect, invite, import, adjust filters). - **Voice & constraints** — tone, and any space/illustration limits. ## Output Format ### Empty States: [screen] Write the relevant types (skip those that don't apply): - **First use
- Working from a brief
- Required Inputs
- Output Format
- Empty States: [screen]
- Quality Checks
- Anti-Patterns
- Based On
What does the empty-state-writer skill do?
Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (first-use, user-cleared, no-results, error/permission), so a blank screen guides instead of confuses.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill empty-state-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.