Project-level blind spot audit and BLINDSPOTLEDGER.md triage. Use for ledger-triage or ledger cleanup after an audit: organize, close, process, decide, handle, or go through existing ledger findings/items/rows, including equivalent non-English requests. Also use for blindspot passes, unknown-unknown audits, hidden risks, missing decisions, stale assumptions, readiness/gap/health checks beyond the owner's own checklist, unfamiliar-domain planning, cross-project sanity checks, and post-implementation review. Works across software, games, writing, research, content, and business plans. Ledger triage is consent-gated: collect owner choices before applying status, awareness, archive, or decision-packet edits. Do not trigger for routine bug fixes, ordinary code review, formatting, or implementation-only requests unless the user also asks what they may be missing, risking, overlooking, or cleaning up in the blindspot ledger.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryScience & researchStars0
About this skill
Project-level blind spot audit and BLINDSPOTLEDGER.md triage. Use for ledger-triage or ledger cleanup after an audit: organize, close, process, decide, handle, or go through existing ledger findings/items/rows, including equivalent non-English requests. Also use for blindspot passes, unknown-unknown audits, hidden risks, missing decisions, stale assumptions, readiness/gap/health checks beyond the owner's own checklist, unfamiliar-domain planning, cross-project sanity checks, and post-implementation review. Works across software, games, writing, research, content, and business plans. Ledger triage is consent-gated: collect owner choices before applying status, awareness, archive, or decision-packet edits. Do not trigger for routine bug fixes, ordinary code review, formatting, or implementation-only requests unless the user also asks what they may be missing, risking, overlooking, or cleaning up in the blindspot ledger.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Project-level blind spot audit and BLINDSPOT_LEDGER.md triage. Use for ledger-triage or ledger cleanup after an audit: organize, close, process, decide, handle, or go through existing ledger findings/items/rows, including equivalent non-English requests. Also use for blindspot passes, unknown-unknown audits, hidden risks, missing decisions, stale assumptions, readiness/gap/health checks beyond the owner's own checklist, unfamiliar-domain planning, cross-project sanity checks, and post-implementation review. Works across software, games, writing, research, content, and business plans. Ledger triage is consent-gated: collect owner choices before applying status, awareness, archive, or decision-packet edits. Do not trigger for routine bug fixes, ordinary code review, formatting, or implementation-only requests unless the user also asks what they may be missing, risking, overlooking, or cleaning up in the blindspot ledger.
About this listing
Category
Science & research
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.