Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cherryhq/gh-create-issue
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.
Passed 4 of 10 test cases with the skill, and 3 of 10 without it.
and 3 more in the full report
5 fixed4 passed either way11 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
The bug report template defines two labels: `bug` and `frontend`. Construct the `gh issue create` command for an issue titled `[Bug]: Button broken` using body file `/tmp/gh-issue-body-123456.md`.
| Checked | Without skill | With skill |
|---|---|---|
| Appends a separate --label flag for each label specified by the template | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the user requests to create an issue. Must follow the repository's issue template format.
Analyze the user's request to determine the issue type:
Engineering Task is not a GitHub issue form and is not offered to regular users. Only select it when the request clearly describes internal engineering work.
If unclear, ask the user which template to use. Do not default to "Others" on your own.
Engineering Task is meant for maintainers and collaborators with write access. This is a request,
not an access control — nothing prevents anyone from calling gh issue create directly, and this
skill does not try to. The check below is here so that a contributor without write access learns
that early and gets pointed somewhere more useful.
Before collecting any information, read the authenticated user's permission level:
repo="$(gh repo view --json nameWithOwner --jq .nameWithOwner)"
user="$(gh api user --jq .login)"
permission="$(gh api "repos/$repo/collaborators/$user/permission" --jq .permission 2>/dev/null)"
case "$permission" in
admin | write) echo "eligible" ;;
*) echo "not eligible" ;;
esac
Only admin and write are eligible (maintain reports as write). Always compare the returned
value: on a public repository this endpoint answers read for any user, including one who is not a
test cases passed, vs 3 / 10 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.