A tight, highly actionable instruction-only skill: concrete commands, exact section and label names, an explicit post-edit validation step with a recovery loop, and a closing checklist. The only gap is the missing gh command for editing an existing PR body, which keeps actionability just below full marks.

Dimension	Reasoning	Score
Conciseness	Lean ~40 lines with no explanation of concepts Claude already knows; the only elaboration ("pkg means the TiDB module area, not a literal Go package path") is non-obvious domain knowledge that earns its place. Matches the 'every token earns its place' anchor, not the trimmable anchor 4.	5 / 5
Actionability	Provides a copy-paste command ("gh pr create -T .github/pull_request_template.md"), exact label names ("do-not-merge/needs-linked-issue"), and exact mutable targets. Not 5 because the existing-PR edit path says to call gh without giving the specific edit command (e.g., "gh pr edit --body-file"), leaving a minor gap.	4 / 5
Workflow Clarity	A clear 7-step sequence with an explicit validation checkpoint (step 7: re-read the PR and check bot-gated labels) and a feedback loop ("If a label remains unexpectedly, diff the current body against .github/pull_request_template.md"), plus a Quick Checks checklist — matching the anchor with validation steps, error recovery, and checklists.	5 / 5
Progressive Disclosure	The skill is under 50 lines, has no bundle files, and needs none: sections (Overview, Workflow, Quick Checks) are well-organized and the only external pointers (.github/pull_request_template.md, tidb-issue-metadata-guard) are clearly signaled. The simple-skill exception applies.	5 / 5
	Total	19 / 20 Passed

Description

66%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 naming three concrete capabilities in a well-defined niche. Its main weakness is the absence of any "Use when..." trigger clause, which both caps completeness and slightly weakens trigger coverage since common synonyms like "pull request" are not present.

Suggestions

Add an explicit trigger clause, e.g. "Use when editing a TiDB pull request title or body, creating a PR from the TiDB template, or when do-not-merge bot labels appear unexpectedly."

Include common synonyms such as "pull request" and "GitHub" so the description matches natural user phrasing beyond just "PR metadata".

Mention the release-note block or PR title format in the capability list to round out coverage of what the skill actually guards.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — "Create or edit TiDB PR metadata", "diagnose template-related bot labels", "preserve required fields and hidden comments" — which matches the 'several specific actions; minor gaps' anchor. Not 5 because coverage omits title conventions and issue linking; not 3 because it goes beyond 1-2 actions.	4 / 5
Completeness	The "what" is clear (create/edit metadata, diagnose labels, preserve fields), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely implicit.	3 / 5
Trigger Term Quality	"TiDB", "PR metadata", "bot labels", and "template" are natural terms a user would say, giving good keyword coverage. Not 5 because common variations like "pull request" (spelled out), "GitHub", and "release note" are missing.	4 / 5
Distinctiveness Conflict Risk	"TiDB PR metadata" carves out a clear niche, but the generic phrases "PR metadata" and "bot labels" carry minor overlap risk with generic GitHub PR-editing skills and the sibling issue-metadata skill. Mostly distinct, matching anchor 4 rather than the minimal-conflict anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: pingcap/tidb
Path: .agents/skills/tidb-pr-metadata-guard/SKILL.md
Commit: 93a01d3

Reviewed: 5 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.