github-issue-creator
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue. Supports images/GIFs for visual evidence.
Install with Tessl CLI
npx tessl i github:microsoft/agent-skills --skill github-issue-creatorOverall
score
99%
Does it follow best practices?
Validation 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 an excellent skill description that hits all the marks. It clearly specifies concrete capabilities (converting various input types to GitHub issues), includes natural trigger terms users would actually say, explicitly states when to use it, and carves out a distinct niche that won't conflict with general markdown or documentation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports' and 'Supports images/GIFs for visual evidence' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Convert raw notes...into GitHub-flavored markdown issue reports') AND when ('Use when the user pastes bug info, error messages, or informal descriptions and wants a structured GitHub issue') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'raw notes', 'error logs', 'voice dictation', 'screenshots', 'bug info', 'error messages', 'informal descriptions', 'GitHub issue', 'images/GIFs'. These match how users naturally describe their needs. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub issue creation from unstructured input. The combination of input types (notes, logs, dictation, screenshots) and output format (GitHub-flavored markdown issues) creates a distinct, non-conflicting scope. | 3 / 3 |
Total | 12 / 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 teaches Claude to transform unstructured input into structured GitHub issues. It excels at providing concrete examples showing the transformation process, clear severity guidelines, and a complete template without any unnecessary explanation. The two input→output examples effectively demonstrate handling different input types (voice dictation vs error paste).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what GitHub issues are or how markdown works. Every section serves a purpose and the template is minimal yet complete. | 3 / 3 |
Actionability | Provides a complete, copy-paste ready template with concrete examples showing input→output transformations. The guidelines are specific (severity definitions, naming conventions, placeholder formats) rather than vague. | 3 / 3 |
Workflow Clarity | For this single-task skill, the workflow is unambiguous: receive messy input → apply template → output to /issues/ with specified naming. The guidelines section provides clear decision criteria for severity and handling edge cases. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (template, output location, guidelines, examples). At ~80 lines, it's appropriately self-contained without needing external references. Content flows logically from template to guidelines to examples. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.