← EasyRegistryCONTENT HISTORY

Update to EasyRegistry

Snapshot Sep 30, 2026 · 23:10 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "find-a-registry-and-choose-a-gift",
  "description": "Use when someone is a guest looking for a friend's or family member's EasyRegistry gift registry — a wedding, baby shower, birthday or fundraiser — and wants to see what is on it and what is still available. Works without signing in. Not for adding or buying gifts; purchases and contributions happen on the public registry page.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 572
    }
  ],
  "skill_md_contents": "---\nname: find-a-registry-and-choose-a-gift\ndescription: Use when someone is a guest looking for a friend's or family member's EasyRegistry gift registry — a wedding, baby shower, birthday or fundraiser — and wants to see what is on it and what is still available. Works without signing in. Not for adding or buying gifts; purchases and contributions happen on the public registry page.\n---\n\n# Find a registry and choose a gift\n\nUse this when the user is a guest: \"find Sam and Riley's wedding registry\", \"what's left on Priya's baby shower list\", \"what can I get them\". No sign-in is needed.\n\n## Workflow\n\n1. **Get the two things search needs.** `find_registry` requires the event date (or a close approximation) and at least three characters of the couple's or host's name, or the registry title or slug. Search matches registries within one month either side of the date and will not accept a date more than a month in the past. If the user only has the year or the season, ask for the month.\n2. **Search.** Call `find_registry`. It returns up to ten matches. If there is one clear match, continue. If there are several, show title, names and event date and ask which one. If there are none, suggest checking the spelling, the date, or asking the host for the registry link (the slug at the end of the link can be used as the search text).\n3. **Show the registry.** Call `view_registry` for the public details: title, event date, location, description and any message from the hosts. Respect the host's settings; if a detail is not returned, do not guess it.\n4. **Browse gifts.** Call `view_gifts` and present what is available, grouped sensibly (by price range or category if obvious). Note that some items may already be partly funded or bought; only present what the tool returns as available.\n5. **Help them choose.** If the user gives a budget or a preference, filter the list and recommend two or three options with prices.\n6. **Hand off to buy.** Give the public registry page link so they can buy or contribute there. The app cannot purchase, reserve or contribute on their behalf.\n\n## Boundaries\n\n- Only use these three public tools; never attempt owner tools for a guest.\n- Do not reveal or speculate about the owner's private data (contributions, contributor names, totals, bank details). These tools do not return them.\n- Do not fabricate registries, gifts or prices when a search is empty.\n- If the registry is password-protected or closed, say so and suggest the guest contact the host.\n\n## Output\n\nThe matched registry (title, date, location), a short list of available gifts with prices, and the public page link for purchasing.\n"
}

SHA-256: 2c4cb5e63c372dd85f948cba3b8a005c7660a3b1af82ff313c980f1a867e7201