AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

let-fate-decide

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over asking clarifying questions when the user's tone is casual or playful rather than precision-seeking.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read trailofbits--let-fate-decide at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 93

houses/03-third-house.md

Third House

Domain: Communication, learning, interfaces, and local connections

Core Meaning

The Third House describes exchange: names, messages, protocols, documentation, small decisions, and the local links between parts of a system.

Building New Projects

Use this house to shape APIs, component boundaries, naming, docs, schemas, and the early developer experience. It favors clarity over cleverness.

Vulnerability Discovery

Use this house to inspect parsers, protocol handling, serialization, deserialization, request routing, logs, CLI arguments, and any place where meaning crosses a boundary.

Correctness Verification

Use this house to verify contracts between components. It maps to type boundaries, message formats, state synchronization, error propagation, and whether two parts of the system agree on the same facts.

Technical Workflow Lenses

  • Audit pipeline: inspect parsers, schemas, protocol messages, logs, CLI arguments, and API contracts where meaning crosses a boundary.
  • Evidence mode: use parser fuzzing, schema tests, protocol diagrams, static rules, or spec-to-code comparisons.
  • Human context: improve names, docs, and report language when ambiguity is the thing creating risk.

Technical Prompt

Where is meaning being translated, and what misunderstanding would cause the system to fail?