CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

issue-reporter

仅在用户点名 GitHub Issue、Bug Report 或 Feature Request 时使用;未点名 GitHub 的反馈改用 cherry-studio-feedback。

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary lean operational skill: terse, command-driven, well-sectioned, with explicit user-confirmation and dedup checkpoints guarding the batch/destructive submission flows. The only meaningful improvements are completing the gh issue create invocation (flags/template usage) and stating how to fetch the upstream issue templates, plus handling the duplicate-found case.

DimensionReasoningScore

Conciseness

The ~35-line body is maximally lean: every line is operational (commands, paths, a fill-in template, URLs) with zero explanation of concepts Claude already knows and no padding. Arrow-compressed steps like「收集信息(...) → 查重 ... → 预览给用户 → 确认后 gh issue create」assume Claude's competence, matching anchor 5 exactly.

5 / 5

Actionability

Mostly copy-paste ready: 「gh auth status 2>&1」, 「gh search issues "[关键词]" --repo CherryHQ/cherry-studio --state open --limit 5」, template paths, storage file paths, and a concrete markdown archive template. Minor gaps keep it below anchor 5: 「gh issue create」 lacks its argument form (--title/--body or --template), and reading 「.github/ISSUE_TEMPLATE/0_bug_report.yml」 does not specify how to obtain the file from the upstream repo (no clone/URL assumed).

4 / 5

Workflow Clarity

Both GitHub-mode and batch flows have clear arrow-sequenced steps with real checkpoints: dedup search (查重), user preview (预览给用户), mandatory confirmation (提交前必须用户确认 / 确认后), and post-submit status updates. The batch-operation cap at 3 does not apply since validation and confirmation are present, but it stays at 4 because error recovery is not addressed (e.g., what to do when 查重 finds an existing issue, or when gh issue create fails).

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist) and no need for external references; per the rubric's simple-skill guideline it scores 5 on well-organized sections alone. The body is cleanly sectioned (触发边界 / 检测登录 / GitHub 模式 / 本地模式 / 注意) and every path referenced is an external destination (repo, forum, form URL), not a missing bundle file.

5 / 5

Total

18

/

20

Passed

Description

51%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is an excellent routing boundary — explicit trigger terms and an explicit hand-off to the sibling feedback skill — but it omits any statement of what the skill does. Adding a short capability clause (e.g., '为 CherryHQ/cherry-studio 创建 GitHub Issue 或在本地存档 bug/feature 报告') would fix both the specificity and completeness gaps.

Suggestions

Add a concrete capability statement, e.g. 「为 CherryHQ/cherry-studio 提交 GitHub Issue(Bug Report / Feature Request),未登录 GitHub 时存档到本地 .cherry-assistant/」 so the description answers 'what' as well as 'when'.

Include the target repository name (CherryHQ/cherry-studio) in the description to strengthen specificity and distinguish it from generic issue-filing skills.

Optionally add one or two natural trigger variations such as plain 'GitHub' or '提issue' to broaden natural-term coverage without weakening the boundary.

DimensionReasoningScore

Specificity

The description names its domain —「仅在用户点名 GitHub Issue、Bug Report 或 Feature Request 时使用」— but states zero concrete actions; it never says what the skill actually does (e.g., submit issues to a repo, save local reports). This matches anchor 2 ('Names the domain but actions are minimal or generic') rather than 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The 'when' is explicit and strong, but the 'what' is entirely missing — the description never states the skill's capability (creating GitHub issues, filing local bug/feature reports). Anchor 2 explicitly covers this case ('only "when" is present without "what"'), and it cannot be 3+ because no capability is stated, only a trigger condition.

2 / 5

Trigger Term Quality

「GitHub Issue」「Bug Report」「Feature Request」are natural phrases users would actually say when needing this skill, giving good keyword coverage. It falls short of anchor 5 because common variations (e.g., plain 'GitHub', '提个issue', '报bug') are absent — though the latter are deliberately routed to the sibling skill, they are still not covered here.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche with distinct triggers and explicitly hands off non-GitHub feedback to「cherry-studio-feedback」, minimizing conflict risk with the sibling skill. This is a textbook match for anchor 5 ('Clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CherryHQ/cherry-studio

Path

resources/builtin-agents/cherry-assistant/.claude/skills/issue-reporter/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.