Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/create-issue
Create a GitHub issue with a drafted title and body.
Passed 2 of 9 test cases with the skill, and 5 of 9 without it.
2 fixed4 passed either way9 still failing7 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to draft an issue for a broken navigation link. We want to store the temporary draft body in a file with a unique random hex identifier across sessions before running gh issue create. Which shell command produces this random hex prefix?
| Checked | Without skill | With skill |
|---|---|---|
| Generates four random bytes using head -c 4 /dev/urandom piped to xxd -p | Missed | Passed |
The instructions your model reads when the skill loads.
Draft a focused title and body for a GitHub issue, then file it. Bug reports state reproduction steps and observed versus expected behavior.
Determine what the issue is about from the conversation. When the subject is ambiguous, use request_user_input to settle it before drafting.
List the repo's issue templates, read its labels, and search for an existing issue covering the same thing:
ls .github/ISSUE_TEMPLATE/ 2>/dev/null
gh label list --limit 100
gh issue list --search "<keywords>" --state all
Treat an empty listing as normal. When templates exist, read the one matching the issue type, and read .github/ISSUE_TEMPLATE/config.yml when present. Follow the template's structure and required sections, and apply the labels and title prefix the template declares. For a YAML issue form, render each field's attributes.label as a ### heading with the answer beneath, matching what the web form produces. When config.yml sets blank_issues_enabled: false, choose a template rather than filing a blank issue.
When the search surfaces a plausible duplicate, present it and use request_user_input to confirm whether to file anyway.
$github-voice SkillRun the $github-voice skill to load writing style rules.
Draft the title and body. Output them as chat text so the user can review before anything is filed.
Use request_user_input for confirmation only. Generate a random tag so the body file is unique across sessions:
head -c 4 /dev/urandom | xxd -p
Write the drafted body to .turbo/issue/<tag>-body.md (using the printed tag) with apply_patch, then create the issue with gh issue create --body-file:
gh issue create --title "<TITLE>" --body-file .turbo/issue/<tag>-body.md --label "<LABEL>,<LABEL>"
test cases passed, vs 5 / 9 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.