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

Testing

by wellwelwel in wellwelwel/poku

Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage.

MITAuto-check passedTesting & QA

Install Testing

skills CLI
$ npx skills add wellwelwel/poku --skill testing -a claude-code

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

GitHub CLI
$ gh skill install wellwelwel/poku 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/wellwelwel/poku.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/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
1.2k
Token cost
~1k tokens
SKILL.md length
477 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage.

  • Works in 7 steps: Test Structure → Test Commands → Test Patterns → …
  • Adding fixtures
  • Calls npm
  • Working on coverage

What it does

Testing is an agent skill from wellwelwel/poku. Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage. Use when writing, organizing, or running tests, adding fixtures, or working on coverage.

Its SKILL.md is about 1k 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 Containers and End-to-end testing. It works with Docker, npm and Deno. The repository describes itself as: 🐷 Poku makes testing easy for Node.js, Bun, Deno, and you at the same time. The licence is MIT.

When your agent uses it

  • Adding fixtures
  • Working on coverage

Example prompts

  • “/testing”

Requirements

  • Docker

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Test Structure
  2. Test Commands
  3. Test Patterns
  4. Test Utils (test/utils/)
  5. Fixtures (test/fixtures/)
  6. Docker Testing
  7. Coverage

What it can do on your machine

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

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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 1k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 477 words of instructions outside code blocks.

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

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 wellwelwel/poku at commit e02df0b, republished under its MIT licence (© wellwelwel). 477 words, ~1,003 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder).
name
testing
description
Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage. Use when writing, organizing, or running tests, adding fixtures, or working on coverage.

How tests are organized and where to look. Read the actual test/ tree to confirm details, since test files change over time.

1. Test Structure

Tests live under test/, organized by purpose:

  • test/unit/: core services and utilities
  • test/integration/: API surface by feature, with a subdirectory per feature (assertions, describe, it, test, strict assertions, before/after each, wait-for, etc.)
  • test/e2e/: CLI workflows, service management, and watch mode
  • test/compatibility/: Docker-based multi-version checks
  • test/__fixtures__/: scenario fixtures, mirroring the test structure
  • test/__utils__/: shared test helpers
  • test/__docker__/: Docker infrastructure (compose plus Dockerfiles)

Read the relevant directory to discover the current files. Poku tests itself, so these files also show how describe(), it(), test(), and assert are used in practice.

2. Test Commands

The package.json scripts are the source of truth. The main ones:

  • npm test: runs the unit, integration, and e2e suites on Node via tsx
  • npm run test:bun: same suites on the Bun runtime
  • npm run test:deno: same suites on Deno (with --denoAllow=all)
  • npm run test:coverage: runs npm test with the --coverage flag (c8 plus monocart-coverage-reports via @pokujs/c8)
  • npm run test:docker:node: runs the Docker compatibility matrix
3. Test Patterns

Open a representative file in the relevant directory to learn the pattern:

  • Unit: parallel assertions via Promise.all([it(...)])
  • Integration: comprehensive coverage of a single API surface per feature
  • E2E: service lifecycle with startService(), waitForPort(), and server.end()
  • Compatibility: @pokujs/docker lifecycle to run a suite inside a container

Comments are completely prohibited in tests. describe, it, test, assert, and strict all accept a message, so express intent through those instead.

Prefer value-preserving asserts over a derived boolean. assert(regex.test(x)) collapses failures to Actual: false / Expected: true. assert.match / assert.doesNotMatch print Value + RegExp, and assert.strictEqual / assert.deepStrictEqual print Actual + Expected. Split combined checks like a && b into independent assertions. A boolean assertion is acceptable only when no value-preserving form fits.

A bug-reproduction test asserts the correct expected behavior, so without a fix it MUST fail and pass only once the bug is fixed. Never write it to pass against the buggy behavior.

Show full SKILL.md (148 more words)Show less
4. Test Utils (test/__utils__/)

Shared helpers for writing tests:

  • inspectPoku(args, configs): run the CLI, capture stdout/stderr/exitCode
  • inspectCLI(command, args): generic CLI inspection
  • watchCLI(args, configs): monitor watch mode via a getOutput() callback
  • legacyFetch(host, port): HTTP fetch for Node 16 compatibility
5. Fixtures (test/__fixtures__/)

Fixtures provide controlled scenarios and mirror the test structure (unit/, integration/, e2e/). They cover cases such as config files, HTTP servers, pass/fail outcomes, fail-fast, file discovery, module types (CJS/ESM/TypeScript), reporters, and watch mode. Read test/__fixtures__/ to find an existing scenario or to add a new one next to its peers.

6. Docker Testing
  • Filter the version: FILTER=node-<version> npm run test:docker:node
  • Compose file: test/__docker__/docker-compose.yml
  • Runs against the built ci/ (NODE_ENV=build, .js)
