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/05-fifth-house.md

Fifth House

Domain: Creativity, experimentation, expressiveness, and delight

Core Meaning

The Fifth House describes the creative opening. It points to prototypes, user delight, sharp examples, playful exploration, and the part of the work that benefits from imagination.

Building New Projects

Use this house to identify the prototype, demo path, interactive loop, or opinionated product choice that makes the project feel alive.

Vulnerability Discovery

Use this house to try unusual inputs, creative abuse cases, unexpected feature combinations, and behavior that appears harmless because it was built for convenience or delight. It maps to debug or demo endpoints, feature flags that skip validation, overly flexible APIs, upload or template features, and convenience modes that quietly bypass normal controls.

Correctness Verification

Use this house to generate examples, edge cases, model-based scenarios, property tests, and small experiments that reveal whether the abstraction behaves as intended.

Technical Workflow Lenses

  • Audit pipeline: turn intuition into concrete abuse cases, weird feature combinations, fuzz dictionaries, and exploratory probes.
  • Evidence mode: prefer prototypes, fuzz harnesses, property tests, mutation survivors, screenshots, or small proof-of-concept experiments.
  • Domain lens: in product and UX work, validate delight with real workflows rather than assuming novelty is useful.

Technical Prompt

Where would a creative experiment teach more than another round of analysis?