Weavebench Cua Reproduce
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
Files Cherry Studio bug reports and feature requests as GitHub Issues after a duplicate check and your confirmation, or saves them locally when GitHub is not signed in.
SKILL.md written in Chinese; this summary is our English description.
Install Cherry Studio GitHub Issue Reporter
$ npx skills add CherryHQ/cherry-studio --skill issue-reporter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CherryHQ/cherry-studio issue-reporter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter .claude/skills/issue-reporter && rm -rf skills-srcUse ~/.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/
Install the "issue-reporter" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter into .claude/skills/issue-reporter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporterType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CherryHQ/cherry-studio --skill issue-reporter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CherryHQ/cherry-studio issue-reporter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter .agents/skills/issue-reporter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-reporter" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter into .agents/skills/issue-reporter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CherryHQ/cherry-studio --skill issue-reporter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CherryHQ/cherry-studio issue-reporter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter .cursor/skills/issue-reporter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-reporter" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter into .cursor/skills/issue-reporter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CherryHQ/cherry-studio.git --path resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CherryHQ/cherry-studio --skill issue-reporter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CherryHQ/cherry-studio issue-reporter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter .gemini/skills/issue-reporter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-reporter" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter into .gemini/skills/issue-reporter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CherryHQ/cherry-studio issue-reporterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CherryHQ/cherry-studio --skill issue-reporter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter .github/skills/issue-reporter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-reporter" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter into .github/skills/issue-reporter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CherryHQ/cherry-studio --skill issue-reporter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CherryHQ/cherry-studio issue-reporter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter .opencode/skills/issue-reporter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-reporter" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter into .opencode/skills/issue-reporter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-reporter- GitHub stars
- 52k
- Token cost
- ~335 tokens
- SKILL.md length
- 76 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Files Cherry Studio bug reports and feature requests as GitHub Issues after a duplicate check and your confirmation, or saves them locally when GitHub is not signed in.
- Filing a bug as a GitHub Issue on the Cherry Studio repository
- SKILL.md covers 触发边界, 检测 GitHub 登录, GitHub 模式 and 本地模式, plus 1 more section
- Calls gh
- Submitting a feature request through the repository's issue template
What it does
This skill, written in Chinese, files bug reports and feature requests for the Cherry Studio repository, and it only runs when you explicitly ask for a GitHub Issue. Generic phrases such as submit feedback or report a bug are not enough; those go to the `cherry-studio-feedback` skill instead, and no GitHub command is run. When it does run, it first checks `gh auth status` to choose between GitHub mode and local mode.
In GitHub mode a bug report collects the description, reproduction steps, expected behavior, platform and version, searches open issues for duplicates, reads the repository's bug template, shows you a preview and runs `gh issue create` only after you confirm, then returns the link. Feature requests follow the same path with the feature template and are also logged to a local `feature-requests.md` file. In local mode, reports are saved to `bug-reports.md` or `feature-requests.md` under `.cherry-assistant/` in a fixed entry format, and you are pointed to GitHub, a forum or a form for filing.
A batch mode can submit all pending saved reports one by one, with duplicate checks and previews. The rules require confirmation before every submission, redaction of tokens and keys in logs, and a Blocked marker on changes to the Redux or IndexedDB schema.
When your agent uses it
- Filing a bug as a GitHub Issue on the Cherry Studio repository
- Submitting a feature request through the repository's issue template
- Saving reports locally when the GitHub CLI is not signed in
Example prompts
- “Submit this as a GitHub Issue: the app crashes when I import a large knowledge base file.”
- “Create a GitHub feature request for exporting chats as Markdown.”
- “Submit all my saved bug reports to GitHub.”
Requirements
- The GitHub CLI (`gh`), signed in, for GitHub mode
What it can do on your machine
Read from SKILL.md and the folder at commit 9558400. 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
Links to these hosts (documentation or services it may open):
mcnnox2fhjfq.feishu.cn
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
Cherry Studio GitHub Issue Reporter loads about 335 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 76 words of instructions outside code blocks.
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 9558400, republished under its AGPL-3.0 licence (© CherryHQ). 76 words, ~335 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-reporter/SKILL.md (or your agent's skills folder).- name
- issue-reporter
- description
- 只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发，必须改用 cherry-studio-feedback 并默认提交飞书。
Issue Reporter
触发边界
只有用户明确要求提交到 GitHub，才能继续本流程。不得从“提交问题”“反馈”“bug”或“功能建议”推断 GitHub；未明确点名 GitHub 时立即转交 cherry-studio-feedback，不得运行 gh auth status、搜索仓库或发起任何 GitHub 操作。
检测 GitHub 登录
每次提交前: gh auth status 2>&1。成功→GitHub模式，失败→本地模式。
GitHub 模式
Bug Report: 收集信息(描述/复现步骤/期望/平台/版本) → 查重 gh search issues "[关键词]" --repo CherryHQ/cherry-studio --state open --limit 5 → 读模板 .github/ISSUE_TEMPLATE/0_bug_report.yml → 预览给用户 → 确认后 gh issue create → 告知链接
Feature Request: 确认需求→查重→读模板 1_feature_request.yml→预览→确认→提交→记录到 .cherry-assistant/feature-requests.md
本地模式
Bug 存 .cherry-assistant/bug-reports.md，Feature 存 feature-requests.md：
### [Bug/Feature]: [标题]
- **日期**: YYYY-MM-DD | **平台**: OS | **版本**: vX.X.X
- **描述**: ... | **复现步骤**: 1... 2... | **期望**: ...
- **状态**: 待提交
---存档后引导: GitHub(推荐) https://github.com/CherryHQ/cherry-studio/issues | 论坛 linux.do | 飞书表单 https://mcnnox2fhjfq.feishu.cn/share/base/form/shrcnsjfFkx4gy6wx9LQ70tMaKe
批量提交: 有权限时可说「帮我把待提交的都提交了」→读文件→筛待提交→逐个查重预览确认→更新状态为「已提交 #号」
注意
- 提交前必须用户确认
- 脱敏日志中 token/key
- Redux/IndexedDB schema 变更标记 Blocked: v2
© 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
Just SKILL.md in resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter of CherryHQ/cherry-studio.
Open the folder on GitHubat commit 9558400
Compare with similar skills
Cherry Studio GitHub Issue Reporter 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cherry Studio GitHub Issue Reporter this skillCherryHQ/cherry-studio | 52k | — | ~335 | Automated safety check: Pass | AGPL-3.0 | |
| Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness | 1.7k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Evidence-Driven Testingmichaelshimeles/skills | 1.3k | 1 repos | ~3.9k | Automated safety check: Pass | None | |
| Create GitHub IssueNVIDIA/OpenShell | 16k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Triage IssuesClickHouse/clickhouse-java | 1.6k | — | ~904 | Automated safety check: Pass | Apache-2.0 | |
| Gentle AI Issue CreationGentleman-Programming/gentle-shell | 1.2k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Evidence-Driven Testing
michaelshimeles/skills
Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.
- Official
Create GitHub Issue
NVIDIA/OpenShell
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
Triage Issues
ClickHouse/clickhouse-java
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
Gentle AI Issue Creation
Gentleman-Programming/gentle-shell
Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.
Termio Bug Report
termio-sh/termio
Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…
More from CherryHQ/cherry-studio
All 30 skills in this repoOffice 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.
GitHub Issue Creator
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.
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.
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.
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.
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.
Related
Works with
Categories
Questions about Cherry Studio GitHub Issue Reporter
What does Cherry Studio GitHub Issue Reporter do?
Files Cherry Studio bug reports and feature requests as GitHub Issues after a duplicate check and your confirmation, or saves them locally when GitHub is not signed in. This skill, written in Chinese, files bug reports and feature requests for the Cherry Studio repository, and it only runs when you explicitly ask for a GitHub Issue. Generic phrases such as submit feedback or report a bug are not enough; those go to the `cherry-studio-feedback` skill instead, and no GitHub command is run.
When should I use Cherry Studio GitHub Issue Reporter?
Cherry Studio GitHub Issue Reporter fits situations like: filing a bug as a GitHub Issue on the Cherry Studio repository; submitting a feature request through the repository's issue template; saving reports locally when the GitHub CLI is not signed in.
How do I install Cherry Studio GitHub Issue Reporter in Claude Code?
Run `npx skills add CherryHQ/cherry-studio --skill issue-reporter -a claude-code`. Or copy the skill folder (resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter in CherryHQ/cherry-studio) into .claude/skills/issue-reporter in your project. Claude Code loads it when a task matches its description.
How do I install Cherry Studio GitHub Issue Reporter in Codex?
Run `npx skills add CherryHQ/cherry-studio --skill issue-reporter -a codex`. Or copy the skill folder (resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter in CherryHQ/cherry-studio) into .agents/skills/issue-reporter in your project. Codex loads it when a task matches its description.
Can I use Cherry Studio GitHub Issue Reporter 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 issue-reporter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-reporter, .gemini/skills/issue-reporter, .github/skills/issue-reporter and .opencode/skills/issue-reporter in your project.
What does Cherry Studio GitHub Issue Reporter need to run?
Going by SKILL.md and its folder, Cherry Studio GitHub Issue Reporter needs the command-line tools its instructions call (gh). Our summary lists: The GitHub CLI (`gh`), signed in, for GitHub mode.
Does Cherry Studio GitHub Issue Reporter access the network?
SKILL.md names 1 domain. As links in the text: mcnnox2fhjfq.feishu.cn. This is read from the text; nothing was executed.
Is Cherry Studio GitHub Issue Reporter 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 Cherry Studio GitHub Issue Reporter use?
Cherry Studio GitHub Issue Reporter 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 Cherry Studio GitHub Issue Reporter use?
About 335 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cherry Studio GitHub Issue Reporter?
Skills that share tags, products or a category with Cherry Studio GitHub Issue Reporter: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 16k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cherry Studio GitHub Issue Reporter?
CherryHQ (a GitHub organization) maintains it in CherryHQ/cherry-studio, which has 52,476 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 9, 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.