Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Astrology API: generate natal charts, synastry, composite, transits, solar/lunar returns, progressions, directions, planetary positions, house cusps, aspects...
Astrology API: generate natal charts, synastry, composite, transits, solar/lunar returns, progressions, directions, planetary positions, house cusps, aspects...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill when the user asks about: Birth charts, natal charts, horoscopes Zodiac compatibility, synastry, relationship analysis Planetary positions, transits, aspects Moon phases, lunar metrics, void of course Solar/lunar returns, progressions, directions Tarot card readings, spreads, interpretations Numerology (core numbers, compatibility, comprehensive) Vedic astrology (kundli, doshas, dashas, panchang) Chinese astrology (bazi, ming gua, feng shui) Human design (bodygraph, type, channels, gates) Kabbalah (tree of life, birth angels, gematria) Astrocartography (relocation, power zones, lines) Fixed stars (positions, conjunctions) Eclipses (upcoming, natal impact) Palmistry (palm analysis, reading) Daily/weekly/monthly/yearly horoscopes Career, health, spiritual, psychological analysis Chart rendering (SVG, PNG images)
Before making any API call, verify: $ASTROLOGY_API_KEY environment variable is set curl is available on PATH If the API key is missing, ask the user to set it: export ASTROLOGY_API_KEY="your_token_here"
Gather data from the user depending on the request type: For natal/personal: name, birth date (year, month, day), birth time (hour, minute), birth city + country code (2-letter ISO) For synastry/compatibility: birth data for TWO people For transits: natal data + transit date/time For horoscopes by sign: just the zodiac sign name For tarot: question or spread type For numerology: full name + birth date Call the API using {baseDir}/scripts/astro-api.sh: bash {baseDir}/scripts/astro-api.sh POST /api/v3/charts/natal '{ ... }' Present results in a human-friendly format, highlighting key findings.
bash {baseDir}/scripts/astro-api.sh POST /api/v3/charts/natal '{ "subject": { "name": "John", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "options": { "house_system": "P", "zodiac_type": "Tropic", "language": "EN" } }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/charts/synastry '{ "subject": { "name": "Person A", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "partner": { "name": "Person B", "year": 1992, "month": 7, "day": 20, "hour": 9, "minute": 0, "second": 0, "city": "London", "country_code": "GB" }, "options": {"house_system": "P", "zodiac_type": "Tropic", "language": "EN"} }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/charts/transit '{ "subject": { "name": "John", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "transit": { "year": 2026, "month": 2, "day": 12, "hour": 12, "minute": 0, "second": 0, "city": "New York", "country_code": "US" }, "options": {"house_system": "P", "zodiac_type": "Tropic", "language": "EN"} }'
bash {baseDir}/scripts/astro-api.sh GET /api/v3/data/now
bash {baseDir}/scripts/astro-api.sh POST /api/v3/data/positions '{ "subject": { "name": "John", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "options": {"house_system": "P", "zodiac_type": "Tropic"} }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/data/lunar-metrics '{ "subject": { "name": "now", "year": 2026, "month": 2, "day": 12, "hour": 12, "minute": 0, "second": 0, "city": "New York", "country_code": "US" } }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/horoscope/sign/daily '{ "sign": "aries", "language": "EN" }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/horoscope/personal/daily '{ "subject": { "name": "John", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "language": "EN" }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/analysis/natal-report '{ "subject": { "name": "John", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "options": {"house_system": "P", "zodiac_type": "Tropic", "language": "EN"} }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/svg/natal '{ "subject": { "name": "John", "year": 1990, "month": 3, "day": 15, "hour": 14, "minute": 30, "second": 0, "city": "New York", "country_code": "US" }, "options": {"house_system": "P", "zodiac_type": "Tropic"} }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/tarot/cards/draw '{ "count": 3 }'
bash {baseDir}/scripts/astro-api.sh POST /api/v3/numerology/core-numbers '{ "full_name": "John Smith", "birth_date": "1990-03-15" }' Full endpoint reference: Read {baseDir}/references/api-endpoints.md for all 190+ endpoints with detailed parameters.
When the user doesn't specify preferences, use these defaults: House system: P (Placidus) โ most common in Western astrology Zodiac type: Tropic (Tropical) โ Western standard Language: EN (English) โ override based on user's language Tradition: universal โ broadest coverage
When presenting results to the user: Start with the highlights: Sun sign, Moon sign, Ascendant (Rising) Use plain language โ translate astrological jargon Format positions as tables when showing multiple planets Highlight notable aspects (conjunctions, oppositions, squares, trines) For compatibility: lead with the overall score/summary For horoscopes: present the text naturally, don't dump raw JSON For chart images (SVG/render): save to a file and inform the user
Birth time unknown: Use noon (12:00) and note that house positions and Moon degree may be less accurate City not found: Ask for latitude/longitude instead. Use latitude and longitude fields instead of city/country_code API errors (400/422): Parse the error message and explain to the user what's wrong (e.g., invalid date, missing field) Large responses: For analysis reports, summarize the key points rather than showing everything Language support: The API supports EN, RU, FR, DE, ES, IT, PT, and more โ match the user's language when possible
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.