Writes failing tests first, establishing a strict implementation contract for test-driven development.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add am-will/codex-skills --skill tdd-test-writerCompatible with
Supported agents
Completes the RED phase of TDD by authoring behavior-focused tests that fail for the right reason, then hands off to implementation agents with objective pass criteria
Delegates test authoring to a tdd_test_writer subagent when available, ensuring tests remain unmodified during implementation
Detects existing test frameworks and conventions (pytest, jest, vitest, go test, cargo test
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontdd-test-writerExecute the skills CLI command in your project's root directory to begin installation:
epx add am-will/codex-skills --skill tdd-test-writerFetches tdd-test-writer from am-will/codex-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:
.cursor/skills/tdd-test-writer
Restart Cursor to activate tdd-test-writer. Access via /tdd-test-writerin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
frontend-design
am-will/codex-skills · Frontend · same repo
markdown-url
am-will/codex-skills · Productivity · same repo
seo-content-writer
aaron-he-zhu/seo-geo-claude-skills · Marketing · tag: writer
kids-book-writer
jamesrochabrun/skills · Productivity · tag: writer
docs-writer
google-gemini/gemini-cli · Documents · tag: writer
novel-writer-workflow-guide
wordflowlab/novel-writer-skills · Frontend · tag: writer
Solid pick for teams standardizing on skills: tdd-test-writer is focused, and the summary matches what you get after install.
Registry listing for tdd-test-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in tdd-test-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for tdd-test-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
We added tdd-test-writer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in tdd-test-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
tdd-test-writer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend tdd-test-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
tdd-test-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in tdd-test-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 50