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 no concrete actions, no meaningful trigger terms, and no explicit guidance on when to use it. The auto-generated boilerplate ('Auto-activating skill for Enterprise Workflows') adds no useful information for skill selection. It would be nearly indistinguishable from other GitHub-related skills and would fail to activate on natural user requests.
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', 'GitHub ticket'.
Remove the duplicated trigger term and the generic 'Enterprise Workflows' boilerplate, replacing them with meaningful context about what distinguishes this skill from other GitHub-related skills.
| 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 ticket'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Github Issue Creator' provides some specificity to GitHub issues, which narrows the domain somewhat. However, the lack of detail about what specifically it does (vs. other GitHub-related skills) and the generic 'Enterprise Workflows' category label reduce distinctiveness. | 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 with no actual content. It contains only boilerplate descriptions and repeated mentions of 'github issue creator' without any actionable guidance, executable code, workflow steps, or references. It provides zero value beyond what Claude already knows.
Suggestions
Add concrete, executable examples using the GitHub CLI (`gh issue create`) or the GitHub REST/GraphQL API with actual code snippets showing issue creation with title, body, labels, and assignees.
Define a clear workflow: e.g., 1) gather issue details, 2) validate required fields, 3) create issue via API/CLI, 4) confirm creation and return issue URL.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching how to perform the task.
Include a concrete example showing input (user request) mapped to output (the actual `gh` command or API call with a sample JSON payload).
| 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 substantive information about actually creating GitHub issues. | 1 / 3 |
Actionability | There are zero concrete instructions, no code, no API calls, no commands, no examples of issue payloads or GitHub CLI usage. Every section is vague and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. There is nothing to progressively disclose. | 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
3a2d27d
- 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.