Update to All your Horoscopes

{
  "name": "compatibility-walkthrough",
  "description": "Guide a friendship or love compatibility lookup between two zodiac signs or birthdays. Use when the user asks to compare compatibility, match two signs, or find the widget's compatibility percentage. Open the correct star-sign view and guide the client-only interaction; never invent or claim model access to the displayed score.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 208
    },
    {
      "relative_path": "references/zodiac-date-ranges.md",
      "size_in_bytes": 732
    }
  ],
  "skill_md_contents": "---\nname: compatibility-walkthrough\ndescription: Guide a friendship or love compatibility lookup between two zodiac signs or birthdays. Use when the user asks to compare compatibility, match two signs, or find the widget's compatibility percentage. Open the correct star-sign view and guide the client-only interaction; never invent or claim model access to the displayed score.\n---\n\n# Compatibility Walkthrough\n\nOpen the primary sign's profile and guide the user to the requested client-side compatibility entry.\n\n## Inputs\n\nResolve:\n\n- the primary person's star sign or birthday\n- the other person's star sign or birthday\n- `friendship` or `love`\n\nWhen a birthday is supplied instead of a sign, read [the zodiac date ranges](references/zodiac-date-ranges.md). Ask for clarification when a numeric date is ambiguous or a date is invalid.\n\n## Workflow\n\n1. Resolve both signs and the compatibility type. Minimize personal data: after deriving a sign from a birthday, use the sign rather than forwarding the birthday to the tool.\n2. If both signs are the same, explain that the widget omits the active sign from its compatibility list, so it cannot display a same-sign percentage. Offer to show the shared sign profile instead.\n3. For two different signs, call `horoscope` with:\n   - `starSign`: the primary sign\n   - `route`: `star-sign`\n   - `reason`: a concise explanation naming the requested compatibility type and counterpart sign\n4. Tell the user to select `Friendship` or `Love` in the widget, then locate the other sign in the displayed list.\n5. If the user wants an interpretation, ask them to provide the displayed percentage. Never infer the score from the tool response or claim to read the widget interaction.\n6. When the user provides the score, restate it accurately and offer a brief, non-deterministic takeaway plus one constructive conversation prompt.\n\n## Output\n\nReturn the two resolved signs, compatibility type, exact widget steps, and either:\n\n- `Score awaiting user lookup`, or\n- the user-reported score with a clearly entertainment-oriented interpretation\n\n## Boundaries\n\n- The `horoscope` tool exposes a star-sign view but no model-visible compatibility data.\n- Do not fabricate a percentage, scrape the widget, or imply that compatibility predicts relationship success.\n- Do not provide high-stakes relationship, mental-health, legal, or safety advice from an astrology score.\n"
}