CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-matt-pocock-skills

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

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/engineering/setup-matt-pocock-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured, prompt-driven setup skill with concrete commands, precise decision rules, and user-confirmation checkpoints throughout. Its main weaknesses are the missing seed template files that step 4 depends on (hurting both actionability and progressive disclosure), the absence of a post-write verification step, and minor repetition around the triage-conditional logic.

Suggestions

Ship the five seed templates (issue-tracker-github.md, issue-tracker-gitlab.md, issue-tracker-local.md, triage-labels.md, domain.md) in the skill bundle, or inline their essential content, so the referenced paths actually resolve.

Add a lightweight verification step after writing (e.g., re-read the edited CLAUDE.md/AGENTS.md block and the docs/agents/*.md files to confirm they were written as confirmed) before declaring setup complete.

State the triage-installed conditional once (at the point where it governs behavior) instead of repeating it in the exploration list, Section B, and the write step.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explanations of git, GitHub, or what an issue tracker is), with every section carrying operational instructions. Minor trimming is possible: the triage-installed conditional is stated three times (exploration, Section B, and the write step), and the Section A explainer paragraph is long.

4 / 5

Actionability

Guidance is highly concrete — exact commands (`git remote -v`, `gh label create` / `glab label create`), exact paths (`docs/agents/issue-tracker.md`, `.scratch/<feature>/`), the five canonical label strings, and a complete markdown template block. It falls short of 5 because step 4's doc writing depends on seed templates (issue-tracker-*.md, triage-labels.md, domain.md) that are not present in the bundle, leaving a real gap when executing the write step.

4 / 5

Workflow Clarity

A clear five-step sequence (探索 → 呈现发现并询问 → 确认并编辑 → 写入 → 完成) with meaningful checkpoints: user confirmation before writing, a repo-reachability check via `gh repo view` / `glab repo view` with explicit failure handling ("停下来并告诉用户缺少什么"), and legacy-file migration rules. It is not 5 because there is no post-write verification before step 5 declares completion.

4 / 5

Progressive Disclosure

Structure is good — an overview body with clearly signaled, one-level-deep references to the seed templates — but all five referenced files (issue-tracker-github.md, issue-tracker-gitlab.md, issue-tracker-local.md, triage-labels.md, domain.md) are missing from the bundle. Scored against the actual bundle structure, the references do not resolve, which is more than a minor organization gap.

3 / 5

Total

15

/

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 concise, third-person description that clearly states both what it configures and when it should run, with a well-delineated niche. It scores solidly across dimensions but stops short of top marks on trigger-term coverage and could enumerate more concrete trigger phrases for the when-clause.

Suggestions

Add natural trigger synonyms such as "setup" or "初始化" so users phrasing the request differently still match the description.

Make the when-clause more trigger-phrase oriented, e.g., "Use when setting up or onboarding this repo's engineering skills for the first time."

DimensionReasoningScore

Specificity

"设置其 issue tracker、triage labels 词汇与 domain docs 布局" names three concrete, distinct configuration targets, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the setup action per target is generic and no sub-actions are enumerated.

4 / 5

Completeness

The 'what' is explicit (issue tracker, triage label vocabulary, domain docs layout) and the 'when' is explicit ("在首次使用其他 engineering skills 前运行一次"), so the missing-trigger cap at 3 does not apply. It is not 5 because the when-clause states timing rather than enumerating concrete trigger phrases a user would say.

4 / 5

Trigger Term Quality

Terms like "配置", "engineering skills", "issue tracker", "triage labels", and "domain docs" are natural phrases a user would plausibly say when invoking this skill, giving good coverage. It is not 5 because common variations and synonyms (e.g., "setup", "初始化", "onboarding") are absent.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — one-time per-repo configuration consumed by a specific suite of engineering skills ("在首次使用其他 engineering skills 前运行一次") — with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.