Borrowing it
Nothing to install: this file belongs to BloomBooks/BloomDesktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BloomBooks/BloomDesktop/master/.claude/skills/improve-test-automation-coverage/SKILL.mdgit clone --depth 1 https://github.com/BloomBooks/BloomDesktopWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bloombooks/bloomdesktop/improve-test-automation-coverage)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/improve-test-automation-coverage"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/improve-test-automation-coverage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/improve-test-automation-coverage"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/improve-test-automation-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00136 | $0.04130 |
| Opus 5.5 | $0.00054 | $0.01652 |
| Sonnet 5.5 | $0.00027 | $0.00826 |
| Haiku 4.5 | $0.00014 | $0.00413 |
Grade A, and why
improve-test-automation-coverage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve test automation coverage
Turn N manual test cases into edge-to-edge tests, in parallel, with one Orca worktree and one Claude Fable 5.1 worker per case. You are the controller: you pick and claim the cases, start the workers, answer their review requests, and report. The workers write the tests and open the PRs. The developer answers worker questions in Orca.
Files beside this skill:
notion_automation.py— list, show, claim, and update cards. Run it withpy.e2e-lock.mjs— the machine-wide lock every Playwright run goes through. Workers use it; you use it too if you ever run a test yourself.worker-brief.md— the task brief template for a worker.
Related skills: .claude/skills/add-e2e-test/SKILL.md (what a worker follows), orchestration
and orca-cli (Orca mechanics; run orca skills get orchestration first, the guide is
version-matched), preflight (the worker runs it to open the PR), personal-board.
Authorization
Invoking this skill authorizes, for this run only: setting the Automation and
Automation Notes properties of Notion test cards; creating Orca worktrees and workers; and,
inside each worker, everything preflight authorizes (commit, push, draft PR, bot replies). Still
forbidden: marking a PR ready for review, moving any Orca card to Peer Review, setting a card to
Automated or Keep manual (a human does both, after merge or after judging the case).
Constants
- Notion database "Test Case Runs", suite run
6.5(the current release; change--suitewhen the team moves on). Token:BLOOM_TESTCASE_NOTION, Windows User scope. In PowerShell:$env:BLOOM_TESTCASE_NOTION = [Environment]::GetEnvironmentVariable('BLOOM_TESTCASE_NOTION','User') - Base branch for every worktree and PR:
master. The BloomE2E system lives on master; pass--base-branch masterexplicitly, do not rely on the Orca repo default. This is the exceptionAGENTS.mdallows to its "new work targets Version6.5" rule: an e2e test cannot target a branch that has nosrc/BloomE2E. - Worker agent:
claude, modelclaude-fable-5-1. - Default N: 3. N is a maximum; if fewer Planned cards exist, take what there is and say so.
- Worktree name:
tc<TestCaseID>-<one to three words from the title>, for exampletc349-duplicate-page. There is no YouTrack card for this work, so theBL-prefix rule does not apply;preflightfinding no ticket id is the expected outcome.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +244 lines · +58 tokens per session 32c8004b6879
- 1mo ago Changed · -1 lines d5919da5ce68
- 1mo ago First seen · 12 lines · 78 tokens per session scan A 88c83bcd7e0d
improve-test-automation-coverage is a skill published in the GitHub repository BloomBooks/BloomDesktop (43 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 4,130 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.