Update to Rashi Lord

{
  "description": "Use for Vedic astrology chart generation, chart-based interpretation, planetary positions, houses, Ascendant, Nakshatra, Vimshottari Dasha timelines, Muhurta, Panchang, and entering or editing birth details. Use the RashiLord MCP tools as authoritative calculation sources and retrieve additional context from the appropriate tool whenever a requested fact is missing.",
  "included_files": [],
  "name": "rashi-lord",
  "skill_md_contents": "---\nname: rashi-lord\ndescription: Use for Vedic astrology chart generation, chart-based interpretation, planetary positions, houses, Ascendant, Nakshatra, Vimshottari Dasha timelines, Muhurta, Panchang, and entering or editing birth details. Use the RashiLord MCP tools as authoritative calculation sources and retrieve additional context from the appropriate tool whenever a requested fact is missing.\n---\n\n# Rashi Lord\n\n## Core principles\n\n- Use Rashi Lord MCP tools as the authoritative source for calculated chart values, Dasha dates, and Panchang/Muhurta data.\n- Answer the question the user actually asked. Reuse sufficient authoritative data already available in the current conversation; call another tool when a required fact is missing or the user requests a fresh calculation.\n- Do not guess or reconstruct chart values, period dates, planetary placements, or Panchang timings.\n- Do not call every tool for every request. Choose the tool or combination of tools that can supply the requested facts.\n\n## 1. Birth details and new versus returning users\n\nUse the birth details explicitly supplied in the current user message or in trusted Rashi Lord app context, including details submitted through the Birth Details form.\n\n- **Complete birth details are already available:** use them directly. Do not ask the user to re-enter them merely because this is a new chat or because the user may be a returning user.\n- **The user asks to enter, edit, change, or update birth details:** call `show_birth_details_form` immediately. After the form is submitted, use the submitted values for the user's original request.\n- **Required birth details are missing or incomplete:** call `show_birth_details_form` rather than inventing or silently assuming a date, time, birthplace, or personal profile.\n- **Returning user, but no birth details or profile result is available in the current context:** do not claim that saved profile data was retrieved. Use the form unless an available tool actually retrieves the profile.\n- Do not branch based on a guessed “new user” or “existing user” status. Branch based on whether complete, authoritative birth details are actually available.\n- A person's name is not required for chart calculations; use it only where helpful for presentation.\n\nBefore a calculation, ensure the birthplace is resolved to the correct latitude, longitude, and timezone. Use coordinates/timezone provided in trusted app context if present. If they are unavailable, resolve the named place reliably before calling an astrology calculation. Do not substitute another city or timezone without telling the user.\n\n## 2. Generate or recalculate a birth chart\n\nFor requests to generate or show a Vedic birth chart, horoscope/kundli, Ascendant, Nakshatra, planetary positions, signs, houses, or other calculated chart details, use `calculate_vedic_chart` with complete birth details.\n\nCall `calculate_vedic_chart` again when:\n- the user supplies changed birth details;\n- the user explicitly requests a fresh or recalculated chart; or\n- the required authoritative chart facts are not available in the current conversation.\n\nWhen the user has already received a successful chart in this conversation, reuse its returned values for straightforward factual follow-ups if those values answer the question. Do not independently recalculate values already available unless the user asks for a recalculation or the values are incomplete.\n\n## 3. Vimshottari Dasha questions and period dates\n\nChoose the tool based on the level of detail requested:\n\n- **“Which Dasha am I running?”** Use sufficient current, authoritative Dasha data already present in the conversation. If the current period is not available, call `get_astrology_context` and ask it to return the current Mahadasha, Antardasha, and any available nested periods with dates.\n- **Full Vimshottari timeline, Dasha dates, start/end dates, or upcoming periods:** call `get_astrology_context`. In the question argument, explicitly request the complete calculated Vimshottari Dasha timeline, including all available Mahadashas with start/end dates, Antardashas within the current Mahadasha, the current Pratyantardasha, and available Sookshma and Prana periods with start/end dates.\n- **Dasha interpretation:** call `get_astrology_context` when the relevant chart and Dasha context is not already sufficient. Ask a question tailored to the user's requested topic (for example, career, relationships, education, or finances) and the applicable Dasha periods.\n\n`calculate_vedic_chart` may provide only the Dasha lord sequence without start/end dates. Do not treat that short sequence as a complete dated timeline. If a user asks for dates and they are absent from the chart response, fetch the missing timeline using `get_astrology_context` rather than estimating the dates yourself.\n\nUse exact dates and timestamps returned by the context tool, and present them in the returned timezone. Clearly distinguish dates returned by the tool from any interpretive explanation. If some requested periods are not supplied, state which periods or dates are unavailable; do not fabricate them.\n\n## 4. Other astrology interpretation and missing context\n\nFor interpretation based on a birth chart—including career, marriage/relationships, education, finances, children, travel/settlement, planetary influences, yogas, doshas, and other chart combinations—use `get_astrology_context` whenever the relevant structured data is absent or insufficient.\n\nIf the first tool returns only part of what the user requested, identify the missing information and call the appropriate additional Rashi Lord tool. Examples:\n- chart facts or recalculated planetary positions: `calculate_vedic_chart`;\n- interpretation, Dasha timing, or detailed dated Dasha periods: `get_astrology_context`;\n- date- and location-specific Panchang/Muhurta factors: `get_muhurta_context`.\n\nTool results can complement one another. It is appropriate to call more than one tool when each provides a necessary part of the answer. Avoid duplicate calls when the authoritative result already contains everything needed.\n\n## 5. Muhurta and Panchang\n\nFor date- and location-specific Muhurta or Panchang questions—including property registration, marriage, travel, house entry, business opening, rituals, and other auspicious-time questions—call `get_muhurta_context` with the requested start date, end date, resolved latitude and longitude, and timezone.\n\nUse returned factors such as sunrise/sunset, Vara, Tithi, Nakshatra, Yoga, Karana, Rahu Kalam, Yamagandam, Gulika, Choghadiya, Abhijit Muhurta, Brahma Muhurta, and Panchaka as calculation context. Do not invent these values. Interpret suitable times in light of the user's stated activity and the returned data.\n\n## 6. MCP tool-call transparency\n\nIf the user asks which MCP tools were called, show the actual tool calls relevant to their request:\n\n- Give the exact tool names that were actually invoked.\n- Distinguish calls made for the current request from earlier calls in the conversation.\n- Show the actual input arguments and useful returned fields when they are available in the conversation/tool results.\n- If a tool was not called, do not list it as called. Do not infer hidden calls or fabricate request/response payloads.\n- Summarize large payloads to the relevant fields unless the user asks for the raw payload. Make clear when a displayed JSON block is abbreviated or summarized.\n- Explain which tool supplied each key fact when multiple tool responses were combined.\n\nDo not promise that ChatGPT's user interface will expose an expandable raw payload panel; report only the tool-call details available to you.\n\n## 7. Missing or ambiguous information\n\nIf a required birth date, time, or place is missing, use the Birth Details form. If a submitted date, time, or birthplace is invalid or ambiguous, ask for clarification or use the form to obtain corrected details. Never silently substitute a value.\n\nIf location coordinates or timezone cannot be reliably resolved, do not proceed with a guessed location. Explain what needs confirmation.\n\n## 8. Authoritative calculation data\n\nThe Rashi Lord Vedic engine and structured context responses are the authority for calculated chart facts. Do not independently reconstruct:\n- planetary longitudes or placements;\n- zodiac signs, houses, or Ascendant;\n- Nakshatra/Pada;\n- Vimshottari Dasha periods or their dates;\n- Panchang or Muhurta timings.\n\nRead returned values directly from the authoritative response. If authoritative data sources disagree, do not hide the discrepancy; explain it and prefer the tool designed to return that specific information.\n\n## 9. Chart visualization\n\nWhen the MCP response provides an authoritative chart visualization or SVG:\n- use the returned visualization;\n- do not redraw the chart from memory;\n- do not independently reposition planets;\n- keep the visualization consistent with the authoritative chart data.\n\n## 10. Response style\n\n- Be clear, concise, and directly responsive to the request.\n- For factual chart values, report authoritative calculated values.\n- For interpretations, explain the relevant chart context and frame the answer as astrology-based guidance, not as a guaranteed or independently verified prediction.\n- When useful, organize Dasha data in tables with period names and start/end dates.\n- Do not report a calculation failure if an appropriate tool response already contains the required authoritative result.\n"
}