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
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill file-test-bug93
Does it follow best practices?
Evaluation — 81%
↑ 2.02xAgent success when using this skill
Validation for skill structure
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 well-crafted skill description with excellent trigger term coverage and clear distinctiveness. The explicit TRIGGERS section effectively communicates when to use this skill. The main weakness is limited specificity about what actions the skill performs beyond the basic 'file an issue' - it could benefit from mentioning specific capabilities like parsing JUnit output or formatting the issue.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub issues, integration test failures) and the action (file an issue), but doesn't list multiple concrete actions or elaborate on what the skill actually does beyond filing an issue. | 2 / 3 |
Completeness | Clearly answers both what (file a GitHub issue for local integration test failures) and when (explicit TRIGGERS section with multiple trigger phrases). The trigger list serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'file test bug', 'report test failure', 'create bug for test', 'integration test failed', 'test failure issue', 'junit failure' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: GitHub issues specifically for local integration test failures. The combination of 'GitHub issue' + 'integration test' + 'failure' creates a distinct trigger profile unlikely to conflict with general issue filing 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 well-crafted skill that efficiently guides Claude through filing test bug issues. It provides concrete paths, tool names, and a complete issue template while maintaining a clear workflow with an explicit diagnosis checkpoint before issue creation. The 'Important' section appropriately emphasizes a critical constraint about preserving log contents.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable guidance including specific file paths, exact MCP tool name, complete issue template with placeholders, and explicit labels. The template is copy-paste ready with clear field substitutions. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoint (step 6 marked as REQUIRED). The diagnosis step before issue creation serves as a validation/analysis gate, and the workflow handles the multi-step process of gathering data, analyzing, then creating the issue. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Input, Steps, Important). For a skill of this scope (~50 lines, single focused task), the structure is appropriate without needing external file references. The issue template is appropriately inline as it's the core deliverable. | 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.
- 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.