caliber-testing SKILL.md skillA

caliber-testing from caliber-ai-org/ai-setup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add caliber-ai-org/ai-setup/caliber-testing@git:20260402.460f56e

Pins git:20260402.460f56e in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
caliber-ai-org/ai-setup
Path
.claude/skills/caliber-testing/SKILL.md
Versions recorded
5
Latest version
git:20260402.460f56e, committed Apr 2, 2026
First version recorded
Mar 19, 2026
Size
12,945 bytes
Repository stars
1,316
License
MIT

Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment variable save/restore in beforeEach/afterEach, vi.clearAllMocks() lifecycle, and test file organization. Use when user says 'write tests', 'add test coverage', 'test this', creates *.test.ts files, or when test failures appear in CI. Do NOT use for non-test code or for debugging without writing tests.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Caliber Testing

## Critical

- All test files MUST be placed in `__tests__/` directories parallel to source files: `src/[module]/__tests__/[module].test.ts`
- Register any new `__tests__/` directories in `vitest.config.ts`'s `include` glob (already configured: `src/**/*.test.ts`)
- NEVER mock `src/test/setup.ts` — it is the global LLM provider mock already applied to all tests
- Environment variable tests MUST save `process.env` in `beforeEach`, restore in `afterEach`, and explicitly delete env vars to test absence
- Temporary file/directory cleanup MUST happen in `afterEach`, not in individual test cleanup. Use `fs.rmSync(dir, { recursive: true, force: true })`
- When a test requires unmocking modules mocked in global setup, call `vi.unmock('../module.js')` BEFORE the import statement
- Run `pnpm test` locally and `pnpm test:coverage` before committing to verify coverage thresholds (lines: 50, functions: 50, branches: 50, statements: 50)

## Instructions

### Step 1: Create the test file in the correct directory
Create `src/[module]/__tests__/[module].test.ts`. The parent source file is `src/[module]/[module].ts`.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_nmkoi2anid6qlec5/9444971184e66b30dea74dcf41567bf0939cec8aa09e24778fb877639f8cacb0.json

Then /plugin install caliber-testing@markdownregistry-nmkoi2anid6qlec5 in Claude Code. It installs git:20260402.460f56e, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add caliber-ai-org/ai-setup/caliber-testing@sha256:9444971184e66b30

The line at the top of this page pins the label git:20260402.460f56e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_nmkoi2anid6qlec5.svg)](https://markdownregistry.com/a/art_nmkoi2anid6qlec5)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in caliber-ai-org/ai-setup/caliber-testing since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of caliber-testing from somewhere else? Ask it: where did my caliber-testing come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Mar 19, 2026 and Apr 2, 2026, about one every 4 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260402.460f56e latest2026-04-02 460f56e 12,945 BA view · diff
git:20260330.4e5d8f62026-03-30 4e5d8f6 7,382 BC view · diff
git:20260329.8cf93fd2026-03-29 8cf93fd 6,356 BA view · diff
git:20260323.a0915792026-03-23 a091579 7,363 BA view · diff
git:20260319.c97e02c2026-03-19 c97e02c 9,105 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (12945 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

caliber-ai-org/ai-setup · 1,316 stars · license MIT · pushed 2026-09-24 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_nmkoi2anid6qlec5
GET https://markdownregistry.com/api/v1/resolve?ref=caliber-ai-org/ai-setup/caliber-testing
GET https://markdownregistry.com/api/v1/blob/9444971184e66b30dea74dcf41567bf0939cec8aa09e24778fb877639f8cacb0

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from caliber-ai-org/ai-setup

adding-a-command SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/adding-a-command/SKILL.md · Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in…
git:20260428.99f2785 · audit A · 1,316 stars
caliber-testing SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/caliber-testing/SKILL.md · Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted()…
git:20260428.99f2785 · audit A · 1,316 stars
find-skills SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/find-skills/SKILL.md · Discovers and installs community skills from the public registry. Use when the user mentions a technology, framework…
git:20260329.8cf93fd · audit A · 1,316 stars
llm-provider SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/llm-provider/SKILL.md · Adds a new LLM provider implementing LLMProvider interface with call() and stream() methods. Integrates with provider…
git:20260428.99f2785 · audit A · 1,316 stars
save-learning SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/save-learning/SKILL.md · Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do…
git:20260329.8cf93fd · audit A · 1,316 stars
scoring-checks SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/scoring-checks/SKILL.md · Add a new deterministic scoring check in src/scoring/checks/ that evaluates config quality. Follows the Check[] return…
git:20260428.99f2785 · audit A · 1,316 stars
setup-caliber SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/setup-caliber/SKILL.md · Sets up Caliber for automatic AI agent context sync. Installs pre-commit hooks so CLAUDE.md, Cursor rules, and Copilot…
git:20260329.8cf93fd · audit A · 1,316 stars
writers-pattern SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/writers-pattern/SKILL.md · Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform…
git:20260428.99f2785 · audit A · 1,316 stars
adding-a-command SKILL.md skill
caliber-ai-org/ai-setup · .claude/skills/adding-a-command/SKILL.md · Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in…
git:20260402.460f56e · audit A · 1,316 stars
find-skills SKILL.md skill
caliber-ai-org/ai-setup · .claude/skills/find-skills/SKILL.md · Discovers and installs community skills from the public registry. Use when the user mentions a technology, framework…
git:20260319.c97e02c · audit A · 1,316 stars
llm-provider SKILL.md skill
caliber-ai-org/ai-setup · .claude/skills/llm-provider/SKILL.md · Adds a new LLM provider implementing LLMProvider interface with call() and stream() methods. Integrates with provider…
git:20260402.460f56e · audit A · 1,316 stars
save-learning SKILL.md skill
caliber-ai-org/ai-setup · .claude/skills/save-learning/SKILL.md · Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do…
git:20260319.c97e02c · audit A · 1,316 stars

Every file in caliber-ai-org/ai-setup

Other files named caliber-testing

caliber-testing SKILL.md skill
caliber-ai-org/ai-setup · .agents/skills/caliber-testing/SKILL.md · Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted()…
git:20260428.99f2785 · audit A · 1,316 stars
caliber-testing SKILL.md skill
caliber-ai-org/ai-setup · .cursor/skills/caliber-testing/SKILL.md · Writes Vitest tests following project patterns: __tests__/ directories, vi.mock() for module mocking with vi.hoisted()…
git:20260428.99f2785 · audit A · 1,316 stars

Browse by kind, by grade A, or by owner.