CtrlK
BlogDocsLog inGet started
Tessl Logo

github-repository-management

通过 GitHub MCP 管理仓库协作时使用,例如检索仓库、提 Issue、起草或创建 PR、查看评论、回复评审和做合并前检查。当用户要操作 GitHub 仓库协作流程而不是修改本地代码实现时优先使用。

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A concise, well-organized instructional skill with clear write-operation checkpoints. Its main weakness is progressive disclosure: the body repeatedly points to reference/workflows.md for templates and process details, but that file is absent from the bundle.

Suggestions

Create the referenced reference/workflows.md (or references/workflows.md) with the PR/Issue templates and tool-selection details the body promises, so the navigation target actually exists.

Inline a minimal concrete example or two (e.g. a skeleton PR title/body template, or the specific GitHub MCP tool names for 查重 and 创建 PR) to raise actionability without waiting on the external file.

Make the merge-prep validation steps explicit as a checklist (review 状态 ✓ / check runs ✓ / 冲突风险 ✓ / 用户授权 ✓) to push workflow_clarity from mostly-checkpointed to fully checkpointed.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned (适用场景、不适用场景、快速指导、高信号规则、关键陷阱) with no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Concrete guidance is present (先读后写 checklist, 查重/看 diff/展示拟提交内容 rules, merge-prep checklist), but it defers concrete templates and tool choices to reference/workflows.md rather than giving copy-paste-ready specifics; minor gaps.

4 / 5

Workflow Clarity

The 先读后写 sequence provides clear ordered checkpoints with validation before destructive write ops and a merge-prep checklist, matching the clear-sequence-with-most-checkpoints anchor; a few checkpoints are implicit rather than explicit.

4 / 5

Progressive Disclosure

Structure is good and references are one level deep, but the referenced file reference/workflows.md does not exist in the bundle (references/, scripts/, assets/ are empty), so the navigation points to a missing target — content that should be separate is deferred to a non-existent file.

3 / 5

Total

16

/

20

Passed

Description

92%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.

A strong description that names concrete GitHub-MCP collaboration actions, gives an explicit trigger condition, and clearly distinguishes itself from neighboring skills. Minor trigger-term synonym coverage keeps it just short of perfect on that one dimension.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions (检索仓库、提 Issue、起草或创建 PR、查看评论、回复评审、合并前检查), matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly states what it does (the 例如 list of actions) and when to use it ("当用户要操作 GitHub 仓库协作流程而不是修改本地代码实现时优先使用"), answering both what and when with concrete triggers.

5 / 5

Trigger Term Quality

It uses natural terms users would say (Issue、PR、评论、评审、合并前检查、GitHub MCP、仓库协作), with good coverage but a few common synonyms/extensions absent; not quite the fully comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply scoped against adjacent skills (local code changes, commit-message formatting, correctness review), giving clear distinct triggers with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
TencentBlueKing/bk-ci
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.