Code Solving
HoangTheQuyen/think-better
Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through 7 steps with evidence-based quality gates.
Find consequential behavior that a passing test suite does not establish, using focused exploratory checks.
Install Test Blindspots
$ npx skills add Neeeophytee/finding-unknowns-skills --skill test-blindspots -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills test-blindspots --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/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-blindspots .claude/skills/test-blindspots && 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 "test-blindspots" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspots into .claude/skills/test-blindspots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-blindspots", 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/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspotsType 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 Neeeophytee/finding-unknowns-skills --skill test-blindspots -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills test-blindspots --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-blindspots .agents/skills/test-blindspots && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-blindspots" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspots into .agents/skills/test-blindspots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-blindspots", 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 Neeeophytee/finding-unknowns-skills --skill test-blindspots -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills test-blindspots --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-blindspots .cursor/skills/test-blindspots && 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 "test-blindspots" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspots into .cursor/skills/test-blindspots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-blindspots", 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/Neeeophytee/finding-unknowns-skills.git --path skills/test-blindspots--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 Neeeophytee/finding-unknowns-skills --skill test-blindspots -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills test-blindspots --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-blindspots .gemini/skills/test-blindspots && 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 "test-blindspots" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspots into .gemini/skills/test-blindspots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-blindspots", 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 Neeeophytee/finding-unknowns-skills test-blindspotsInstalls 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 Neeeophytee/finding-unknowns-skills --skill test-blindspots -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-blindspots .github/skills/test-blindspots && 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 "test-blindspots" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspots into .github/skills/test-blindspots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-blindspots", 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 Neeeophytee/finding-unknowns-skills --skill test-blindspots -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills test-blindspots --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-blindspots .opencode/skills/test-blindspots && 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 "test-blindspots" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/test-blindspots into .opencode/skills/test-blindspots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-blindspots", 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
test-blindspots- GitHub stars
- 343
- Token cost
- ~676 tokens
- SKILL.md length
- 355 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Find consequential behavior that a passing test suite does not establish, using focused exploratory checks.
- Works in 6 steps: Establish the intended behavior and… → Compare important behavior with what the… → For each selected gap, state the… → …
- The user asks what green tests miss
- SKILL.md covers Steps and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Blindspots is an agent skill from Neeeophytee/finding-unknowns-skills. Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already failing test.
Its SKILL.md is about 680 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 generation, Test coverage and Failing and flaky tests. The repository describes itself as: 14 installable skills for Claude Code, OpenAI Codex, and Hermes: find unknowns, clarify requirements, manage context, test assumptions, and verify bug fixes with regression… The licence is MIT.
When your agent uses it
- The user asks what green tests miss
- Wants confidence in test coverage for a specific change
Example prompts
- “/test-blindspots”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish the intended behavior and scope from the request, specification, changed code, callers, and relevant tests. Run the relevant…
- Compare important behavior with what the tests actually assert. Look for a concrete gap: a mock replacing the boundary being claimed, an…
- For each selected gap, state the question and design a small exploratory probe that can distinguish correct from incorrect behavior. Use…
- Execute the bounded probes within scope. Record observed behavior and the requirement it contradicts. If intended behavior is unclear…
- For a confirmed failure, preserve a minimal reproducer. Add a focused regression test when test edits are within the task's scope; verify…
- Finish with confirmed defects first, then consequential untested risks or specification questions, the evidence for each, and what was not…
What it can do on your machine
Read from SKILL.md and the folder at commit ca5696a. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Test Blindspots loads about 676 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 355 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
The full file from Neeeophytee/finding-unknowns-skills at commit ca5696a, republished under its MIT licence (© Neeeophytee). 355 words, ~676 tokens.
Download SKILL.mdSave it as
.claude/skills/test-blindspots/SKILL.md (or your agent's skills folder).- name
- test-blindspots
- description
- Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already failing test.
Test blindspots
Passing tests establish their assertions under their setup. The gap to investigate is where the implementation and its tests share the same untested assumption.
Steps
- Establish the intended behavior and scope from the request, specification, changed code, callers, and relevant tests. Run the relevant baseline when possible. If it is already failing, report that limitation rather than describing it as green.
- Compare important behavior with what the tests actually assert. Look for a concrete gap: a mock replacing the boundary being claimed, an untested transition, a missing consumer expectation, or an invariant only exercised on the happy path. Choose by consequence and evidence, not by a generic checklist or coverage percentage.
- For each selected gap, state the question and design a small exploratory probe that can distinguish correct from incorrect behavior. Use existing tooling and isolated data. Prefer the actual component over a mock when the mock is the source of uncertainty.
- Execute the bounded probes within scope. Record observed behavior and the requirement it contradicts. If intended behavior is unclear, report a specification question; if execution is unavailable, report an untested risk. Neither is a confirmed defect.
- For a confirmed failure, preserve a minimal reproducer. Add a focused regression test when test edits are within the task's scope; verify that it fails for the intended reason. Report any deliberately failing reproducer separately from the baseline. Do not silently repair production code.
- Finish with confirmed defects first, then consequential untested risks or specification questions, the evidence for each, and what was not examined. Finding no consequential gap is a valid result.
Show full SKILL.md (86 more words)Show less
Guardrails
- Do not equate low coverage with a defect, or green tests with exhaustive correctness. A hypothetical scenario alone is not a finding.
- Preserve existing tests and assertions. Do not weaken a test, expand the refactor, or install an unrelated testing framework to produce a result.
- Keep probes away from production data and external side effects unless explicitly authorized. State when a local fixture cannot represent the real boundary.
- Keep this proportional to the change. Stop when further exploration is unlikely to alter the user's decision.
© Neeeophytee, 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 skills/test-blindspots of Neeeophytee/finding-unknowns-skills.
Open the folder on GitHubat commit ca5696a
Compare with similar skills
Test Blindspots 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 |
|---|---|---|---|---|---|---|
| Test Blindspots this skillNeeeophytee/finding-unknowns-skills | 343 | — | ~676 | Automated safety check: Pass | MIT | |
| Code SolvingHoangTheQuyen/think-better | 122 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Caliber Testingcaliber-ai-org/ai-setup | 1.3k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Offloadimbue-ai/offload | 125 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Write Testsopenplayerjs/openplayerjs | 649 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Test Debuggingruby-git/ruby-git | 1.8k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
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…
Offload
imbue-ai/offload
Activate when you see offload.toml in a repo, offload referenced in build targets (justfile, Makefile, scripts), or when you need to run a large test suite in parallel.
Write Tests
openplayerjs/openplayerjs
Write or extend Jest tests for OpenPlayerJS to this repo's exact conventions — makeCore factories, typed internals handles instead of as any, media property mocking, fake timers, ads/vast mocks, and…
Test Debugging
ruby-git/ruby-git
Debugs failing or flaky tests and improves test coverage. An agent skill from ruby-git/ruby-git.
QA Metrics
petrkindlmann/qa-skills
Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites.
More from Neeeophytee/finding-unknowns-skills
All 14 skills in this repoAgent Interface Design
Neeeophytee/finding-unknowns-skills
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples.
Assumption Test
Neeeophytee/finding-unknowns-skills
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach.
Blindspot Pass
Neeeophytee/finding-unknowns-skills
Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills.
Brainstorm Prototypes
Neeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.
Change Quiz
Neeeophytee/finding-unknowns-skills
After a working session, produce a report on what changed plus a quiz the user must pass before merging.
Context Audit
Neeeophytee/finding-unknowns-skills
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list.
Related
Categories
Questions about Test Blindspots
What does Test Blindspots do?
Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Test Blindspots is an agent skill from Neeeophytee/finding-unknowns-skills. Find consequential behavior that a passing test suite does not establish, using focused exploratory checks.
When should I use Test Blindspots?
Test Blindspots fits situations like: the user asks what green tests miss; wants confidence in test coverage for a specific change.
How do I install Test Blindspots in Claude Code?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill test-blindspots -a claude-code`. Or copy the skill folder (skills/test-blindspots in Neeeophytee/finding-unknowns-skills) into .claude/skills/test-blindspots in your project. Claude Code loads it when a task matches its description.
How do I install Test Blindspots in Codex?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill test-blindspots -a codex`. Or copy the skill folder (skills/test-blindspots in Neeeophytee/finding-unknowns-skills) into .agents/skills/test-blindspots in your project. Codex loads it when a task matches its description.
Can I use Test Blindspots 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 Neeeophytee/finding-unknowns-skills --skill test-blindspots -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-blindspots, .gemini/skills/test-blindspots, .github/skills/test-blindspots and .opencode/skills/test-blindspots in your project.
What does Test Blindspots need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Blindspots is instructions for the agent only.
Does Test Blindspots 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 Test Blindspots 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 Test Blindspots use?
Test Blindspots 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 Test Blindspots use?
About 676 tokens (SKILL.md is roughly 2.7k 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 Test Blindspots?
Skills that share tags, products or a category with Test Blindspots: Code Solving (HoangTheQuyen/think-better, 122 stars), Caliber Testing (caliber-ai-org/ai-setup, 1.3k stars), Offload (imbue-ai/offload, 125 stars) and Write Tests (openplayerjs/openplayerjs, 649 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Blindspots?
Neeeophytee (a GitHub user) maintains it in Neeeophytee/finding-unknowns-skills, which has 343 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 28, 2026.
Source: Neeeophytee/finding-unknowns-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.