setup-matt-pocock-skills

为此仓库配置 engineering skills——设置其 issue tracker、triage labels 词汇与 domain docs 布局。在首次使用其他 engineering skills 前运行一次。

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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 well-organized, prompt-driven setup skill with concrete commands, paths, and templates and a clear multi-step workflow including a confirm-before-write checkpoint. The main gap is that the seed template files referenced in the body are missing from the bundle, slightly undermining progressive disclosure.

Suggestions

Ship the referenced seed templates (issue-tracker-github.md, issue-tracker-gitlab.md, issue-tracker-local.md, triage-labels.md, domain.md) alongside SKILL.md so the one-level-deep references resolve.

Add a short post-write verification step in '### 5. Done' (e.g., re-read the written docs/agents/*.md and confirm the ## Agent skills block was inserted/updated) to close the workflow_clarity loop.

Tighten the Section A 'Explainer' paragraph and the conditional-skip sentences to reduce token cost without losing the confirm-with-user intent.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no explanations of git/GitHub/ADRs); the Section A 'Explainer' block and some conditional-skip prose could be trimmed, but otherwise efficient.	4 / 5
Actionability	Highly concrete for an instruction-only skill: exact commands ('git remote -v'), exact paths ('docs/agents/issue-tracker.md'), exact label strings, and a verbatim '## Agent skills' block template — copy-paste ready guidance covering the common cases.	5 / 5
Workflow Clarity	Clear five-step sequence (Explore → Present → Confirm → Write → Done) with a user-confirmation checkpoint before writing and explicit conditional skips; not a 5 because there is no post-write verification that the files landed correctly.	4 / 5
Progressive Disclosure	Well-structured overview with clearly signaled one-level-deep references to seed templates (issue-tracker-github.md, domain.md, etc.); held at 4 rather than 5 because the referenced seed files are not present in the skill bundle, so the navigation cannot be fully verified.	4 / 5
	Total	17 / 20 Passed

Description

78%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 specific, third-person description that clearly conveys both the setup actions and the one-time trigger, occupying a distinct niche with low conflict risk. Main weakness is the trigger-phrase coverage, which is good but lacks synonyms and natural variations.

Dimension	Reasoning	Score
Specificity	Names three concrete configuration targets — '设置其 issue tracker、triage labels 词汇与 domain docs 布局' — giving specific actions rather than vague language, though each is stated at a 'set up X' level without further detail.	4 / 5
Completeness	Explicitly states both what ('为此仓库配置 engineering skills——设置...') and when ('在首次使用其他 engineering skills 前运行一次'), with the when being a concrete trigger; not a 5 because the when is a one-time setup instruction rather than a richly enumerated trigger-phrase set.	4 / 5
Trigger Term Quality	Contains natural terms a user would say ('engineering skills', 'issue tracker', 'triage labels', 'domain docs'); good coverage but missing common synonyms or file-extension-style variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche — per-repo setup of this specific engineering-skills suite (issue tracker / triage labels / domain docs) — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: vinvcn/mattpocock-skills-zh-CN
Path: skills/engineering/setup-matt-pocock-skills/SKILL.md
Commit: 9fb0161

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.