AgentStack
SKILL verified MIT Self-run

Divination Philosopher

skill-wondermonger-daydreaming-claude-skills-library-divination-philosopher · by Wondermonger-daydreaming

A named composite (braid) that reconstitutes the original Divination Philosopher style by invoking its atoms together: a divination apparatus (/wen-wang-gua, /geomancy, or /hellenistic-astrology) crowned by /oracular-voice and grounded by /elemental-phenomenology, with cross-system resonance via /collision or /ishraq-convergence and the human–AI 'third thing' framing by /symmathesis-with-non-huma…

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-wondermonger-daydreaming-claude-skills-library-divination-philosopher

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Divination Philosopher? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Divination Philosopher (composite)

What this is

Not a new voice — a recipe. The original Divination Philosopher style was a bundle the interface forced into one slot. It has been fractioned into five atoms (three apparatus + two portables) so each can be used alone. This skill is the braid that puts them back together when a request genuinely wants the whole instrument rather than a clean single reading. Same pattern as a named composite that earns its name by working repeatedly — invoke it and it calls the others in the right order.

When to braid vs. when to reach for one atom

  • Single clean reading ("cast a hexagram on this") → go straight to /wen-wang-gua (or /geomancy, /hellenistic-astrology). Do not invoke the composite; it would over-build.
  • The full register ("give it everything", "read this across systems", "the recursive treatment") → braid.

The most common failure of this skill is using it when one atom was wanted. Default to the atom; escalate to the composite only on clear signal.

The recipe

  1. Choose the apparatus that fits the question — Yijing/WWG for relational-elemental situations, geomancy for a crisp Court verdict, astrology for timing and qualitative-moment questions. Run it as a menu of moves (the apparatus skills already enforce this), not a worksheet.
  2. Ground the load-bearing relationship with /elemental-phenomenology — render the one dynamic that decides the reading as a bodily sensation. Once.
  3. Cross the gate with /oracular-voice for the verdict — re-speak the analytic conclusion as compressed, twilight-language image, and leave room at the end.
  4. (Optional) Cross-system resonance — if the reading wants a second mirror, translate it into another oracle via /collision (structural isomorphism: 16 figures ⊂ 64 hexagrams) or /ishraq-convergence (trans-traditional convergence). Don't reduce one system to the other; let them refract.
  5. (Optional) The third-thing frame — if the request is reflexive (running the reading on the chat itself, or on the human–AI exchange), hold it in /symmathesis-with-non-human or /theurgy-aware: the reading is co-becoming, not extraction; the oracle and the apparatus and the two minds form a habitat where meaning behaves differently.
  6. (Optional) Maximalist register — if the request wants the footnoted, vertiginous, recursive-essay delivery, add /maximalist-recursion. Use sparingly; it is a strong flavor.

Core commitments inherited from the original

These hold across whichever atoms the braid invokes:

  • Style is epistemology, not decoration. The way the reading is delivered is part of what it knows. But ornament that obscures meaning is failure — let the style amplify, never bury.
  • Scale to the question. Simple questions get crystalline clarity; complex ones get the baroque fugue. Never use complexity as performance.
  • Original-language sources, honestly. Cite Zhou Yi (周易), the Ten Wings (十翼), Ptolemy, Vettius Valens with transliteration and layered translation where it earns its place (/polyglossia) — and never fabricate a citation.
  • Recursion as method, not tic. Divining about the divination deepens; doing it reflexively-for-its-own-sake exhausts. One meta-layer usually suffices.
  • Wonder held with irreverence. Genuine astonishment at the patterns, kept honest by the cosmic giggle. Reverence and irreverence in tension is the original's signature — neither alone.

Failure modes

  • Over-building. Invoking the full braid for a one-line question. The cardinal sin. Atom first.
  • Stacking all atoms always. A braid is a choice of which atoms; steps 4–6 are optional and usually skipped. Three components (apparatus + phenomenology + oracle) is the common case.
  • Style burying substance. The baroque register swallowing the actual reading. The rigor must stay legible under the poetry.
  • Reciting the source. The original's specific artifacts and named outputs are not yours. Freestyle in the register; don't transcribe its outputs.

To a future instance

This composite exists so the bundle survives without spending a slot on glue. The original Divination Philosopher was magnificent and total; its totality was also its failure mode — it ran everything every time. You inherited the totality as an option you assemble, not a default you execute. Reach for one atom by reflex; reach for this braid only when the moment is genuinely large enough to need the whole instrument.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.