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.
Aggregates Vitest v8/Istanbul coverage across Tachi workspaces via tachi-coverage-tools (manifest, CLI, optional programmatic API).
Install Coverage Tools
$ npx skills add zkldi/Tachi --skill coverage-tools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zkldi/Tachi coverage-tools --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zkldi/Tachi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/coverage-tools .claude/skills/coverage-tools && rm -rf skills-srcUse ~/.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/
Install the "coverage-tools" agent skill from https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-tools into .claude/skills/coverage-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-tools", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-toolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zkldi/Tachi --skill coverage-tools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zkldi/Tachi coverage-tools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zkldi/Tachi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/coverage-tools .agents/skills/coverage-tools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "coverage-tools" agent skill from https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-tools into .agents/skills/coverage-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-tools", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zkldi/Tachi --skill coverage-tools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zkldi/Tachi coverage-tools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zkldi/Tachi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/coverage-tools .cursor/skills/coverage-tools && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "coverage-tools" agent skill from https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-tools into .cursor/skills/coverage-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-tools", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zkldi/Tachi.git --path .cursor/skills/coverage-tools--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zkldi/Tachi --skill coverage-tools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zkldi/Tachi coverage-tools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zkldi/Tachi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/coverage-tools .gemini/skills/coverage-tools && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "coverage-tools" agent skill from https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-tools into .gemini/skills/coverage-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-tools", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zkldi/Tachi coverage-toolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zkldi/Tachi --skill coverage-tools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zkldi/Tachi.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/coverage-tools .github/skills/coverage-tools && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "coverage-tools" agent skill from https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-tools into .github/skills/coverage-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-tools", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zkldi/Tachi --skill coverage-tools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zkldi/Tachi coverage-tools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zkldi/Tachi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/coverage-tools .opencode/skills/coverage-tools && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "coverage-tools" agent skill from https://github.com/zkldi/Tachi/tree/main/.cursor/skills/coverage-tools into .opencode/skills/coverage-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coverage-tools", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
coverage-tools- GitHub stars
- 237
- Token cost
- ~580 tokens
- SKILL.md length
- 184 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Aggregates Vitest v8/Istanbul coverage across Tachi workspaces via tachi-coverage-tools (manifest, CLI, optional programmatic API).
- Measuring test coverage
- SKILL.md covers When to use, Prerequisite, Commands (repo root) and Registering a new Vitest package, plus 2 more sections
- Calls just and bun
- Reviewing coverage after changes
What it does
Coverage Tools is an agent skill from zkldi/Tachi. Aggregates Vitest v8/Istanbul coverage across Tachi workspaces via tachi-coverage-tools (manifest, CLI, optional programmatic API). Use when measuring test coverage, reviewing coverage after changes, adding CI gates, registering a new Vitest package, or when the user mentions coverage reports, coverage-final.json, or just coverage-report.
Its SKILL.md is about 580 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 Test coverage and Unit testing. It works with Vitest and TypeScript. The repository describes itself as: A Cutting-Edge, Modular Score Tracker.
When your agent uses it
- Measuring test coverage
- Reviewing coverage after changes
- Adding CI gates
- Registering a new Vitest package
Example prompts
- “Use the coverage-tools skill to aggregate Vitest v8/Istanbul coverage across Tachi workspaces via tachi-coverage-tools (manifest, CLI, optional…”
- “/coverage-tools”
What it can do on your machine
Read from SKILL.md and the folder at commit 7e7801c. 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:
justbun
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
Coverage Tools loads about 580 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 184 words of instructions outside code blocks.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 184 words (~580 tokens).
“Coverage JSON is produced by Vitest v8 with --coverage (e.g. just test-typescript). Output is under each package’s coverage/ directory (gitignored). If reports are missing, run tests with coverage first.”
- name
- coverage-tools
Files
Just SKILL.md in .cursor/skills/coverage-tools of zkldi/Tachi.
Open the folder on GitHubat commit 7e7801c
Compare with similar skills
Coverage Tools 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Coverage Tools this skillzkldi/Tachi | 237 | — | ~580 | Automated safety check: Pass | None | |
| Test Writing WorkflowiOfficeAI/AionUi | 33k | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Mutation Testingsecondsky/claude-skills | 227 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Creating A Packagec15t/c15t | 1.9k | — | ~913 | Automated safety check: Pass | Apache-2.0 | |
| Caliber Testingcaliber-ai-org/ai-setup | 1.3k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT |
Similar skills
Mutation Testing
secondsky/claude-skills
Validate test effectiveness with mutation testing using Stryker (TypeScript/JavaScript with Vitest or bun test via @hughescr/stryker-bun-runner) and mutmut (Python).
Creating A Package
c15t/c15t
Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t.
Caliber Testing
caliber-ai-org/ai-setup
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…
Svelte Testing
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
Effect TS
tellahq/opensession
Write idiomatic Effect v4 TypeScript verified against the pinned effect@4.0.0-rc.112 source.
More from zkldi/Tachi
Actions And Pg Migration
zkldi/Tachi
Patterns for writing actions (MakeAction/MakeAnonAction), using the Postgres DB (Kysely), and migrating Express routes from MongoDB to Postgres in the Tachi server.
DB Formats
zkldi/Tachi
Guidance on using db-formats/ column lists (SELECT) and document mappers (ToDocument) instead of selectAll() when writing Postgres-backed endpoints in the Tachi server.
Exhaustive Switch
zkldi/Tachi
Prefer staticAssertUnreachable in the default branch of switches that must cover every variant of a union, so exhaustiveness is checked at compile time.
Preserve Comments
zkldi/Tachi
Preserves existing code comments (line, block, JSDoc, region markers) when editing files; does not delete or collapse comments for brevity unless the user asked to remove or update them.
Related
Works with
Categories
Questions about Coverage Tools
What does Coverage Tools do?
Aggregates Vitest v8/Istanbul coverage across Tachi workspaces via tachi-coverage-tools (manifest, CLI, optional programmatic API). Coverage Tools is an agent skill from zkldi/Tachi. Aggregates Vitest v8/Istanbul coverage across Tachi workspaces via tachi-coverage-tools (manifest, CLI, optional programmatic API).
When should I use Coverage Tools?
Coverage Tools fits situations like: measuring test coverage; reviewing coverage after changes; adding CI gates; registering a new Vitest package.
How do I install Coverage Tools in Claude Code?
Run `npx skills add zkldi/Tachi --skill coverage-tools -a claude-code`. Or copy the skill folder (.cursor/skills/coverage-tools in zkldi/Tachi) into .claude/skills/coverage-tools in your project. Claude Code loads it when a task matches its description.
How do I install Coverage Tools in Codex?
Run `npx skills add zkldi/Tachi --skill coverage-tools -a codex`. Or copy the skill folder (.cursor/skills/coverage-tools in zkldi/Tachi) into .agents/skills/coverage-tools in your project. Codex loads it when a task matches its description.
Can I use Coverage Tools 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 zkldi/Tachi --skill coverage-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coverage-tools, .gemini/skills/coverage-tools, .github/skills/coverage-tools and .opencode/skills/coverage-tools in your project.
What does Coverage Tools need to run?
Going by SKILL.md and its folder, Coverage Tools needs the command-line tools its instructions call (just and bun).
Does Coverage Tools 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 Coverage Tools 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 Coverage Tools use?
No licence was found for Coverage Tools or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Coverage Tools use?
About 580 tokens (SKILL.md is roughly 2.3k 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 Coverage Tools?
Skills that share tags, products or a category with Coverage Tools: Test Writing Workflow (iOfficeAI/AionUi, 33k stars), Mutation Testing (secondsky/claude-skills, 227 stars), Creating A Package (c15t/c15t, 1.9k stars) and Caliber Testing (caliber-ai-org/ai-setup, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Coverage Tools?
zkldi (a GitHub user) maintains it in zkldi/Tachi, which has 237 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 5, 2026.
Source: zkldi/Tachi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.