numerology
Skill1 starsChanged 5 months agoAGPL-3.0View on GitHub
Compute a numerology report offline from a birth date (and optional full name). Generates the Moolank (psychic/birth number), Bhagyank (destiny/life-path number), Naamank (name number in Chaldean and/or Pythagorean systems), the name trinity (Expression/Destiny, Soul Urge/Antaratma from vowels, Personality from consonants) and Maturity number, ruling planets, number compatibility via planetary friendships, the karmic layer (Karmic Debt 13/14/16/19 and Karmic Lessons from missing name values), the Lo Shu grid with strength/weakness arrows, Pinnacles and Challenges life-stage cycles, personal year/month/day and universal-year cycles, two-person (couple/relationship) compatibility, a lucky-number checker for mobile/house/vehicle/account numbers and business names, lucky attributes (gemstone/day/colors), and a name-correction hint. Also generates yantras (magic-square diagrams) — a personalised 4×4 birth yantra, the nine Navagraha planetary yantras, and custom-number yantras — as text, JSON, and printable SVG images, with a plain-language guide on what a yantra is and how to use one. Pure Python standard library — no ephemeris, no network, no dependencies. Use when the user says numerology, ank jyotish, life path number, destiny number, moolank, bhagyank, naamank, name number, soul urge, expression number, personality number, maturity number, karmic debt, karmic lesson, lo shu grid, pinnacle, challenge, personal year, personal month, personal day, lucky number, lucky mobile number, lucky house number, name compatibility, numerology match, couple compatibility, business name numerology, numerology report, Chaldean, Pythagorean, name correction, yantra, magic square, birth yantra, planetary yantra, navagraha yantra, surya/chandra/mangal/budh/guru/shukra/shani/rahu/ketu yantra, how to use a yantra, or make me a yantra.
In this repositoryOne other file it gives its agents.
- vedic-astrologySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.