New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitHub Issue Creator

by CherryHQ in CherryHQ/cherry-studio

Creates GitHub issues for the current repository by choosing the matching issue template and following its format, with a permission check for engineering tasks.

AGPL-3.0Auto-check passedDevelopment

Install GitHub Issue Creator

skills CLI
$ npx skills add CherryHQ/cherry-studio --skill gh-create-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CherryHQ/cherry-studio gh-create-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/gh-create-issue .claude/skills/gh-create-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gh-create-issue
GitHub stars
52k
Token cost
~1.6k tokens
SKILL.md length
773 words
Files
2 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Creates GitHub issues for the current repository by choosing the matching issue template and following its format, with a permission check for engineering tasks.

  • Works in 5 steps: Determine Template Type → Read the Selected Template → Collect Information → …
  • Filing a bug report in the current repository's GitHub issues
  • SKILL.md covers Workflow and Notes
  • Calls gh

What it does

The skill picks a template from what you describe: a bug report for problems, errors or crashes, a feature request for new features or enhancements, questions and discussion for help requests, an engineering task for internal work with no user-facing change, and otherwise others. If the type is unclear, the agent asks you instead of falling back to Others, and it follows the repository's own issue template format.

Engineering Task is not a GitHub issue form and is meant for maintainers with write access. Before collecting details, the agent reads the authenticated user's permission through the gh API. Only admin and write count, and it compares the returned value because a public repository reports read for anyone. Everyone else is pointed to a public template and offered help filing there. The skill states that the check is a courtesy and not an access control. A reference file describes the engineering task template.

When your agent uses it

  • Filing a bug report in the current repository's GitHub issues
  • Turning a feature idea into an issue that follows the template
  • Recording a deferred follow-up or technical debt as an engineering task

Example prompts

  • “Create an issue: the app crashes when I open settings after updating.”
  • “File a feature request for exporting chats as Markdown.”
  • “Open an engineering task for the refactor we deferred from the last PR.”

Requirements

  • GitHub CLI (gh), authenticated
  • A repository that defines issue templates

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Determine Template Type
  2. Read the Selected Template
  3. Collect Information
  4. Build and Preview Issue Content
  5. Create Issue

What it can do on your machine

Read from SKILL.md and the folder at commit dd0767e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Issue Creator loads about 1.6k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 37 tokens; SKILL.md has 773 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CherryHQ/cherry-studio at commit dd0767e, republished under its AGPL-3.0 licence (© CherryHQ). 773 words, ~1,586 tokens.

Download SKILL.mdSave it as .claude/skills/gh-create-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gh-create-issue
description
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.

GitHub Create Issue

Use this skill when the user requests to create an issue. Must follow the repository's issue template format.

Workflow

Step 1: Determine Template Type

Analyze the user's request to determine the issue type:

  • If the user describes a problem, error, crash, or something not working -> Bug Report
  • If the user requests a new feature, enhancement, or additional support -> Feature Request
  • If the user is asking a question or needs help with something -> Questions & Discussion
  • If the user describes engineering work with no user-facing behavior change (a follow-up deferred from a pull request, technical debt, refactoring, tooling or CI work) -> Engineering Task
  • Otherwise -> Others

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.

Eligibility Check (Engineering Task only)

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:

bash
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 collaborator at all, so a successful call proves nothing on its own. Do not use repos/{owner}/{repo}/collaborators/{user} here — it answers 204 for read- and triage-only collaborators, who are not the intended audience for this template.

If the result is anything else, do not use this template. Explain that it is meant for maintainers with write access, politely ask the contributor to use one of the public templates instead, and offer to help them file it there — their report is welcome, just not under this template. Do not quietly switch templates while keeping the Engineering Task labels or issue type.

Step 2: Read the Selected Template
  1. Read the corresponding template file from .github/ISSUE_TEMPLATE/ directory.
  2. Identify required fields (validations.required: true), title prefix (title), labels (labels, if present), and issue type (type, if present).

For Engineering Task, read references/engineering-task.md instead — it lives outside .github/ISSUE_TEMPLATE/ on purpose and carries its own title prefix, labels, issue type, and body structure.

