circumspicere

Survey runtime behavior, egress, and documentation claims to identify blind spots.

Updated May 20, 2026
One-click install
npx skills add https://github.com/watmin/datamancy.dev --skill circumspicere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: circumspicere
Source: https://github.com/watmin/datamancy.dev/tree/main/circumspicere
Command: npx skills add https://github.com/watmin/datamancy.dev --skill circumspicere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Circumspicere reveals the blind spots that inward guards miss by surveying the surrounding runtime: default behavior, egress surfaces, claims encoded in documentation, and unenforced invariants.

Core Features & Use Cases

  • Perimeter survey: assesses the surround to surface gaps between code, claims, and runtime behavior.
  • Threat-surface awareness: identifies negative space and unexamined paths to prevent silent failures.
  • Audit-ready findings: provides a structured view for security reviews or code audits.

Quick Start

Cast circumspicere after inward wards report to surface what the surround left uncovered.

Frequently Asked Questions about circumspicere

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find security blind spots in runtime behavior and default egress paths?

To find security blind spots in runtime behavior, survey the surrounding perimeter to surface gaps between code, claims, and default egress. This reveals unexamined paths and negative space to prevent silent failures during security reviews.

What is the best way to audit claims versus code for unenforced invariants?

Auditing claims versus code involves surveying shipped documentation to enforce alignment with relied-on invariants. This process surfaces untested or unenforced aspects of the artifact, providing structured findings for remediation.

How do I perform a perimeter survey after an inward security ward report?

Perform a perimeter survey after inward wards report to surface what the surround left uncovered. Cast an analysis to assess default behavior and egress surfaces, revealing hidden blind spots missed by inward guards.

Does this approach reveal untested paths in quality assurance audits?

Yes, revealing untested paths in quality assurance audits requires identifying negative space and unexamined runtime paths. This provides an audit-ready, structured view of gaps between the artifact's promises and its actual behavior.

Why do inward guards miss hidden blind spots during runtime audits?

Inward guards miss hidden blind spots because they lack perimeter awareness of default behavior and documentation claims. Surveying the surround enforces alignment between code and relied-on invariants, surfacing unexamined paths for remediation.

Can I use this for security reviews needing visibility beyond inward spell reports?

Yes, security reviews needing visibility beyond inward spell reports benefit from surveying the surrounding runtime. This assesses default egress and claims encoded in documentation to surface unenforced invariants and negative space.