E2E tests use Playwright. Located in apps/examples/e2e/ (SDK examples) and apps/dotcom/client/e2e/ (tldraw.com).
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 tldraw/tldraw --skill write-e2e-testsCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwrite-e2e-testsExecute the skills CLI command in your project's root directory to begin installation:
epx add tldraw/tldraw --skill write-e2e-testsFetches write-e2e-tests from tldraw/tldraw 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/write-e2e-tests
Restart Cursor to activate write-e2e-tests. Access via /write-e2e-testsin 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.
write-unit-tests
tldraw/tldraw · Testing · same repo
write-a-skill
mattpocock/skills · Productivity · tag: write
symfony:api-platform-tests
makfly/superpowers-symfony · Backend · tag: tests
playwright-generate-test
github/awesome-copilot · Testing · same category
flutter-testing
flutter/skills · Testing · same category
pytest-patterns
manutej/luxor-claude-marketplace · Testing · same category
We added write-e2e-tests from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: write-e2e-tests is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend write-e2e-tests for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
write-e2e-tests is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in write-e2e-tests — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: write-e2e-tests is focused, and the summary matches what you get after install.
write-e2e-tests is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
write-e2e-tests fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
write-e2e-tests has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added write-e2e-tests from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 32