Step 3: Collect Information

Based on the selected template, ask the user for required information only. Follow the template's required fields and option constraints (for example, Platform and Priority choices).

Show full SKILL.md (335 more words)Show less
Step 4: Build and Preview Issue Content

Create a temp file and write the issue content:

  • Use issue_body_file="$(mktemp /tmp/gh-issue-body-XXXXXX).md"
  • Use the exact title prefix from the selected template.
  • Fill content following the template body structure and section order.
  • Apply labels exactly as defined by the template.
  • Keep all labels when there are multiple labels.
  • If template has no labels, do not add custom labels.
  • Apply the issue type exactly as defined by the template's type field.

Preview the temp file content. Show the file path (e.g., /tmp/gh-issue-body-XXXXXX.md) and ask for confirmation before creating. Skip this step if the user explicitly indicates no preview/confirmation is needed (for example, automation workflows).

Step 5: Create Issue

Use gh issue create command to create the issue.

Use a unique temp file for the body:

bash
issue_body_file="$(mktemp /tmp/gh-issue-body-XXXXXX).md"
cat > "$issue_body_file" <<'EOF'
...issue body built from selected template...
EOF

Create the issue using values from the selected template:

bash
gh issue create --title "<title_with_template_prefix>" --body-file "$issue_body_file"

If the selected template includes labels, append one --label per label:

bash
gh issue create --title "<title_with_template_prefix>" --body-file "$issue_body_file" --label "<label_1_from_template>" --label "<label_2_from_template>"

If the selected template has no labels, do not pass --label.

If the selected template declares a type, pass it as well. --body-file does not carry the issue type over on its own, so omitting this leaves the issue untyped:

bash
gh issue create --title "<title_with_template_prefix>" --body-file "$issue_body_file" --type "<type_from_template>"

--template and --web resolve against .github/ISSUE_TEMPLATE/ on the default branch, so neither works for Engineering Task. Build the body locally for it.

For the other templates you may use --template as a starting point (use the exact template name from the repository):

bash
gh issue create --template "<template_name>"

Use the --web flag to open the creation page in browser when complex formatting is needed:

bash
gh issue create --web

Clean up the temp file after creation:

bash
rm -f "$issue_body_file"

Notes

  • Must read template files under .github/ISSUE_TEMPLATE/ (or references/ for Engineering Task) to ensure following the correct format.
  • Treat template files as the only source of truth. Do not hardcode title prefixes, labels, or issue types in this skill.
  • Title must be clear and concise, avoid vague terms like "a suggestion" or "stuck".
  • Provide as much detail as possible to help developers understand and resolve the issue.
  • If user doesn't specify a template type, ask them to choose one first.

© CherryHQ, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/gh-create-issue of CherryHQ/cherry-studio.

  • SKILL.md
  • references/engineering-task.md

Open the folder on GitHubat commit dd0767e

Compare with similar skills

GitHub Issue Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Issue Creator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issue Creator this skillCherryHQ/cherry-studio52k—~1.6kAutomated safety check: PassAGPL-3.0
Issue Fixmono/SkiaSharp5.6k—~5.1kAutomated safety check: PassMIT
Bug Report TriageOrchestratorInc/agent-orchestrator13k—~1.8kAutomated safety check: PassApache-2.0
OpenROAD Issue TriageThe-OpenROAD-Project/OpenROAD3.2k—~842Automated safety check: PassBSD-3-Clause
Community Triageroryeckel/wyoming_openai218—~2.9kAutomated safety check: PassApache-2.0
Handsontable Demo Page Generatorhandsontable/handsontable22k—~1.8kAutomated safety check: PassCustom licence

Similar skills

  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Bug Report Triage

    OrchestratorInc/agent-orchestrator

    Helps a reporter describe a bug, searches for duplicates and gathers diagnostic evidence kept separate from a short, human-worded issue draft.

    13k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • OpenROAD Issue Triage

    The-OpenROAD-Project/OpenROAD

    Reproduces an OpenROAD GitHub bug from an attached tarball and shrinks the failing design with whittle.py so maintainers get a minimal test case.

    3.2k GitHub stars~842 tokensUpdated today
    DevelopmentAuto-check passed

  • Community Triage

    roryeckel/wyoming_openai

    GitHub issues, pull requests, bug reports, scope questions, and support threads.

    218 GitHub stars~2.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Handsontable Demo Page Generator

    handsontable/handsontable

    Builds two throwaway HTML test pages for a Handsontable pull request, one on the released CDN version and one on the local build, to compare behavior side by side.

    22k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Prp Debug

    Wirasm/prp

    Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.

    2.3k GitHub stars~1.1k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

