github-issue-creator
Github Issue Creator - Auto-activating skill for Enterprise Workflows. Triggers on: github issue creator, github issue creator Part of the Enterprise Workflows skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/github-issue-creator/SKILL.mdQuality
Discovery
7%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 description is extremely weak, essentially just restating the skill name with boilerplate auto-generated text. It provides no concrete actions, no meaningful trigger terms, and no explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other GitHub-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates GitHub issues with titles, descriptions, labels, assignees, and milestones via the GitHub API.'
Add a 'Use when...' clause with natural trigger terms like 'create a GitHub issue', 'open an issue', 'file a bug report', 'submit a feature request', 'new issue on GitHub'.
Remove the duplicated trigger term and the generic 'Auto-activating skill for Enterprise Workflows' boilerplate, replacing it with meaningful capability and context information.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Github Issue Creator') but does not describe any concrete actions like creating issues, adding labels, assigning users, or setting milestones. It relies on the skill name alone rather than listing specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is essentially just the skill name repeated as a trigger phrase. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'github issue creator' repeated twice. It misses natural user phrases like 'create a GitHub issue', 'open an issue', 'file a bug', 'submit a feature request', or 'GitHub issues'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Github Issue Creator' provides some specificity to GitHub issues rather than generic document or code tasks, but the lack of detail about what it actually does (vs. other GitHub-related skills like issue management, PR creation, etc.) creates potential overlap. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual instructional content. It repeatedly names the skill topic ('github issue creator') without providing any concrete guidance, code examples, API usage, or workflow steps. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples showing how to create GitHub issues (e.g., using the GitHub CLI `gh issue create` or the GitHub REST/GraphQL API with curl or Python requests).
Define a clear workflow with steps: gather issue details, format the payload, create the issue via API/CLI, validate the response, and handle errors.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe meta-information about the skill rather than teaching how to perform the task.
Include a concrete example with sample input (issue title, body, labels, assignees) and expected output (API response or CLI output) to make the skill actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'github issue creator' excessively, and contains no actual technical content or instructions. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no API calls, no example payloads, no GitHub CLI usage. Every section describes what the skill supposedly does without actually instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Claims to provide 'step-by-step guidance' but none is present. There are no sequences, no validation checkpoints, and no actual process described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no linked resources, and no structured navigation. It mentions 'Related Skills' but provides no actual links or file references. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
dc559db
- 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.