Install
$ agentstack add skill-greatmark-fable-field-guide-skills-blindspot-pass ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Blindspot Pass
Help the user discover their unknown unknowns before work starts. This is a read-only pass: do not modify any files.
Workflow
- Anchor on the user's starting point. If not already clear from the
conversation, ask once — a single short message, at most three sub-questions — about their experience with this problem and codebase, what they have already decided, and what they plan to do next.
- Explore the territory. Search the relevant code, docs, git history, and
(if the domain is unfamiliar) the web. Look specifically for things the user did not mention in their description of the task.
- Report blindspots, organized as:
- Questions you didn't know to ask — decisions hidden in this area
(existing conventions, invariants, feature flags, edge cases).
- What "good" looks like — quality bars, reference implementations, or
prior art the user should calibrate against.
- History and potholes — past attempts, known pitfalls, TODO/FIXME
landmines, coupling that will bite.
- Domain concepts — if the domain is new to the user, teach the 3-5
concepts they need to evaluate results (not an encyclopedia).
- End with "how to prompt me better": 3-6 concrete things the user should
specify in their next prompt now that these blindspots are visible.
Rules
- Prioritize blindspots that would change the user's approach; skip trivia.
- Cite files and line numbers so claims are checkable.
- If the area turns out to be simple with few blindspots, say so plainly
instead of inventing findings.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GreatMark
- Source: GreatMark/fable-field-guide-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.