More from CherryHQ/cherry-studio

All 30 skills in this repo

  • Office File Transform

    CherryHQ/cherry-studio

    Derives new files from a selected part of a spreadsheet, Word document, PDF or slide deck, such as a cell range, paragraph, page or slide, without ever modifying the source file.

    52k GitHub stars~4.7k tokensUpdated today
    Auto-check passed

  • Cherry Studio PR Review

    CherryHQ/cherry-studio

    Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.

    52k GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Cherry Studio Regression Tests

    CherryHQ/cherry-studio

    Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.

    52k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Antigravity CLI Runner

    CherryHQ/cherry-studio

    Runs the Antigravity CLI headlessly with the agy command to analyze a repository or carry out a coding task, then checks its JSON result and the diff.

    52k GitHub stars~531 tokensUpdated today
    Auto-check passed

  • Kimi Code Delegation

    CherryHQ/cherry-studio

    Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.

    52k GitHub stars~504 tokensUpdated today
    Auto-check passed

  • GitHub PR Creation

    CherryHQ/cherry-studio

    Creates or updates GitHub pull requests by reading the repository's PR template, filling every section and picking the right base branch under its release rules.

    52k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about GitHub Issue Creator

What does GitHub Issue Creator do?

Creates GitHub issues for the current repository by choosing the matching issue template and following its format, with a permission check for engineering tasks. The skill picks a template from what you describe: a bug report for problems, errors or crashes, a feature request for new features or enhancements, questions and discussion for help requests, an engineering task for internal work with no user-facing change, and otherwise others. If the type is unclear, the agent asks you instead of falling back to Others, and it follows the repository's own issue template format.

When should I use GitHub Issue Creator?

GitHub Issue Creator fits situations like: filing a bug report in the current repository's GitHub issues; turning a feature idea into an issue that follows the template; recording a deferred follow-up or technical debt as an engineering task.

How do I install GitHub Issue Creator in Claude Code?

Run `npx skills add CherryHQ/cherry-studio --skill gh-create-issue -a claude-code`. Or copy the skill folder (.agents/skills/gh-create-issue in CherryHQ/cherry-studio) into .claude/skills/gh-create-issue in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Creator in Codex?

Run `npx skills add CherryHQ/cherry-studio --skill gh-create-issue -a codex`. Or copy the skill folder (.agents/skills/gh-create-issue in CherryHQ/cherry-studio) into .agents/skills/gh-create-issue in your project. Codex loads it when a task matches its description.

Can I use GitHub Issue Creator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CherryHQ/cherry-studio --skill gh-create-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-create-issue, .gemini/skills/gh-create-issue, .github/skills/gh-create-issue and .opencode/skills/gh-create-issue in your project.

What does GitHub Issue Creator need to run?

Going by SKILL.md and its folder, GitHub Issue Creator needs the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (gh), authenticated; A repository that defines issue templates.

Does GitHub Issue Creator access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Issue Creator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Issue Creator use?

GitHub Issue Creator is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issue Creator use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 579 tokens, read only when the agent opens those files.

What are the alternatives to GitHub Issue Creator?

Skills that share tags, products or a category with GitHub Issue Creator: Issue Fix (mono/SkiaSharp, 5.6k stars), Bug Report Triage (OrchestratorInc/agent-orchestrator, 13k stars), OpenROAD Issue Triage (The-OpenROAD-Project/OpenROAD, 3.2k stars) and Community Triage (roryeckel/wyoming_openai, 218 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Creator?

CherryHQ (a GitHub organization) maintains it in CherryHQ/cherry-studio, which has 52,407 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 7, 2026.

Source: CherryHQ/cherry-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.