colin-roy-ehri/gratitude/community-match

Community Match

Triggers the backend's deterministic match routine. Cheap (no LLM call). Returns the raw match list and counts. When the backend finds a new match it ALSO pushes a notification into the inbox of both parties — read that with community-inbox.

When to use

• Right after a user posts a NEED or OFFER (this skill is chained automatically from those).
• When the user asks "any new matches?" — but prefer community-inbox because that one decrypts contact info too.
• When the chat is first opened (background refresh).

Instructions

Call the run_js tool with:

• skill_name: community-match
• script_name: index.html
• data: {} (no parameters)

Output

{
  "myKeyCount": 3,
  "myMessageCount": 3,
  "globalMessageCount": 42,
  "matches": [ { "leftMessageId": "...", "rightMessageId": "...", "score": 0.8, "reason": "..." } ]
}

You MUST always call the `run_js` tool — do not skip it. Then act on the result:

• If `matches` is non-empty: do not reply to the user yet. Immediately call the community-inbox skill in the same turn (no narration in between) so the new match is surfaced with matchToken, category, and decrypted contact info. Reply to the user based on the community-inbox output, not the community-match output.
• If matches is empty: reply "No new matches right now."

Never reply without first running the tool. Never reply with a single character or empty message.