agentsclimarketplace

Blindspot

Skill MaybeMonad/skills/skills/unknown-reduction/blindspot

Install
npx -y skills add MaybeMonad/skills --skill blindspot

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Pre-implementation blind spot pass for finding unknown unknowns before agentic coding, design, research, or domain work. Use when the user says blindspot pass, unknown unknowns, help me prompt better, I am new to this codebase/domain, I do not know what questions to ask, or wants relevant risks, hidden constraints, and cheap probes before implementation.

SKILL.md

2.3 KB, as published. Nobody here has run it

Blindspot

Use this skill to expose the unknowns that may make the user's prompt or plan misrepresent the real territory. The goal is to help the user prompt better and choose a safer next step before implementation gets expensive.

Workflow

  1. Establish the starting point:
    • What the user explicitly wants.
    • What they know, do not know, and can judge by taste.
    • The codebase, domain, runtime, data, references, or real-world system that forms the territory.
  2. Inspect before asking:
    • Search local files, docs, examples, screenshots, logs, or current external sources when those can answer factual unknowns.
    • State what was inspected and what is still uninspected.
  3. Classify important unknowns using references/unknowns-taxonomy.md.
  4. Prioritize only unknowns that can change architecture, scope, UX, correctness, safety, cost, or validation.
  5. For each major blindspot, give the cheapest probe: code search, reference read, prototype, user question, runtime check, test, or source lookup.
  6. End with a better prompt, plan constraint, or next artifact for the user to use.

Output Shape

Use this structure unless the user asks for another format:

  1. Starting point
  2. Territory inspected
  3. Top blindspots
  4. Cheap probes
  5. Better prompt
  6. Blocking questions

Rules

  • Lead with the unknowns that could most change the work.
  • Separate unknowns from risks. A risk is a known possible failure; an unknown is missing information that may reveal a different path.
  • Do not ask a broad questionnaire. Ask only questions whose answers change the next step.
  • Teach just enough vocabulary for the user to recognize better options.
  • If the right next step is not implementation, say so and name the artifact: brainstorm, prototype, interview, reference analysis, or plan review.

Resources

  • references/unknowns-taxonomy.md: read when producing the blindspot pass or when the task needs a structured unknown-card format.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.