CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-cli

使用 GitHub CLI (`gh`) 执行非交互式 GitHub 协作与自动化任务(PR、Issue、Actions、Release、API 查询/修改)。当用户要求“用 gh 命令完成任务”、需要结构化 JSON 输出(`--json`/`--jq`)、批量处理 PR/Issue(如“批量 review 多个 PR”)、按策略合并(如“检查通过后自动 squash 合并”)时使用此 skill。

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

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

The body is lean, actionable, and well-sequenced with strong validation checkpoints. Its main weakness is reference depth: the command index points through a group index to per-subcommand files, adding an extra hop of indirection.

Suggestions

Flatten the reference hierarchy so the body links directly to group index files (e.g. references/pr.md) and have each group index contain its subcommand details inline, reducing commands.md → group → subcommand to a single level of indirection.

In the Reference section, state explicitly that commands.md is only an index and that group files (pr.md, issue.md, etc.) are the primary entry points, so Claude does not always load two files before reaching guidance.

Consider linking the most-used subcommand files (e.g. pr-review.md, pr-diff.md) directly from the relevant Operation Decision bullet to skip the intermediate index hop for common tasks.

DimensionReasoningScore

Conciseness

Lean body with no concept-explanation padding; every section is an actionable rule or checklist that assumes Claude's competence, with each token earning its place.

3 / 3

Actionability

Provides concrete commands and flags (`gh api --paginate`, `gh api -f/-F`, `gh api repos/{owner}/{repo}/pulls/{num}/comments`) plus specific gotchas (422 from mismatched `commit_id`/`headRefOid`), giving executable guidance rather than vague direction.

3 / 3

Workflow Clarity

Sequenced Workflow steps, an Operation Decision branch table, Failure Handling, and an explicit pre-write Safety Checklist with validation checkpoints and idempotency handling for batch/destructive operations.

3 / 3

Progressive Disclosure

Overview body signals references clearly, but navigation is two levels deep (commands.md → group index like pr.md → subcommand pr-diff.md), exceeding the one-level-deep ideal in the rubric anchor.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, and clearly distinguishes the skill's niche while covering both what it does and when to use it. It is concise without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as PR/Issue/Actions/Release handling, API query/modify, structured JSON output, batch processing, and policy-based merging rather than vague language.

3 / 3

Completeness

Explicitly answers what (non-interactive GitHub collaboration/automation via gh) and when, with an explicit "当用户要求……时使用此 skill" trigger clause.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say — "用 gh 命令完成任务", "批量 review 多个 PR", "检查通过后自动 squash 合并" — plus concrete flags `--json`/`--jq`, giving good coverage of likely triggers.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to gh CLI tasks with distinct, gh-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
BiFangKNT/mtga
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.