Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Shoebtamboli/rails_claude_skills --skill refine-requirementsgit clone --depth 1 https://github.com/Shoebtamboli/rails_claude_skillsWrote 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/shoebtamboli/rails_claude_skills/refine-requirements)<a href="https://agentmods.dev/skills/shoebtamboli/rails_claude_skills/refine-requirements"><img src="https://agentmods.dev/badge/skills/shoebtamboli/rails_claude_skills/refine-requirements/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shoebtamboli/rails_claude_skills/refine-requirements"><img src="https://agentmods.dev/badge/skills/shoebtamboli/rails_claude_skills/refine-requirements.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.01454 |
| Opus 5 | $0.00029 | $0.00727 |
| Sonnet 5 | $0.00012 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
refine-requirements 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 12d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refine Requirements Skill
Ask targeted follow-up questions to clarify ambiguous requirements and update implementation tasks based on the answers. Used after initial feature planning to ensure comprehensive understanding before coding.
When to Use This Skill
Use this skill when:
- After running
/plan-featureand need more clarity - User says "I need to clarify some things"
- Requirements seem ambiguous or incomplete
- User mentions "refine", "more details", "questions"
- Before starting implementation to reduce rework
Instructions
Follow these steps to refine requirements:
Step 1: Understand Current Context
First, gather context about what's been planned:
- Check if TodoWrite has active tasks (indicates planning already happened)
- If tasks exist, read them to understand the feature scope
- If no tasks, ask user: "What feature are you refining requirements for?"
Present current understanding:
I can see you're planning [feature name] with [N] tasks. Let me ask some clarifying questions to refine the requirements.
Step 2: Identify Gaps and Ambiguities
Analyze the current plan for common gaps:
Data/Schema Questions:
- Missing field validations or constraints
- Unclear relationships or associations
- Missing indexes or performance considerations
- Data migration or seeding needs
Business Logic Questions:
- Edge cases not covered
- Validation rules unclear
- State transitions undefined
- Authorization rules ambiguous
UI/UX Questions:
- User workflows incomplete
- Error handling unclear
- Success/failure states undefined
- Mobile vs desktop behavior
Technical Questions:
- Performance requirements unclear
- Caching strategy undefined
- Background job needs
- Real-time updates needed?
- API requirements
Step 3: Ask Targeted Questions
Use AskUserQuestion to ask 3-5 focused questions based on the feature type.
Question selection strategy:
- Refer to reference.md for question templates by feature type
- Prioritize questions that will change implementation significantly
- Focus on gaps that could cause rework later
- Avoid questions already answered in the plan
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 227 lines · 58 tokens per session scan A 0197430e0a07
refine-requirements is a skill published in the GitHub repository Shoebtamboli/rails_claude_skills (16 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 1,454 once invoked, about $0.0003 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
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".