New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Test Runner

by FoundationDB in FoundationDB/fdb-record-layer

Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures.

Apache-2.0Auto-check passedTesting & QA

Install Test Runner

skills CLI
$ npx skills add FoundationDB/fdb-record-layer --skill test-runner -a claude-code

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

GitHub CLI
$ gh skill install FoundationDB/fdb-record-layer 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/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/test-runner .claude/skills/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
test-runner
GitHub stars
675
Token cost
~396 tokens
SKILL.md length
155 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures.

  • Works in 4 steps: Read the full test output — look for the… → Check if the failure is in a yaml test → Check if the failure is an async issue → …
  • Tasks that involve Integration testing
  • SKILL.md covers How to run tests and Diagnosing failures
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Test Runner is an agent skill from FoundationDB/fdb-record-layer. Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures. Some example usages: "Run EmbeddedRelationalStatementTest" "Run the yaml integration tests" "Why is this test failing?" "Run the tests for the class I just modified"

Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Integration testing. The repository describes itself as: A relational database with SQL support built on FoundationDB. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Integration testing

Example prompts

  • “Run EmbeddedRelationalStatementTest”
  • “Run the yaml integration tests”
  • “Why is this test failing?”
  • “/test-runner”

Workflow steps

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

  1. Read the full test output — look for the stack trace and the assertion message.
  2. Check if the failure is in a yaml test
  3. Check if the failure is an async issue
  4. Check if FDB connectivity is the issue

What it can do on your machine

Read from SKILL.md and the folder at commit f266052. 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

Test Runner loads about 396 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 155 words of instructions outside code blocks.

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

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 FoundationDB/fdb-record-layer at commit f266052, republished under its Apache-2.0 licence (© FoundationDB). 155 words, ~396 tokens.

