Agent skill

TiDB Failpoint Test Runner

by pingcap in pingcap/tidb

“Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.”

— description from SKILL.md by pingcap
Apache-2.0Auto-check passedTesting & QA

Install TiDB Failpoint Test Runner

skills CLI
$ npx skills add pingcap/tidb --skill tidb-failpoint-test-runner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pingcap/tidb tidb-failpoint-test-runner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pingcap/tidb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tidb-failpoint-test-runner .claude/skills/tidb-failpoint-test-runner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tidb-failpoint-test-runner
GitHub stars
41k
Token cost
~256 tokens
SKILL.md length
103 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

  • Works in 4 steps: Use docs/agents/testing-flow.md ->… → Run the matching command set from… → Keep the run targeted with -run ; for… → …
  • SKILL.md covers Overview and Workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

About this skill

TiDB Failpoint Test Runner is a skill in pingcap/tidb (41k stars). Its SKILL.md is about 256 tokens. Licence: Apache-2.0.

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Use docs/agents/testing-flow.md -> Failpoint decision for unit tests to decide whether the package needs failpoint enablement.
  2. Run the matching command set from docs/agents/testing-flow.md
  3. Keep the run targeted with -run ; for Bazel-specific variants, see the Bazel notes in docs/agents/testing-flow.md -> Failpoint-enabled run.
  4. Record the decision evidence and exact test command in the final report.

What it can do on your machine

Read from SKILL.md and the folder at commit 7a3dacb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TiDB Failpoint Test Runner loads about 256 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 103 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~39
When it runs · the whole SKILL.md, loaded when a task matches
~256

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pingcap/tidb at commit 7a3dacb, republished under its Apache-2.0 licence (© pingcap). 103 words, ~256 tokens.

Download SKILL.mdSave it as .claude/skills/tidb-failpoint-test-runner/SKILL.md (or your agent's skills folder).
name
tidb-failpoint-test-runner
description
Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.

TiDB Failpoint Test Runner

Overview

Follow this workflow before running package tests under pkg/.... -tags=intest,deadlock does not enable failpoints. Canonical command details live in docs/agents/testing-flow.md -> Failpoint decision for unit tests.

Workflow

  1. Use docs/agents/testing-flow.md -> Failpoint decision for unit tests to decide whether the package needs failpoint enablement.
  2. Run the matching command set from docs/agents/testing-flow.md:
    • Failpoint-enabled run when the package matches the failpoint checks.
    • Unit tests (/pkg/...) when it does not.
  3. Keep the run targeted with -run <TestName>; for Bazel-specific variants, see the Bazel notes in docs/agents/testing-flow.md -> Failpoint-enabled run.
  4. Record the decision evidence and exact test command in the final report.

© pingcap, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/tidb-failpoint-test-runner of pingcap/tidb.

Open the folder on GitHubat commit 7a3dacb

Compare with similar skills

TiDB Failpoint Test Runner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TiDB Failpoint Test Runner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TiDB Failpoint Test Runner this skillpingcap/tidb41k—~256Automated safety check: PassApache-2.0
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Test Writing WorkflowiOfficeAI/AionUi33k1 repos~1.2kAutomated safety check: PassApache-2.0
Adk Verify Snippetsgoogle/adk-python22k—~1.4kAutomated safety check: PassApache-2.0
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • Test Writing Workflow

    iOfficeAI/AionUi

    Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.

    33k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed
  • Adk Verify Snippets

    google/adk-python

    Official

    Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…

    22k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check: notes
  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

More from pingcap/tidb

All 9 skills in this repo
  • Decides from local git changes whether make bazel_prepare must run in TiDB before build or test commands, and reports the evidence for the decision.

    41k GitHub stars~408 tokensUpdated today
    Auto-check passed
  • Investigates TiDB plan or test-result diffs that the change does not explain, ruling out failpoint setup and merge effects before expected outputs are updated.

    41k GitHub stars~498 tokensUpdated today
    Auto-check passed
  • Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.

    41k GitHub stars~260 tokensUpdated today
    Auto-check passed
  • Use when running tests under tests/realtikvtest that require a local TiUP playground lifecycle with strict startup, readiness checks, and cleanup.

    41k GitHub stars~250 tokensUpdated today
    Auto-check passed
  • Checks a fix proposed by a user or reviewer for intent, correctness and compatibility before the agent implements it in the TiDB codebase.

    41k GitHub stars~523 tokensUpdated today
    Auto-check passed
  • Keeps TiDB GitHub issues consistent by following the issue templates, writing reproducible reports, checking for duplicates and applying labels explicitly.

    41k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about TiDB Failpoint Test Runner

How do I install TiDB Failpoint Test Runner in Claude Code?

Run `npx skills add pingcap/tidb --skill tidb-failpoint-test-runner -a claude-code`. Or copy the skill folder (.agents/skills/tidb-failpoint-test-runner in pingcap/tidb) into .claude/skills/tidb-failpoint-test-runner in your project. Claude Code loads it when a task matches its description.

How do I install TiDB Failpoint Test Runner in Codex?

Run `npx skills add pingcap/tidb --skill tidb-failpoint-test-runner -a codex`. Or copy the skill folder (.agents/skills/tidb-failpoint-test-runner in pingcap/tidb) into .agents/skills/tidb-failpoint-test-runner in your project. Codex loads it when a task matches its description.

Can I use TiDB Failpoint Test Runner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pingcap/tidb --skill tidb-failpoint-test-runner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tidb-failpoint-test-runner, .gemini/skills/tidb-failpoint-test-runner, .github/skills/tidb-failpoint-test-runner and .opencode/skills/tidb-failpoint-test-runner in your project.

What does TiDB Failpoint Test Runner need to run?

SKILL.md names no scripts, command-line tools or credentials: TiDB Failpoint Test Runner is instructions for the agent only.

Does TiDB Failpoint Test Runner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TiDB Failpoint Test Runner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does TiDB Failpoint Test Runner use?

TiDB Failpoint Test Runner is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TiDB Failpoint Test Runner use?

About 256 tokens (SKILL.md is roughly 1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TiDB Failpoint Test Runner?

Skills that share tags, products or a category with TiDB Failpoint Test Runner: Jest Testing Patterns (ChrisWiles/claude-code-showcase, 6.1k stars), Rust TDD Workflow (rtk-ai/rtk, 83k stars), Test Writing Workflow (iOfficeAI/AionUi, 33k stars) and Adk Verify Snippets (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TiDB Failpoint Test Runner?

pingcap (a GitHub organization) maintains it in pingcap/tidb, which has 40,631 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

Source: pingcap/tidb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.