7. Coverage
  • Minimum threshold lives in .nycrc (checkCoverage, the source of truth). The goal is 100%
  • Preference: E2E or integration tests for coverage. Use unit tests only for extremely complex or hard-to-reproduce scenarios, such as watch usage

© wellwelwel, MIT. 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/testing of wellwelwel/poku.

Open the folder on GitHubat commit e02df0b

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 skillwellwelwel/poku1.2k—~1kAutomated safety check: PassMIT
Acarshub Tool Additionssdr-enthusiasts/docker-acarshub117—~707Automated safety check: PassGPL-3.0
Run Dashboard E2E Local ChangesBlackBeltTechnology/pi-agent-dashboard315—~1.3kAutomated safety check: PassMIT
Crabbox SetupAI-Builder-Club/skills1.3k1 repos~1.9kAutomated safety check: NotesNone
Dqd Labctrsploit/ctrsploit154—~1.6kAutomated safety check: PassNone
Openclaw Docker E2E Authoringopenclaw/openclaw392k—~593Automated safety check: PassMIT

Similar skills

  • Acarshub Tool Additions

    sdr-enthusiasts/docker-acarshub

    Use ONLY when working in the docker-acarshub repository AND a task may require adding a system tool, npm package, or other dependency.

    117 GitHub stars~707 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Run Dashboard E2E Local Changes

    BlackBeltTechnology/pi-agent-dashboard

    Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.

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

  • Crabbox Setup

    AI-Builder-Club/skills

    Scaffold an isolated CLOUD dev box per agent (via crabbox + Daytona) for any codebase — the parallel-safe counterpart to dev-local-setup.

    1.3k GitHub starsUsed in 1 repo~1.9k tokens
    Testing & QAAuto-check: notes

  • Dqd Lab

    ctrsploit/ctrsploit

    Manage ctrsploit dqd lab environments from github.com/ctrsploit/dqd.

    154 GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Openclaw Docker E2E Authoring

    openclaw/openclaw

    Author OpenClaw Docker E2E and live provider Docker lanes. An agent skill from openclaw/openclaw.

    392k GitHub stars~593 tokensUpdated today
    Testing & QAAuto-check passed

  • Release Openclaw Plugin Testing

    openclaw/openclaw

    Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E…

    392k GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed

More from wellwelwel/poku

  • Benchmarking

    wellwelwel/poku

    Empirical performance comparison playbook for poku covering hypothesis lenses, a standalone harness with a byte-identical correctness gate, variant generation, sequential hyperfine measurement…

    1.2k GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed

  • Architecture

    wellwelwel/poku

    Architecture deep-dive for poku covering project structure, execution flow, config discovery, runtime detection, and competitive context.

    1.2k GitHub stars~867 tokensUpdated 3 mo ago
    Auto-check passed

  • Documentation

    wellwelwel/poku

    Documentation deep-dive for the poku website covering Docusaurus setup, language policy, feature-to-docs mapping, conventions, JSDoc, and the changelog.

    1.2k GitHub stars~982 tokensUpdated 3 mo ago
    Auto-check passed

  • Engineering

    wellwelwel/poku

    Engineering deep-dive for poku covering performance, code, and security patterns, TypeScript config, build pipeline, developer experience, and CI/CD.

    1.2k GitHub stars~1.4k tokensUpdated 3 mo ago
    Auto-check passed

  • Pre Commit

    wellwelwel/poku

    Run the mandatory pre-commit checks for the poku repository before staging a commit.

    1.2k GitHub stars~728 tokensUpdated 3 mo ago
    Auto-check passed

Works with

Categories

Questions about Testing

What does Testing do?

Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage. Testing is an agent skill from wellwelwel/poku. Testing deep-dive for poku covering test structure, commands, patterns, fixtures, utils, Docker compatibility, and coverage.

When should I use Testing?

Testing fits situations like: adding fixtures; working on coverage.

How do I install Testing in Claude Code?

Run `npx skills add wellwelwel/poku --skill testing -a claude-code`. Or copy the skill folder (.claude/skills/testing in wellwelwel/poku) 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 wellwelwel/poku --skill testing -a codex`. Or copy the skill folder (.claude/skills/testing in wellwelwel/poku) 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 wellwelwel/poku --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 (npm). Our summary lists: Docker.

Does Testing access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. 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 is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing use?

About 1k tokens (SKILL.md is roughly 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: Acarshub Tool Additions (sdr-enthusiasts/docker-acarshub, 117 stars), Run Dashboard E2E Local Changes (BlackBeltTechnology/pi-agent-dashboard, 315 stars), Crabbox Setup (AI-Builder-Club/skills, 1.3k stars) and Dqd Lab (ctrsploit/ctrsploit, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

wellwelwel (a GitHub user) maintains it in wellwelwel/poku, which has 1,183 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 18, 2026.

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