Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.
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 microsoft/github-copilot-for-azure --skill file-test-bugCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfile-test-bugExecute the skills CLI command in your project's root directory to begin installation:
epx add microsoft/github-copilot-for-azure --skill file-test-bugFetches file-test-bug from microsoft/github-copilot-for-azure 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/file-test-bug
Restart Cursor to activate file-test-bug. Access via /file-test-bugin 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.
markdown-token-optimizer
microsoft/github-copilot-for-azure · Productivity · same repo
playwright-generate-test
github/awesome-copilot · Testing · tag: test
file-name-wizard
cygnusfear/agent-skills · Productivity · tag: file
api-fuzzing-for-bug-bounty
sickn33/antigravity-awesome-skills · Backend · tag: bug
dotnet-test-frameworks
dotnet/skills · dotnet-test · tag: test
coverage-analysis
dotnet/skills · dotnet-test · tag: test
Solid pick for teams standardizing on skills: file-test-bug is focused, and the summary matches what you get after install.
file-test-bug is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
file-test-bug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in file-test-bug — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for file-test-bug matched our evaluation — installs cleanly and behaves as described in the markdown.
file-test-bug has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 34