Run tests for React codebase across multiple release channels and configurations.
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 facebook/react --skill testCompatible with
Supported agents
Supports six release channels: source (default), experimental, www, www with variant false, stable, and classic, each with distinct feature flag configurations
Accepts test patterns, watch mode for TDD, and variant flags to test different code paths
Requires explicit test pattern argument to avoid running the entire test suite; uses --silent flag to surface failures and --no-watchman for sandboxing comp
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontestExecute the skills CLI command in your project's root directory to begin installation:
epx add facebook/react --skill testFetches test from facebook/react 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/test
Restart Cursor to activate test. Access via /testin 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.
test-fixing
sickn33/antigravity-awesome-skills · Testing · tag: test
k6-load-test
dengineproblem/agents-monorepo · Testing · tag: test
alicloud-security-content-moderation-green-test
cinience/alicloud-skills · Cloud · tag: test
platform-detection
dotnet/skills · dotnet-test · tag: test
alicloud-security-id-verification-cloudauth-test
cinience/alicloud-skills · Cloud · tag: test
filter-syntax
dotnet/skills · dotnet-test · tag: test
test has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for test matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: test is the kind of skill you can hand to a new teammate without a long onboarding doc.
test reduced setup friction for our internal harness; good balance of opinion and flexibility.
test is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in test — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: test is focused, and the summary matches what you get after install.
test is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added test from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend test for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 33