Download SKILL.mdSave it as .claude/skills/test-runner/SKILL.md (or your agent's skills folder).
name
test-runner
description
Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures. Some example usages: "Run EmbeddedRelationalStatementTest" "Run the yaml integration tests" "Why is this test failing?" "Run the tests for the class I just modified"

Always apply the using-gradle skill for Gradle task syntax and build commands.

How to run tests

  • For yaml-tests: ./gradlew :yaml-tests:test (or --tests 'YamlIntegrationTests.<name>').
  • For embedded-only yaml-tests (faster): ./gradlew :yaml-tests:quickTest.
  • For mixed-mode yaml-tests locally: ./gradlew :yaml-tests:mixedModeTest.
  • For JUnit tests in a module: ./gradlew :<module>:test --tests '<fully.qualified.ClassName>'.

Diagnosing failures

  1. Read the full test output — look for the stack trace and the assertion message.
  2. Check if the failure is in a yaml test:
    • plan mismatch → the actual query plan changed; edit YamlIntegrationTests.java to add @MaintainYamlTestConfig(YamlTestConfigFilters.CORRECT_EXPECTATIONS) to the test entry, then re-run — the framework will auto-correct the expected plan.
    • result mismatch → data or query logic changed; inspect the yamsql file.
  3. Check if the failure is an async issue:
    • BlockingInAsyncContextException → something called join()/get() inside a future.
    • Timeout → possible deadlock; check for blocking calls in completion lambdas.
  4. Check if FDB connectivity is the issue:
    • FDBException or connection refused → FDB is not running or cluster file is wrong.

© FoundationDB, 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 .claude/skills/test-runner of FoundationDB/fdb-record-layer.

Open the folder on GitHubat commit f266052

Compare with similar skills

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.

Test Runner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Runner this skillFoundationDB/fdb-record-layer675—~396Automated safety check: PassApache-2.0
Plugin Testingpolyipseity/obsidian-terminal948—~828Automated safety check: PassAGPL-3.0
Create Modulecartography-cncf/cartography4.1k—~2.5kAutomated safety check: PassApache-2.0
Td Integration Testmarcus/td251—~1.2kAutomated safety check: PassMIT
Integration E2E Testingshinpr/claude-code-workflows691—~3.5kAutomated safety check: PassMIT
JS-in-HTML Testingliaohch3/claude-tap3.3k—~924Automated safety check: PassMIT

Similar skills

  • Plugin Testing

    polyipseity/obsidian-terminal

    Skill for testing Obsidian plugin features in this repository.

    948 GitHub stars~828 tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Create Module

    cartography-cncf/cartography

    Author a new Cartography intel module end-to-end (entry point, sync GET/TRANSFORM/LOAD/CLEANUP, declarative data model, integration test, schema docs).

    4.1k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Td Integration Test

    marcus/td

    Write integration tests for the td-sync admin API using the TestHarness in internal/api/testharnesstest.go.

    251 GitHub stars~1.2k tokensUpdated 7 days ago
    Testing & QAAuto-check passed

  • Integration E2E Testing

    shinpr/claude-code-workflows

    Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.

    691 GitHub stars~3.5k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • JS-in-HTML Testing

    liaohch3/claude-tap

    Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.

    3.3k GitHub stars~924 tokensUpdated 15 days ago
    Testing & QAAuto-check passed

  • Crosvm Testing

    google/crosvm

    Official

    Skill to assist with running tests and managing test VMs in the crosvm repository.

    1.3k GitHub stars~847 tokensUpdated today
    Testing & QAAuto-check passed

More from FoundationDB/fdb-record-layer

All 10 skills in this repo

  • Relational Query Processor

    FoundationDB/fdb-record-layer

    Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner.

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

  • Using Gradle

    FoundationDB/fdb-record-layer

    A skill your agent uses when you need to build the project, compile code, or run tests.

    675 GitHub stars~705 tokensUpdated today
    Auto-check passed

  • Context Resumption

    FoundationDB/fdb-record-layer

    Rebuild working context after a session restart. An agent skill from FoundationDB/fdb-record-layer.

    675 GitHub stars~467 tokensUpdated today
    Auto-check passed

  • Docs Writer

    FoundationDB/fdb-record-layer

    Write or update documentation in docs/sphinx/source/. An agent skill from FoundationDB/fdb-record-layer.

    675 GitHub stars~925 tokensUpdated today
    Auto-check passed

  • Frl Coding Standard

    FoundationDB/fdb-record-layer

    Coding standards for all Java code in fdb-record-layer. An agent skill from FoundationDB/fdb-record-layer.

    675 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Frl Test Coding Standard

    FoundationDB/fdb-record-layer

    Standards for writing tests in fdb-record-layer. An agent skill from FoundationDB/fdb-record-layer.

    675 GitHub stars~792 tokensUpdated today
    Auto-check passed

Categories

Questions about Test Runner

What does Test Runner do?

Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures. Test Runner is an agent skill from FoundationDB/fdb-record-layer. Run tests in the fdb-record-layer codebase, interpret results, and diagnose failures.

When should I use Test Runner?

Test Runner fits situations like: tasks that involve Integration testing.

How do I install Test Runner in Claude Code?

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

How do I install Test Runner in Codex?

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

Can I use 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 FoundationDB/fdb-record-layer --skill 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/test-runner, .gemini/skills/test-runner, .github/skills/test-runner and .opencode/skills/test-runner in your project.

What does Test Runner need to run?

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

Does 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 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 Test Runner use?

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 Test Runner use?

About 396 tokens (SKILL.md is roughly 1.6k 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 Test Runner?

Skills that share tags, products or a category with Test Runner: Plugin Testing (polyipseity/obsidian-terminal, 948 stars), Create Module (cartography-cncf/cartography, 4.1k stars), Td Integration Test (marcus/td, 251 stars) and Integration E2E Testing (shinpr/claude-code-workflows, 691 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Runner?

FoundationDB (a GitHub organization) maintains it in FoundationDB/fdb-record-layer, which has 675 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

Source: FoundationDB/fdb-record-layer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.