Skip to content
cccskills
FreePublished on GitHub

blindspot-pass

Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Blindspot pass

The user is about to work in territory they don't know well. Your job is not to do the task yet. Your job is to show them what they don't know they don't know, so their next prompt is better.

Steps

  1. Ask (or infer from context) two things: what they're trying to do, and what their experience level is with this specific area. Their starting point changes everything.
  2. Explore the relevant territory yourself: the module, its history, its conventions, prior art in the repo, and (if the domain is external) what practitioners consider table stakes.
  3. Report back in four sections:
    • Landmines — the mistakes someone new here typically makes, and any repo-specific potholes (deprecated paths, misleading names, half-migrated patterns).
    • Hidden context — decisions already made that constrain the work (why the code is shaped this way, invariants that must hold).
    • What good looks like — 2-3 examples of the pattern done well, from this repo or elsewhere, so they can calibrate quality.
    • Questions you should be asking — the 3-5 questions an expert would ask before starting, with your best guess at each answer.
  4. End with a rewritten version of their original request that incorporates what you found, so they can see the difference between their map and the territory.

Guardrails

  • Do not start implementing. This skill ends at understanding.
  • Prioritize unknowns that would change the architecture or the approach over trivia.
  • If the area turns out to be simpler than the user feared, say so plainly. "You have no significant blindspots here" is a valid and valuable result.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

The English summary is being prepared. Showing the original description.

Neeeophytee/finding-unknowns-skills353Updated Sep 28, 2026

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

The English summary is being prepared. Showing the original description.

Neeeophytee/finding-unknowns-skills353Updated Sep 28, 2026

Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

The English summary is being prepared. Showing the original description.

Neeeophytee/finding-unknowns-skills353Updated Sep 28, 2026

After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

The English summary is being prepared. Showing the original description.

Neeeophytee/finding-unknowns-skills353Updated Sep 28, 2026

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. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

The English summary is being prepared. Showing the original description.

Neeeophytee/finding-unknowns-skills353Updated Sep 28, 2026

Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.

The English summary is being prepared. Showing the original description.

Neeeophytee/finding-unknowns-skills353Updated Sep 28, 2026

See all skills by Neeeophytee

Report a problem with this skill