A lightweight CLI tool for comparing coding agents head-to-head on reproducible tasks. Every "which coding agent is best?" comparison runs on vibes — this tool systematizes it.
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
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
Submit your Claude Code skill and start earning
epx add affaan-m/everything-claude-code --skill agent-evalCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionagent-evalExecute the skills CLI command in your project's root directory to begin installation:
epx add affaan-m/everything-claude-code --skill agent-evalFetches agent-eval from affaan-m/everything-claude-code 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:
.cursor/skills/agent-eval
Restart Cursor to activate agent-eval. Access via /agent-evalin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
agent-browser
vercel-labs/agent-browser · Productivity · tag: agent
agent-reach
panniantong/agent-reach · Productivity · tag: agent
write-a-skill
mattpocock/skill · other · tag: agent
brand-name-generator
shipshitdev/library · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
smart-ocr
claude-office-skills/skills · Productivity · same category
Registry listing for agent-eval matched our evaluation — installs cleanly and behaves as described in the markdown.
agent-eval has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend agent-eval for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: agent-eval is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in agent-eval — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
agent-eval reduced setup friction for our internal harness; good balance of opinion and flexibility.
agent-eval has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: agent-eval is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend agent-eval for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
agent-eval reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 44