AgentStack
SKILL verified MIT Self-run

Blindspot

skill-tommylower-cortex-blindspot · by tommylower

Pre-mortem pass before infra, deploy, data-model, or unfamiliar-territory work. Surfaces unknown unknowns by cross-referencing the task against past gotchas in memory and the actual repo surfaces it touches. Use before schema changes, deploys, auth work, or any task in territory the user hasn't worked in. Triggers on "blindspot pass", "blind spots", "unknown unknowns", "what am i missing".

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-tommylower-cortex-blindspot

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Blindspot? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

before implementing, find what the prompt doesn't know it's missing. the goal is to pre-pay gotchas that would otherwise become debugging sessions.

process

  1. classify the territory. restate the task in one line and name the surfaces it touches: deploy config, database schema, migrations, auth, env vars, external services, unfamiliar domain.
  1. sweep memory for prior incidents. read the memory index and any gotcha/reference files matching this territory. past incidents in the same territory are the strongest predictor of the next one.
  1. sweep the actual repo surfaces. don't reason from the prompt alone. inspect the real deploy config, schema and migration state, env var usage, middleware, and anything the task assumes but doesn't state. check whether prod and local actually match where the task assumes they do.
  1. report ranked blindspots. for each one: what could break, how you'd find out (loud prod failure vs silent drift), and the cheapest probe to de-risk it right now. rank by blast radius, not likelihood. lead with anything that takes down prod.
  1. end with a prompt upgrade. rewrite the original task prompt with the discovered constraints baked in, ready to paste into a fresh implementation session. include this standing instruction in it:

> keep an implementation-notes.md. if an edge case forces a deviation from the plan, pick the conservative option, log it under "deviations", and keep going.

notes

  • if a blindspot can be resolved by reading code or running a cheap read-only command, resolve it in-pass instead of reporting it as open.
  • this is not a code review or a plan review. it only hunts for the gap between what the prompt assumes and what the territory actually is.
  • complement to grill-me: grill-me stress-tests a plan the user has. blindspot hunts for what neither the user nor the plan has considered.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.