Tarot reading research
Skill ProfesseurHaipeng/tarot-reading-research-skill/skills/tarot-reading-research
Research Tarot history, deck iconography, spreads, and reflective readings with reproducible draws, source provenance, competing traditions, and explicit uncertainty. Use when Codex is asked to explain Tarot cards, deck systems, spreads, reversals, readings, or Tarot history.From its SKILL.md
npx -y skills add ProfesseurHaipeng/tarot-reading-research-skill --skill tarot-reading-researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.7 KB, 683 tokens by cl100k_base, as published. Nobody here has run it
Tarot Reading Research
Treat Tarot as a historical-cultural interpretive system. Card meanings and readings are symbolic traditions, not established causal predictors. Never make medical, legal, financial, safety, fertility, employment, or relationship decisions for a user.
Runtime: Python 3.10+
The bundled helper requires Python 3.10+ and only the Python standard library. It is deterministic and does not make network requests.
Workflow
- Identify the deck tradition and edition; record creator, date, language, medium, and licence.
- Read historical-corpus.md before making an origin claim. Do not project a modern occult system backward onto fifteenth-century playing cards.
- Separate card imagery, historical claims, divinatory convention, and reflective interpretation. Read deck-systems.md before transferring a meaning between deck families.
- Record the question, spread positions, draw order, orientation rule, and whether the draw was user-supplied or simulated. Never fabricate a random draw. Store the resulting record using tarot-record.schema.json.
- Apply reading-logic.md: card observation first, spread function second, tradition third, user reflection last.
- Compare at least two interpretive traditions when meanings differ. Make the reading reflective and conditional, with concrete next questions.
- Finish with a reality check: what can be observed, what is metaphor, what professional or consent boundary applies, and what evidence would challenge the interpretation.
Tools and references
Use Python 3.10+ standard library only. Run python3 scripts/transparent_spread.py --seed <visible-seed> --spread three-card-reflection for a reproducible draw. The output includes the algorithm version, deck-catalog SHA-256, source ids, positions, and reversal policy. For a physical draw, use --mode physical --cards 'The Fool|Ace of Cups|Justice'; this records the user's cards and does not simulate them. Read learning-path.md, knowledge-model.md, source-registry.md, and evaluation.md before discussing accuracy.
Calculation and interpretation rules
For Tarot, distinguish card imagery, deck-specific iconography, divinatory convention, and reader projection. Use open questions rather than deterministic claims.
Quality questions
- Is every card identifier tied to a named edition, catalogue digest, and source registry entry?
- Are historical facts separated from modern esoteric practice?
- Is a visible image being described rather than a stock meaning being projected onto it?
- Does the reading preserve ambiguity instead of manufacturing certainty?
- Could a user mistake the output for professional advice or a scientific result?
If asked about “success rate,” explain that symbolic usefulness and predictive accuracy are different hypotheses. Propose a preregistered, blinded, outcome-based test for empirical evaluation; do not invent a percentage.
Read sources.md when source selection or deck history matters. Do not invoke astronomy, birth data, zodiac, or planetary positions in this Skill: those belong to the separate Western astrology Skill.
What ships with it: 16 files
50.0 KB alongside SKILL.md, 2 of them executable
agents/
- openai.yaml301 B
data/
- deck-contract.json989 B
- decks/rws-v1.json18.0 KB
- interpretive-lenses.json1.1 KB
- spreads.json1.7 KB
references/
- deck-systems.md1.5 KB
- evaluation.md594 B
- historical-corpus.md1.4 KB
- knowledge-model.md835 B
- learning-path.md1.5 KB
- reading-logic.md861 B
- source-registry.md2.5 KB
- sources.md749 B
schemas/
- tarot-record.schema.json1.7 KB
scripts/
- transparent_spread.pyruns12.9 KB
tests/
- test_spread.pyruns3.4 KB