file-test-bug
File a GitHub issue for local integration test failures. TRIGGERS: file test bug, report test failure, create bug for test, integration test failed, test failure issue, junit failure
93
95%
Does it follow best practices?
Impact
81%
2.02xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid, focused skill description that clearly defines a narrow task (filing GitHub issues for test failures) with excellent trigger term coverage. The main weakness is that the 'what' portion could be more detailed about the specific actions involved (e.g., parsing test output, formatting the issue, attaching logs). Overall it performs well for skill selection purposes.
Suggestions
Expand the capability description to list more specific actions, e.g., 'Parses test output, creates a formatted GitHub issue with reproduction steps, attaches relevant logs and stack traces for local integration test failures.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub issues, integration test failures) and the core action (file an issue), but only describes a single action rather than listing multiple concrete capabilities like analyzing logs, formatting reproduction steps, or attaching test output. | 2 / 3 |
Completeness | Clearly answers both 'what' (file a GitHub issue for local integration test failures) and 'when' (explicit TRIGGERS list with six specific trigger phrases). The trigger guidance is explicit and actionable. | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms that users would actually say: 'file test bug', 'report test failure', 'create bug for test', 'integration test failed', 'test failure issue', 'junit failure'. These cover multiple natural phrasings and variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: filing GitHub issues specifically for local integration test failures. The combination of 'GitHub issue' + 'integration test failures' + 'junit' creates a distinct scope unlikely to conflict with general GitHub or general testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that is concise, actionable, and well-structured. It provides a clear multi-step workflow with an explicit validation checkpoint (diagnosis before issue creation), concrete file paths and tool references, and a detailed issue template. The 'Important' section at the end reinforces a critical constraint about not truncating logs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose—no unnecessary explanations of what GitHub issues are, what JUnit is, or how test frameworks work. It assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides concrete, specific guidance: exact file paths (tests/reports/junit.xml), exact MCP tool name (github-mcp-server-create_issue), exact repo/owner, exact issue template with field-level detail, and specific labels. The issue body template is copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced. Step 6 is explicitly marked as REQUIRED and must happen BEFORE step 7 (creating the issue), which is a validation/analysis checkpoint preventing premature issue filing. The diagnosis step includes a feedback loop of analyzing root cause before acting. | 3 / 3 |
Progressive Disclosure | For a skill of this size and scope (~50 lines, single-purpose task), the content is well-organized with clear sections (Input, Steps, Important). No external references are needed, and the structure is easy to scan and follow. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/github-copilot-for-azure
- Commit
a46a937
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.