CtrlK
BlogDocsLog inGet started
Tessl Logo

tidb-pr-metadata-guard

Use when creating or editing TiDB pull requests so PR title scope, PR template fields, hidden HTML comments, and bot-parsed checklist sections stay intact. Trigger on tasks involving PR creation, PR body updates, issue linking from a PR, test checklist updates, or investigating labels like do-not-merge/needs-tests-checked.

72

Quality

89%

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

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 well-structured, actionable instruction skill with a clear sequenced workflow and verification feedback loop for a destructive-ish PR-metadata operation. It earns top marks for disclosure but has minor redundancy and a missing executable command for the existing-PR edit path.

Suggestions

Add the concrete command for updating an existing PR body (e.g. 'gh pr edit <num> --body-file body.md') alongside the existing 'gh pr create -T …' example so both paths are copy-paste ready.

Tighten the Quick Checks section to avoid restating the pkg-scope naming rule and the template HTML-comment rule already covered in Workflow; cross-reference instead of duplicating.

Make the post-update validation a hard gate by stating that the PR body edit is only considered complete once bot-gated labels (do-not-merge/needs-linked-issue, needs-tests-checked) have cleared, not just that they should be re-checked.

DimensionReasoningScore

Conciseness

Lean and assumes competence, but the Quick Checks section repeats the pkg-scope rule and the template HTML-comment rule already stated in Workflow, adding mild redundancy.

4 / 5

Actionability

Provides a concrete copy-paste command ('gh pr create -T .github/pull_request_template.md') and names exact safe/unsafe targets, but omits an executable command for editing existing PRs (only describes mutable sections).

4 / 5

Workflow Clarity

A clear 7-step sequence with a pre-flight review checkpoint (step 6) and a post-update verify/diff feedback loop (step 7), but the validation is advisory rather than a strict 'do not proceed until labels clear' gate.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized Overview/Workflow/Quick Checks sections and no need for external bundle references; the only references are repo files and a sibling skill, one level deep.

5 / 5

Total

17

/

20

Passed

Description

100%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 highly specific, well-targeted description that explicitly states both the capability and concrete trigger conditions for a narrow TiDB PR-metadata niche. It avoids vague language and names exact bot labels and PR elements.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities comprehensively — 'creating or editing TiDB pull requests' plus preserving 'PR title scope, PR template fields, hidden HTML comments, and bot-parsed checklist sections'.

5 / 5

Completeness

Explicitly answers both what (preserve PR title scope, template fields, HTML comments, checklist sections) and when ('Use when creating or editing TiDB pull requests… Trigger on tasks involving…').

5 / 5

Trigger Term Quality

Covers natural trigger terms a TiDB contributor would say — 'PR creation', 'PR body updates', 'issue linking from a PR', 'test checklist updates', and concrete bot labels 'do-not-merge/needs-tests-checked'.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche — TiDB GitHub PR metadata with bot-gated labels — making overlap with unrelated skills unlikely.

5 / 5

Total

20

/

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
pingcap/tidb
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.