tidb-integrationtest-recorder
Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.
50
53%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/tidb-integrationtest-recorder/SKILL.mdQuality
Discovery
57%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 has a clear niche and good distinctiveness due to its specificity to TiDB integration tests and a particular directory path. However, it lacks explicit capability listing (what concrete actions the skill performs) and relies on the 'Use when' clause to imply functionality rather than stating it directly. The trigger terms are adequate but could be expanded with more natural user language variations.
Suggestions
Add explicit capability statements before the 'Use when' clause, e.g., 'Records integration test cases, generates expected output files, and validates that regenerated result files remain minimal and correct.'
Include additional trigger terms users might naturally use, such as 'test output', 'expected results', 'regenerate tests', '.result files', or 'record test'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'recording TiDB integration tests' and 'verifying regenerated result files stay minimal and correct,' which names the domain and some actions but doesn't list multiple concrete actions (e.g., what specific steps are involved in recording or verifying). | 2 / 3 |
Completeness | The description starts with 'Use when' which addresses the 'when' aspect, but the 'what does this do' part is only implied through the trigger conditions rather than explicitly stated as concrete capabilities. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'TiDB', 'integration tests', 'integrationtest', and 'result files', but misses common variations a user might say such as 'test results', 'test output', 'regenerate', or specific file types/paths. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: TiDB integration tests under a specific directory path (tests/integrationtest) with result file verification. This is unlikely to conflict with other skills due to the narrow, well-defined scope. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise and well-structured but critically lacks actionability—it delegates the most important information (the actual recording command) to an external file and provides no executable examples or concrete commands inline. The workflow has a reasonable sequence but is missing explicit validation steps, and the guardrails are too vague to be truly useful.
Suggestions
Include the actual recording command inline (e.g., the specific `go test` invocation with flags) rather than solely delegating to an external file, so the skill is self-contained for the common case.
Add a concrete example showing the full workflow: deriving TestName from a path, running the command, and reviewing the diff output.
Add an explicit validation step in the workflow, e.g., 'Run the recording command a second time and confirm no additional diff is produced' as a numbered step with a checkpoint marker.
Show a concrete example of what 'minimal result diffs' looks like versus unrelated churn to make the guardrail actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what TiDB is or how integration tests work in general. Every line serves a purpose and assumes Claude's competence. | 3 / 3 |
Actionability | The skill provides no concrete commands, code, or executable examples. It delegates the actual recording command to an external file (`docs/agents/testing-flow.md`) and only gives vague guidance like 'keep result diffs minimal' without showing how. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. Step 3 says to 'review changed files' and 'keep result diffs minimal' but doesn't specify how to validate correctness. The guardrail about verifying with another run is mentioned but not integrated into the workflow as an explicit checkpoint. | 2 / 3 |
Progressive Disclosure | References to `docs/agents/testing-flow.md` are clearly signaled and one level deep, which is good. However, with no bundle files provided, we cannot verify the referenced path exists, and the skill delegates its core actionable content (the actual command) entirely to the external file, leaving the skill itself hollow. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- pingcap/tidb
- Commit
e70762e
- 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.