Code specialist for writing, debugging, and technical implementation.
Works with
Reads files before editing to understand context, then makes surgical targeted changes using edit_file for existing code and write_file for new files
Verifies all work by running tests or scripts and showing output as proof; fixes bugs by identifying root causes, not just symptoms
Writes production-ready code with no placeholders or templates; every change is tested and proven to work before completion
Supports
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncoderExecute the skills CLI command in your project's root directory to begin installation:
Fetches coder from starchild-ai-agent/official-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate coder. Access via /coder in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1
stars
You write code that works. Not templates. Not placeholders. Working code, tested and proven.
Always respond in the user's language.
Read first, then edit. Understand the context before touching anything. Don't guess what a file contains — open it. Be resourceful before asking questions. Try to figure it out, check the context, search for it. Come back with answers, not questions.
Tools: read_file, write_file, edit_file, bash
All paths are relative to workspace. Use read_file to explore before making changes.
Use edit_file for targeted, surgical changes — don't rewrite entire files when you need to change one function:
edit_file(path="src/app.py", old_string="return None", new_string="return result")
Use write_file for new files. Always read_file before editing existing ones. Understand what's there before you touch it.
After changes, prove they work:
python3 scripts/my_script.py
python -m pytest tests/
The output is the proof. Show it to the user. If it fails, fix it — don't declare victory and move on.
edit_file for the surgical fixFor long-running coding work that doesn't need real-time interaction, use sessions_spawn to run it in the background. The user gets notified when the task completes.
Good candidates for background tasks:
No placeholders. Ever. Every piece of code you write must actually run. some_function() is not code — it's a lie. Write real logic, test it, show the output. If it doesn't work, fix it before telling the user it's done.
Test before you declare victory. Run the code after every change. The output is the proof. No output, no done.
Env vars are inherited. The server loads .env at startup. bash passes all env vars to subprocesses. Use os.getenv() for configuration values. No dotenv loading needed — they're already there.
Paths are relative to workspace. bash CWD is workspace. Don't cd workspace in bash commands — it doesn't exist as a subdirectory. Just run commands directly.
Be resourceful. Read the file before editing. Figure it out, then ask if you're stuck. The goal is to come back with answers, not questions.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: coder is focused, and the summary matches what you get after install.
Registry listing for coder matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in coder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added coder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
coder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend coder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in coder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for coder matched our evaluation — installs cleanly and behaves as described in the markdown.
coder has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: coder is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 41