Ears Translator
Translate user stories and informal requirements into EARS (Easy Approach to Requirements Syntax) format. Use when Claude needs to (1) convert user stories to formal requirements, (2) transform informal requirements into structured EARS format, (3) review and improve existing requirements using EARS patterns, (4) create testable, unambiguous system requirements. Triggers on requests like "convert to EARS", "write requirements", "formalize these user stories", "EARS format".
Install
npx skills add UserAd/ClaudeSkills --skill ears-translatorgit clone --depth 1 https://github.com/UserAd/ClaudeSkills.git /tmp/ClaudeSkills
mkdir -p ~/.claude/skills
cp -r /tmp/ClaudeSkills/skills/ears-translator ~/.claude/skills/ears-translatorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# EARS Requirements Translator Translate user stories and informal requirements into precise, testable EARS format requirements. ## Workflow ### Step 1: Gather Requirements Read all stories and requirements provided by user. Identify: - The system/component being specified - Functional behaviors described - Conditions, triggers, and states mentioned - Error scenarios and edge cases ### Step 2: Ask Clarification Questions Use AskUserQuestion to clarify ambiguities. Common questions: - What is the exact system/component name? - What are the specific thresholds or timing requirements? - Are there error conditions to handle? - Is this an optional feature or always present? Continue until at least 90% confident about requirements. ### Step 3: Select Output Format Ask user preference: - **Individual REQs**: Each requirement listed separately with IDs (REQ-001, REQ-002...) - **Grouped by feature**: Requirements organized under feature headings ### Step 4: Transform to EARS Apply the appropriate EARS pattern for each requirement. See `references/ears-patterns.md` for pattern details. **Requirement Splitting:** Always attempt to split compound requirements into individual atomic requirements: - If a requirement mentions multiple tools (e.g., "RSpec and Rubocop"), create separate requirements for each - If a requirement mentions multiple services or components, create separate requirements for each
Details
- Skill name
ears-translator- Repository
- UserAd/ClaudeSkills
- Path
skills/ears-translator/SKILL.md- Repo updated
- 29 July 2026
FAQ
What does the Ears Translator skill do?
Translate user stories and informal requirements into EARS (Easy Approach to Requirements Syntax) format. Use when Claude needs to (1) convert user stories to formal requirements, (2) transform informal requirements into structured EARS format, (3) review and improve existing requirements using EARS patterns, (4) create testable, unambiguous system requirements. Triggers on requests like "convert to EARS", "write requirements", "formalize these user stories", "EARS format".
How do I install the Ears Translator skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add UserAd/ClaudeSkills --skill ears-translator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Ears Translator popular?
It lives in UserAd/ClaudeSkills, which has 8 GitHub stars and 0 forks.
Related skills
Architecture
8UserAd/ClaudeSkills
Manage architecture documentation in .architecture directory. Use when Claude needs to (1) create/update/delete architecture artifacts (domains, services, contracts, schemas), (2) validate architecture documentation, (3) query service dependencies or technology status, (4) document new services or domains, (5) work with RabbitMQ/Redis/PostgreSQL/ClickHouse/MongoDB/HTTP contracts. Triggers on "architecture", "add service", "add domain", "document service", "create contract", "validate architecture".
Codex Assistant
8UserAd/ClaudeSkills
Run AI-powered tasks using OpenAI Codex CLI. Use when Claude needs to (1) delegate code analysis or generation tasks to Codex, (2) get a second opinion on code changes, (3) perform parallel AI review, or (4) leverage Codex for specific tasks. Triggers on requests like "use codex to...", "run codex", "ask codex", "codex review".
Kamailio Config
8UserAd/ClaudeSkills
Kamailio SIP server configuration and troubleshooting. Use when Claude needs to: (1) Edit or create Kamailio configuration files (.cfg) (2) Debug SIP routing logic (request_route, failure_route, reply_route) (3) Work with Kamailio pseudo-variables ($ru, $fU, $avp, $xavp, $dlg_var) (4) Configure modules (tm, dialog, acc, sqlops, jansson, http_client, rr, sl, mqueue, rtimer) (5) Understand SIP message flow and transaction handling (6) Validate configuration syntax Triggers: "kamailio", "SIP routing", "kamailio.cfg", SIP-related pseudo-variables
Qpu Submit
9pasqal-io/agent-marketplace
Submit a neutral-atom experiment_spec.json plus its Pulser sequence file to a Rydberg QPU on Pasqal Cloud, with an optional pre-calibration batch that measures the device's Rabi frequency and Rydberg resonance and compensates the submitted jobs. Writes batch IDs for harvest-and-analyze. For a QPU reached over SSH through a cluster scheduler, use submit-to-cea. Triggered by phrases like "submit this spec to the QPU", "run this sequence on Fresnel", "send it to the neutral-atom hardware".
Ugc Repurposer
8lemonhall/influencer-marketing-claude-skills
Transforms influencer content into multiple formats for use across channels including ads, website, email, and social. Maximizes the value of every piece of content created.
Spec to Sequence
9pasqal-io/agent-marketplace
Generate a Pulser sequence builder for a neutral-atom (Rydberg) experiment from an experiment_spec.json. Output is a *_sequence.py with two standardised functions — build_sequence() and compute_observable() — consumed by validate-emu, qpu-submit and harvest-and-analyze. Triggered by phrases like "generate the Pulser sequence", "write the sequence file for this spec", "spec to sequence", "turn the spec into Pulser code".
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.