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/10-tenth-house.md

Tenth House

Domain: Delivery, reputation, public outcome, and long-term direction

Core Meaning

The Tenth House describes what the work becomes in public. It points to shipping, reliability, responsibility, reputation, leadership, and the outcome that will be judged by others.

Building New Projects

Use this house to define the release target, production bar, operational ownership, success metrics, and what must be true before the work is fit to ship.

Vulnerability Discovery

Use this house to prioritize exploitable, high-impact findings over merely interesting behavior. It maps to production exposure, impact, likelihood, blast radius, and reportability.

Correctness Verification

Use this house to focus on user-visible guarantees, service-level behavior, release blockers, acceptance criteria, and whether correctness holds in the environment where the system will be judged.

Technical Workflow Lenses

  • Audit pipeline: prioritize reportable impact, exploitability, remediation clarity, release blockers, and regression coverage.
  • Evidence mode: use production telemetry, acceptance tests, reproducible PoCs, severity scoring, report drafts, and stakeholder-ready summaries.
  • Human context: make accountability explicit: who signs off, who communicates, and what must be true before shipping.

Technical Prompt

What outcome will this work be accountable for once it leaves the workbench?