issue-report-generator
Automatically generate clear, actionable issue reports from failing tests and repository analysis. Analyze test failures to understand expected vs. actual behavior, identify affected code components, and produce well-structured Markdown reports suitable for GitHub Issues or similar trackers. Use when a test fails, when debugging issues, or when the user asks to create an issue report, generate a bug report, or document a test failure.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill issue-report-generator80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly addresses both what the skill does and when to use it, and carves out a distinct niche around test failure analysis and issue report generation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generate clear, actionable issue reports', 'Analyze test failures to understand expected vs. actual behavior', 'identify affected code components', and 'produce well-structured Markdown reports'. These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what (generate issue reports from failing tests, analyze failures, identify affected code, produce Markdown reports) AND when with explicit 'Use when...' clause covering multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'test fails', 'debugging issues', 'create an issue report', 'generate a bug report', 'document a test failure', 'GitHub Issues'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test failure analysis and issue report generation. The combination of 'failing tests', 'issue reports', and 'bug report' creates a distinct trigger profile unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable examples and templates for generating issue reports, but is severely over-engineered with verbose explanations of concepts Claude inherently understands (debugging, Markdown formatting, reading stack traces). The workflow is clear but lacks integrated validation steps, and much of the detailed content should be moved to reference files to improve token efficiency.
Suggestions
Reduce the 5-step workflow to a concise checklist format, removing explanations of basic concepts like 'what is an exception' or 'how to read a stack trace'
Move the detailed examples (Examples 1-4) to a separate examples.md file, keeping only one brief example inline
Integrate the quality checklist as a validation step within the workflow (e.g., 'Step 6: Validate report against checklist before finalizing')
Remove sections explaining Markdown formatting and developer-friendly language - Claude knows these already
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (how to analyze stack traces, what exceptions are, how to format Markdown). The 5-step workflow with detailed sub-bullets explains basic debugging and documentation practices that don't need this level of detail. | 1 / 3 |
Actionability | Provides excellent concrete examples with complete, copy-paste ready Markdown report templates. The four detailed examples (NullPointerException, Assertion Failure, Timeout, Integration Failure) show exact input/output patterns that are immediately usable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced, but lacks validation checkpoints. There's no feedback loop for verifying report quality before submission, and the quality checklist at the end is disconnected from the workflow rather than integrated as a validation step. | 2 / 3 |
Progressive Disclosure | References report_patterns.md appropriately, but the main file is bloated with content that could be in reference files (the extensive examples, the detailed workflow steps). The quick template selection table is good, but too much detail is inline. | 2 / 3 |
Total | 8 / 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.