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/07-seventh-house.md

Seventh House

Domain: Partnership, contracts, users, and external counterparts

Core Meaning

The Seventh House describes the other side of the relationship. It points to users, peers, APIs, vendors, collaborators, adversaries, and any contract that requires two parties to agree.

Building New Projects

Use this house to shape user workflows, integration contracts, partner APIs, permissions, handoffs, and the obligations the system accepts on behalf of others.

Vulnerability Discovery

Use this house to examine trust between parties: authentication, authorization, delegation, OAuth flows, webhooks, multi-tenant boundaries, and third-party integrations.

Correctness Verification

Use this house to verify contracts, compatibility, permissions, cross-service state, idempotency, and behavior at integration boundaries.

Technical Workflow Lenses

  • Audit pipeline: inspect authentication, authorization, delegation, webhooks, OAuth flows, vendors, and multi-tenant boundaries.
  • Evidence mode: use integration tests, contract tests, permission matrices, captured traffic, and cross-service traces.
  • Human context: clarify obligations between teams, users, APIs, reviewers, and external counterparties.

Technical Prompt

Who is on the other side of this interface, and what agreement could fail under pressure?