Source profileQuality 74/100

CherryHQ/cherry-studio/.agents/skills/gh-create-issue/SKILL.md

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.

Source repository stars
49,062
Declared platforms
0
Static risk flags
2
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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

Best for

  • Use when user wants to create a GitHub issue for the current repository.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/gh-create-issue"
Safe inspection promptEditorial

Inspect the Agent Skill "gh-create-issue" from https://github.com/CherryHQ/cherry-studio/blob/dda7cc99d730c36bde685bec586dafe458722a4d/.agents/skills/gh-create-issue/SKILL.md at commit dda7cc99d730c36bde685bec586dafe458722a4d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    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 h…

    If the user describes a problem, error, crash, or something not working - Bug ReportIf the user requests a new feature, enhancement, or additional support - Feature RequestIf the user is asking a question or needs help with something - Questions & Discussion
  2. 02

    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 h…

    If the user describes a problem, error, crash, or something not working - Bug ReportIf the user requests a new feature, enhancement, or additional support - Feature RequestIf the user is asking a question or needs help with something - Questions & Discussion
  3. 03

    Step 2: Read the Selected Template

    1. Read the corresponding template file from .github/ISSUETEMPLATE/ directory. 2. Identify required fields (validations.required: true), title prefix (title), and labels (labels, if present).

    Read the corresponding template file from .github/ISSUETEMPLATE/ directory.Identify required fields (validations.required: true), title prefix (title), and labels (labels, if present).1. Read the corresponding template file from .github/ISSUETEMPLATE/ directory. 2. Identify required fields (validations.required: true), title prefix (title), and labels (labels, if present).
  4. 04

    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).

    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).

Permission review

Static risk signals and limitations

Writes files

medium · line 3

The documentation asks the agent to create, modify, or delete local files.

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

Reads files

low · line 19

The documentation asks the agent to read local files, directories, or repositories.

Read the corresponding template file from `.github/ISSUE_TEMPLATE/` directory.

Writes files

medium · line 28

The documentation asks the agent to create, modify, or delete local files.

Create a temp file and write the issue content:

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score74/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars49,062SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
CherryHQ/cherry-studio
Skill path
.agents/skills/gh-create-issue/SKILL.md
Commit
dda7cc99d730c36bde685bec586dafe458722a4d
License
AGPL-3.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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
  • Otherwise -> Others

If unclear, ask the user which template to use. Do not default to "Others" on your own.

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), and labels (labels, if present).

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).

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.

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:

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:

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

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

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.

You may use --template as a starting point (use the exact template name from the repository):

gh issue create --template "<template_name>"

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

gh issue create --web

Clean up the temp file after creation:

rm -f "$issue_body_file"

Notes

  • Must read template files under .github/ISSUE_TEMPLATE/ to ensure following the correct format.
  • Treat template files as the only source of truth. Do not hardcode title prefixes or labels 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.

Alternatives

Compare before choosing