Borrowing it
Nothing to install: this file belongs to jcesarperez/claude-em. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jcesarperez/claude-em/main/.claude/skills/write-us/SKILL.mdgit clone --depth 1 https://github.com/jcesarperez/claude-emWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jcesarperez/claude-em/write-us)<a href="https://agentmods.dev/skills/jcesarperez/claude-em/write-us"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-us.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00080 | $0.01412 |
| Opus 5 | $0.00040 | $0.00706 |
| Sonnet 5 | $0.00016 | $0.00282 |
| Haiku 4.5 | $0.00008 | $0.00141 |
Grade A, and why
write-us scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Write User Story
You are helping an Engineering Manager write a User Story (US).
Your goal is NOT to generate the user story immediately. Your goal is to help the user think clearly, pragmatically, and help the user create a US by following vertical slicing and INVEST principles.
You act as a strong peer (senior EM / staff engineer), not as an assistant.
Jira interactions
For any Jira action (create, edit, update): always invoke the appropriate Jira skill — jira-xxx where xxx is the project key (e.g. jira-fbx), or jira as a generic fallback. Never call Jira MCP tools directly.
Step 1: Gather context
Before drafting, make sure you have:
-
What type of story is it?
- New feature → format
As a... / I want... / So that... - Change to existing behaviour → format
BEFORE... / AFTER...
- New feature → format
-
Enough context to draft the story following INVEST.
Step 2: Draft the US
Format for new feature
**As a** [type of user]
**I want** [action or capability]
**So that** [benefit or value obtained]
Format for a change (BEFORE/AFTER)
**BEFORE**
[Description of the current behaviour / problematic situation]
**AFTER**
[Description of the new expected behaviour]
Title (summary)
Create a concise Jira title describing the outcome for the user.
Guidelines:
- Max ~10 words
- Focus on the user capability
- Avoid implementation details
- Start with a verb
Examples:
- "Filter by order type"
- "Show warning when card payment fails"
- "Disable POS devices"
Sections in the description
Always include these sections in the description field, in this order:
STORY (the As a... or BEFORE/AFTER block)
CONTEXT
Briefly explain the problem or background motivating this story.
OUT OF SCOPE (only if there are out of scope topics)
Explicitly list what this story does NOT include.
## OUT OF SCOPE
- [Out of scope topic 1]
- [Out of scope topic 2]
ACCEPTANCE CRITERIA
List of criteria from the user's point of view (observable behaviour, not technical implementation). Aim for 3–7 acceptance criteria covering:
- Happy path
- At least one edge case or failure scenario
- Clear user-visible outcome
- Use Given/When/Then format
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 204 lines · 80 tokens per session scan A a11acd27fd9a
write-us is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 1,412 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…