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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill github-issue-creatorActivation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or providing natural trigger terms. The duplicate trigger term and boilerplate 'Auto-activating skill' language add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Creates GitHub issues with titles, descriptions, labels, and assignees from natural language requests'
Include a 'Use when...' clause with natural trigger terms like 'create issue', 'open ticket', 'file bug', 'report problem on GitHub', 'new issue'
Remove the duplicate trigger term and boilerplate category text; replace with concrete capability descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Github Issue Creator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating issues, adding labels, assigning users, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('github issue creator, github issue creator' - duplicated) and overly specific to the skill name itself rather than natural user language like 'create issue', 'open ticket', 'file bug', or 'github bug report'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Github Issue' focus provides some specificity that distinguishes it from generic document or code skills, but without describing actual capabilities, it could conflict with other GitHub-related skills (PR creation, issue management, etc.). | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what the skill claims to do without any concrete guidance, code examples, or actionable steps for creating GitHub issues. The content fails on all dimensions by providing zero executable information.
Suggestions
Add concrete, executable code examples showing how to create GitHub issues using the GitHub API or CLI (e.g., `gh issue create --title 'Bug' --body 'Description'`)
Define a clear workflow with specific steps: 1) gather issue details, 2) format the issue body, 3) create via API/CLI, 4) verify creation succeeded
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual issue templates or field specifications
Include example inputs and outputs showing what a well-formed GitHub issue looks like with title, body, labels, and assignees
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual GitHub issue creation. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for creating GitHub issues. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic marketing-style text with no structure pointing to detailed materials, no references to other files, and no organized sections with actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 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.