Agent skill

Testing

by Microck in Microck/ordinary-claude-skills

Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests.

Custom licenceAuto-check passedTesting & QA

Install Testing

skills CLI
$ npx skills add Microck/ordinary-claude-skills --skill testing -a claude-code

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

GitHub CLI
$ gh skill install Microck/ordinary-claude-skills testing --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/Microck/ordinary-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_all/testing .claude/skills/testing && 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
testing
GitHub stars
401
Token cost
~854 tokens
SKILL.md length
253 words
Files
2
Skills in repo
97
Repo updated
First seen
Licence
Custom licence

At a glance

Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests.

  • Works in 3 steps: Docker is installed and running: docker ps → Sufficient Docker memory allocated (4GB+… → Network access to pull Docker images
  • Asked to run tests
  • SKILL.md covers Quick Commands, Integration Testing, Troubleshooting and Test Architecture, plus 2 more sections
  • Calls pnpm and docker

What it does

Testing is an agent skill from Microck/ordinary-claude-skills. Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests. Use when asked to run tests, fix test failures, debug integration tests, or troubleshoot Docker/database container issues.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).

It sits in Testing & QA, covering Integration testing, Failing and flaky tests and Unit testing. It works with Docker, Microsoft SQL Server and pnpm. The repository describes itself as: An unappealing collection of Claude Skills and resources.

When your agent uses it

  • Asked to run tests
  • Fix test failures
  • Debug integration tests
  • Troubleshoot Docker/database container issues

Example prompts

  • “/testing”

Requirements

  • Docker

Workflow steps

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

  1. Docker is installed and running: docker ps
  2. Sufficient Docker memory allocated (4GB+ recommended)
  3. Network access to pull Docker images

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • pnpm
    • docker

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

  • Network

    Links to these hosts (documentation or services it may open):

    • testcontainers.com

    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

Testing loads about 854 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 253 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 253 words (~854 tokens).

“This skill helps you run and troubleshoot tests in the DBHub project.”

— opening of SKILL.md by Microck, Custom licence
name
testing

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in skills_all/testing of Microck/ordinary-claude-skills.

  • SKILL.md
  • metadata.json

Open the folder on GitHubat commit 1056d29

Compare with similar skills

Testing 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.

Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing this skillMicrock/ordinary-claude-skills401—~854Automated safety check: PassCustom licence
Ckeditor5 TestingTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0
Designing TestsCloudAI-X/claude-workflow-v21.4k1 repos~1.5kAutomated safety check: PassMIT
Running TestsNangoHQ/nango13k—~876Automated safety check: PassCustom licence
Slow TestsUKGovernmentBEIS/inspect_ai2.9k—~1.4kAutomated safety check: PassMIT
NIC Testing Patternsnginx/kubernetes-ingress5.1k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Ckeditor5 Testing

    TriliumNext/Trilium

    Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-check passed
  • Running Tests

    NangoHQ/nango

    A skill your agent uses when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns

    13k GitHub stars~876 tokensUpdated today
    Testing & QAAuto-check passed
  • Slow Tests

    UKGovernmentBEIS/inspect_ai

    Run the gated test classes that plain pytest skips (slow Docker/sandbox tests, live model-provider API tests, flaky tests, trio variants).

    2.9k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • NIC Testing Patterns

    nginx/kubernetes-ingress

    Testing conventions for the NGINX Ingress Controller repo: Go table-driven tests, mandatory snapshot regeneration, Helm tests and Python pytest integration tests.

    5.1k GitHub stars~2.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Grails Test Fixer

    apache/grails-core

    Guides running, reviewing and fixing test failures across grails-core modules with Gradle, including targeted runs and the aggregate HTML and Markdown reports.

    2.9k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

More from Microck/ordinary-claude-skills

All 97 skills in this repo
  • Every Style Editor

    Microck/ordinary-claude-skills

    This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide.

    401 GitHub starsUsed in 3 repos~1.2k tokens
    Auto-check passed
  • Gemini Imagegen

    Microck/ordinary-claude-skills

    Generate and edit images using the Gemini API (Nano Banana Pro).

    401 GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed
  • Andrew Kane Gem Writer

    Microck/ordinary-claude-skills

    Write Ruby gems following Andrew Kane's proven patterns and philosophy.

    401 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Codex

    Microck/ordinary-claude-skills

    Execute Codex CLI for code analysis, refactoring, and automated code changes.

    401 GitHub starsUsed in 2 repos~2.8k tokens
    Auto-check passed
  • Docs Review

    Microck/ordinary-claude-skills

    Review documentation changes for compliance with the Metabase writing style guide.

    401 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check: notes
  • File Todos

    Microck/ordinary-claude-skills

    This skill should be used when managing the file-based todo tracking system in the todos/ directory.

    401 GitHub starsUsed in 2 repos~1.9k tokens
    Auto-check passed

Categories

Questions about Testing

What does Testing do?

Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests. Testing is an agent skill from Microck/ordinary-claude-skills. Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests.

When should I use Testing?

Testing fits situations like: asked to run tests; fix test failures; debug integration tests; troubleshoot Docker/database container issues.

How do I install Testing in Claude Code?

Run `npx skills add Microck/ordinary-claude-skills --skill testing -a claude-code`. Or copy the skill folder (skills_all/testing in Microck/ordinary-claude-skills) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.

How do I install Testing in Codex?

Run `npx skills add Microck/ordinary-claude-skills --skill testing -a codex`. Or copy the skill folder (skills_all/testing in Microck/ordinary-claude-skills) into .agents/skills/testing in your project. Codex loads it when a task matches its description.

Can I use Testing 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 Microck/ordinary-claude-skills --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.

What does Testing need to run?

Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (pnpm and docker). Our summary lists: Docker.

Does Testing access the network?

SKILL.md names 1 domain. As links in the text: testcontainers.com. This is read from the text; nothing was executed.

Is Testing 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 Testing use?

Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Testing use?

About 854 tokens (SKILL.md is roughly 3.4k 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 Testing?

Skills that share tags, products or a category with Testing: Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), Running Tests (NangoHQ/nango, 13k stars) and Slow Tests (UKGovernmentBEIS/inspect_ai, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

Microck (a GitHub user) maintains it in Microck/ordinary-claude-skills, which has 401 GitHub stars. The repository holds 97 skills in this directory. The repository was last updated on September 6, 2026.

Source: Microck/ordinary-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.