CtrlK
BlogDocsLog inGet started
Tessl Logo

tidb-verify-profile

Choose validation for TiDB changes during iteration and delivery, using the checks required for each change type.

77

2.17x
Quality

81%

Does it follow best practices?

Impact

100%

2.17x

2 of 3 eval scenarios. Add 1 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-structured instruction skill: it names concrete commands, sequences the Ready profile explicitly, and cleanly delegates policy to AGENTS.md. Its only notable gap is that the key check-selection detail lives in the external matrix rather than the skill, and there is no explicit guidance for handling failed checks.

DimensionReasoningScore

Conciseness

Every line instructs ('Run only the smallest scoped checks', 'Never run `make bazel_lint_changed` unless the user explicitly requests it') and no concepts Claude already knows are explained. Lean and efficient; each token earns its place.

5 / 5

Actionability

Concrete commands are given (`go test -run <TestName> -tags=intest,deadlock`, `make lint`, `make bazel_lint_changed`), but the central Ready-profile step ('Map changed paths and change types to `AGENTS.md` -> `Task -> Validation Matrix`) delegates the actual check selection to an external doc rather than stating it. Mostly executable guidance with minor gaps; not fully copy-paste ready.

4 / 5

Workflow Clarity

The Ready profile gives a clear 4-step numbered sequence with reuse/rerun checkpoints ('Rerun affected checks when relevant changes or new failures invalidate the results'). It lacks an explicit failure-handling loop (what to do when a required check fails), keeping it at anchor 4 rather than 5, but the sequence and checkpoints are explicit, so it exceeds anchor 3.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Overview, three Profiles) and clearly signaled, one-level-deep references into `AGENTS.md`. No bundle files exist, so per the simple-skill guideline this organization merits the top score.

5 / 5

Total

18

/

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.

The description is concise, third-person, and answers both what and when with a clear TiDB-specific niche. Its main weaknesses are limited synonym coverage for natural trigger phrases and actions that stay at the 'choose validation' level rather than naming concrete checks.

Suggestions

Add natural trigger phrases users would actually say, e.g. 'Use when verifying or testing TiDB changes, or when preparing to deliver a TiDB PR'.

Enumerate one or two concrete actions beyond 'choose validation', such as 'run make lint and scoped go tests' or 'select checks per change type from the validation matrix'.

Mention common synonyms like 'verify', 'test', or 'CI' alongside 'validation' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('TiDB changes') and 1-2 concrete actions ('Choose validation', 'using the checks required for each change type'), but does not list several specific actions. It is more concrete than anchor 2 because the actions go beyond naming the domain, but not comprehensive enough for anchor 4.

3 / 5

Completeness

Both 'what' (choose validation and required checks for TiDB changes) and 'when' ('during iteration and delivery') are explicitly stated, so it exceeds anchor 3 where 'when' is only weakly implied. The 'when' could be more specific with user-sayable triggers, so it falls short of anchor 5.

4 / 5

Trigger Term Quality

Relevant keywords are present ('TiDB', 'validation', 'checks', 'change type'), but common natural variations users would say are missing ('verify', 'test', 'CI', 'before opening a PR'). Matches anchor 3; anchor 4 requires fuller synonym coverage.

3 / 5

Distinctiveness Conflict Risk

'TiDB' pins a clear niche with minimal overlap risk against other skills. It is distinct rather than merely 'mostly distinct' (anchor 4), because the domain qualifier makes false triggers unlikely.

5 / 5

Total

15

/

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.

Validation — 16 / 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.