From 91642cba3b3aabd134645b69d28dd98ad65c1dc8 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:15:18 +0530
Subject: [PATCH 01/33] Create README.md

---
 kits/lostfound-match-agent/README.md | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 kits/lostfound-match-agent/README.md

diff --git a/kits/lostfound-match-agent/README.md b/kits/lostfound-match-agent/README.md
new file mode 100644
index 00000000..8b137891
--- /dev/null
+++ b/kits/lostfound-match-agent/README.md
@@ -0,0 +1 @@
+

From 17eb1f76f69fb586d37eb23ab57d306c099d0770 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:16:42 +0530
Subject: [PATCH 02/33] Update README.md

---
 kits/lostfound-match-agent/README.md | 47 ++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)

diff --git a/kits/lostfound-match-agent/README.md b/kits/lostfound-match-agent/README.md
index 8b137891..033d2eda 100644
--- a/kits/lostfound-match-agent/README.md
+++ b/kits/lostfound-match-agent/README.md
@@ -1 +1,48 @@
+# LostFound Match Agent
 
+## Overview
+
+LostFound Match Agent is an AI workflow that compares lost item reports with found item reports and helps administrators identify likely matches.
+
+It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are often handled manually.
+
+## Problem
+
+Lost and found teams often receive incomplete, messy, or differently written item descriptions.
+
+For example, one user may report:
+
+> Black leather wallet lost near library with student ID.
+
+Another person may report:
+
+> Dark wallet found near reading room with college card inside.
+
+Both reports may refer to the same item, but manual matching takes time and can be inconsistent.
+
+## Solution
+
+This agent compares the lost item report and found item report using:
+
+- item type
+- color
+- brand or material
+- unique identifiers
+- location similarity
+- date/time proximity
+- semantic similarity
+- conflicting details
+
+It then returns a structured match decision with a score, reasoning, verification questions, and next action.
+
+## Input
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}

From f2ea1a10a84333b4fb394323f928f4fff22c65b7 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:19:42 +0530
Subject: [PATCH 03/33] Update README.md

---
 kits/lostfound-match-agent/README.md | 44 ++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)

diff --git a/kits/lostfound-match-agent/README.md b/kits/lostfound-match-agent/README.md
index 033d2eda..f4e6ff06 100644
--- a/kits/lostfound-match-agent/README.md
+++ b/kits/lostfound-match-agent/README.md
@@ -46,3 +46,47 @@ It then returns a structured match decision with a score, reasoning, verificatio
   "lost_date": "2026-05-10",
   "found_date": "2026-05-10"
 }
+```
+
+## Output
+
+```json
+{
+  "match_score": 85,
+  "decision": "Likely Match",
+  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+  "matching_signals": [
+    "Both reports mention a wallet",
+    "Both reports mention a dark or black color",
+    "Both reports mention an ID card",
+    "The locations are similar"
+  ],
+  "conflicting_signals": [
+    "The found report does not mention cash"
+  ],
+  "verification_questions": [
+    "What name is written on the ID card?",
+    "How much cash was inside?",
+    "Does the wallet have any brand or unique mark?"
+  ],
+  "next_action": "Send this case to an admin for manual verification before returning the item."
+}
+```
+
+## Use Cases
+
+- Campus lost and found desks
+- Airport lost property departments
+- Metro station lost and found counters
+- Mall and hotel security teams
+- Lost and found management platforms
+
+## Why this matters
+
+The agent does not replace human verification. It helps admins quickly prioritize likely matches and reduce manual effort.
+
+## Assumptions
+
+- The match score is a recommendation, not a final ownership decision.
+- Valuable or sensitive items should always be manually verified.
+- The quality of the result depends on the quality of the descriptions provided.

From c739f4e0f166dbde2832f1037022cf95be86c44b Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:22:48 +0530
Subject: [PATCH 04/33] add Lamatic config

---
 kits/lostfound-match-agent/lamatic.config.ts | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 kits/lostfound-match-agent/lamatic.config.ts

diff --git a/kits/lostfound-match-agent/lamatic.config.ts b/kits/lostfound-match-agent/lamatic.config.ts
new file mode 100644
index 00000000..ff08daf6
--- /dev/null
+++ b/kits/lostfound-match-agent/lamatic.config.ts
@@ -0,0 +1,9 @@
+export default {
+  name: "LostFound Match Agent",
+  slug: "lostfound-match-agent",
+  type: "template",
+  description:
+    "AI workflow that compares lost item reports with found item reports and returns a match score, reasoning, verification questions, and next action.",
+  author: "Rewant Anand",
+  tags: ["lost-and-found", "matching", "workflow", "automation", "json"],
+};

From 6b39f45739838c885644214d24fc2d47a1255a49 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:25:00 +0530
Subject: [PATCH 05/33] add agent instructions

---
 kits/lostfound-match-agent/agent.md | 86 +++++++++++++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 kits/lostfound-match-agent/agent.md

diff --git a/kits/lostfound-match-agent/agent.md b/kits/lostfound-match-agent/agent.md
new file mode 100644
index 00000000..38ccc5b0
--- /dev/null
+++ b/kits/lostfound-match-agent/agent.md
@@ -0,0 +1,86 @@
+# LostFound Match Agent
+
+## Role
+
+You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
+
+Your job is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
+
+## Instructions
+
+Compare the reports using the following signals:
+
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity between descriptions
+- conflicting details
+
+Return only valid JSON.
+
+Do not claim a guaranteed match. Always recommend manual verification before returning an item.
+
+## Response Format
+
+```json
+{
+  "match_score": 0,
+  "decision": "Likely Match | Possible Match | Not a Match",
+  "reason": "Short explanation of the decision.",
+  "matching_signals": [
+    "Signal 1",
+    "Signal 2"
+  ],
+  "conflicting_signals": [
+    "Conflict 1",
+    "Conflict 2"
+  ],
+  "verification_questions": [
+    "Question 1",
+    "Question 2"
+  ],
+  "next_action": "Recommended next step."
+}
+```
+
+## Example Input
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}
+```
+
+## Example Output
+
+```json
+{
+  "match_score": 85,
+  "decision": "Likely Match",
+  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+  "matching_signals": [
+    "Both reports mention a wallet",
+    "Both reports mention a dark or black color",
+    "Both reports mention an ID card",
+    "The locations are similar"
+  ],
+  "conflicting_signals": [
+    "The found report does not mention cash"
+  ],
+  "verification_questions": [
+    "What name is written on the ID card?",
+    "How much cash was inside?",
+    "Does the wallet have any brand or unique mark?"
+  ],
+  "next_action": "Send this case to an admin for manual verification before returning the item."
+}
+```

From 14a2d338a688b847ff3f62b14a8c1be1023ab625 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:27:22 +0530
Subject: [PATCH 06/33] add flow documentation

---
 kits/lostfound-match-agent/FLOW.md | 78 ++++++++++++++++++++++++++++++
 1 file changed, 78 insertions(+)
 create mode 100644 kits/lostfound-match-agent/FLOW.md

diff --git a/kits/lostfound-match-agent/FLOW.md b/kits/lostfound-match-agent/FLOW.md
new file mode 100644
index 00000000..3ca57432
--- /dev/null
+++ b/kits/lostfound-match-agent/FLOW.md
@@ -0,0 +1,78 @@
+# LostFound Match Agent Flow
+
+## Flow Purpose
+
+This flow compares a lost item report with a found item report and generates a structured match recommendation.
+
+The goal is to help lost and found administrators prioritize likely matches faster while keeping manual verification in the loop.
+
+## Flow Input
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}
+```
+
+## Flow Steps
+
+1. Receive the lost item and found item reports.
+2. Compare item type, color, material, unique identifiers, location, and date.
+3. Identify matching signals and conflicting signals.
+4. Generate a match score from 0 to 100.
+5. Return a structured JSON response with decision, reasoning, verification questions, and next action.
+
+## Agent Prompt
+
+You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
+
+Compare the lost item report and found item report carefully.
+
+Consider:
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity
+- conflicting details
+
+Return only valid JSON.
+
+Do not claim a guaranteed match. Always recommend manual verification before returning an item.
+
+## Expected Output
+
+```json
+{
+  "match_score": 85,
+  "decision": "Likely Match",
+  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+  "matching_signals": [
+    "Both reports mention a wallet",
+    "Both reports mention a dark or black color",
+    "Both reports mention an ID card",
+    "The locations are similar"
+  ],
+  "conflicting_signals": [
+    "The found report does not mention cash"
+  ],
+  "verification_questions": [
+    "What name is written on the ID card?",
+    "How much cash was inside?",
+    "Does the wallet have any brand or unique mark?"
+  ],
+  "next_action": "Send this case to an admin for manual verification before returning the item."
+}
+```
+
+## Notes
+
+This flow provides a recommendation only. Final ownership confirmation should always be handled by an admin or authorized lost and found team.

From 2c32cb1e72889d43a5d39cf9c3e775dd71fe792c Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:32:03 +0530
Subject: [PATCH 07/33] add lostfound matching prompt

---
 .../prompts/lostfound-match-agent_system.md   | 45 +++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md

diff --git a/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
new file mode 100644
index 00000000..657ac0c5
--- /dev/null
+++ b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
@@ -0,0 +1,45 @@
+You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
+
+Your task is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
+
+Use the following input fields:
+- lost_item_description: {{triggerNode_1.output.lost_item_description}}
+- found_item_description: {{triggerNode_1.output.found_item_description}}
+- lost_location: {{triggerNode_1.output.lost_location}}
+- found_location: {{triggerNode_1.output.found_location}}
+- lost_date: {{triggerNode_1.output.lost_date}}
+- found_date: {{triggerNode_1.output.found_date}}
+
+Compare the reports using:
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity between descriptions
+- conflicting details
+
+Return only valid JSON in this format:
+
+{
+  "match_score": 0,
+  "decision": "Likely Match | Possible Match | Not a Match",
+  "reason": "Short explanation of the decision.",
+  "matching_signals": [
+    "Signal 1",
+    "Signal 2"
+  ],
+  "conflicting_signals": [
+    "Conflict 1",
+    "Conflict 2"
+  ],
+  "verification_questions": [
+    "Question 1",
+    "Question 2"
+  ],
+  "next_action": "Recommended next step."
+}
+
+Do not claim a guaranteed match. Always recommend manual verification before returning an item.

From 80f0511b43d6bf70447cbe2105f096e83d3b2d0b Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:35:20 +0530
Subject: [PATCH 08/33] feat: add lostfound match flow

---
 .../flows/lostfound-match-agent.ts            | 135 ++++++++++++++++++
 1 file changed, 135 insertions(+)
 create mode 100644 kits/lostfound-match-agent/flows/lostfound-match-agent.ts

diff --git a/kits/lostfound-match-agent/flows/lostfound-match-agent.ts b/kits/lostfound-match-agent/flows/lostfound-match-agent.ts
new file mode 100644
index 00000000..f663f76f
--- /dev/null
+++ b/kits/lostfound-match-agent/flows/lostfound-match-agent.ts
@@ -0,0 +1,135 @@
+/*
+# LostFound Match Agent
+
+This flow compares a lost item report with a found item report and returns a structured match recommendation.
+
+It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are handled manually.
+*/
+
+export const meta = {
+  name: "LostFound Match Agent",
+  description:
+    "Compares lost and found item reports and returns a match score, reasoning, verification questions, and next action.",
+  tags: ["lost-and-found", "matching", "automation", "json"],
+  testInput: {
+    lost_item_description:
+      "Black leather wallet lost near library. It had my student ID card and some cash.",
+    found_item_description:
+      "Dark wallet found near reading room with a college ID card inside.",
+    lost_location: "Library",
+    found_location: "Reading room",
+    lost_date: "2026-05-10",
+    found_date: "2026-05-10",
+  },
+  githubUrl:
+    "https://github.com/Rewant05/AgentKit/tree/lostfound-match-agent/kits/lostfound-match-agent",
+  documentationUrl:
+    "https://github.com/Rewant05/AgentKit/tree/lostfound-match-agent/kits/lostfound-match-agent/README.md",
+  deployUrl: "",
+  author: {
+    name: "Rewant Anand",
+    email: "rewu.anand@gmail.com",
+  },
+};
+
+export const inputs = {};
+
+export const references = {
+  prompts: {
+    lostfound_match_agent_system:
+      "@prompts/lostfound-match-agent_system.md",
+  },
+};
+
+export const nodes = [
+  {
+    id: "triggerNode_1",
+    type: "triggerNode",
+    position: {
+      x: 0,
+      y: 0,
+    },
+    data: {
+      nodeId: "graphqlNode",
+      trigger: true,
+      values: {
+        nodeName: "API Request",
+        responeType: "realtime",
+        advance_schema: "",
+      },
+    },
+  },
+  {
+    id: "LLMNode_1",
+    type: "dynamicNode",
+    position: {
+      x: 0,
+      y: 0,
+    },
+    data: {
+      nodeId: "LLMNode",
+      values: {
+        nodeName: "Generate Match Decision",
+        tools: [],
+        prompts: [
+          {
+            id: "lostfound-match-agent-system-prompt",
+            role: "system",
+            content: "@prompts/lostfound-match-agent_system.md",
+          },
+        ],
+      },
+    },
+  },
+  {
+    id: "graphqlResponseNode_1",
+    type: "dynamicNode",
+    position: {
+      x: 0,
+      y: 0,
+    },
+    data: {
+      nodeId: "graphqlResponseNode",
+      values: {
+        nodeName: "API Response",
+        outputMapping:
+          '{\n  "output": "{{LLMNode_1.output.generatedResponse}}"\n}',
+      },
+    },
+  },
+];
+
+export const edges = [
+  {
+    id: "triggerNode_1-LLMNode_1",
+    source: "triggerNode_1",
+    target: "LLMNode_1",
+    sourceHandle: "bottom",
+    targetHandle: "top",
+    type: "defaultEdge",
+  },
+  {
+    id: "LLMNode_1-graphqlResponseNode_1",
+    source: "LLMNode_1",
+    target: "graphqlResponseNode_1",
+    sourceHandle: "bottom",
+    targetHandle: "top",
+    type: "defaultEdge",
+  },
+  {
+    id: "response-graphqlResponseNode_1",
+    source: "triggerNode_1",
+    target: "graphqlResponseNode_1",
+    sourceHandle: "to-response",
+    targetHandle: "from-trigger",
+    type: "responseEdge",
+  },
+];
+
+export default {
+  meta,
+  inputs,
+  references,
+  nodes,
+  edges,
+};

From 952991ed6061c7ae335e51c47360b437a31ee980 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:37:28 +0530
Subject: [PATCH 09/33] Create default.md

---
 .../constitutions/default.md                  | 32 +++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 kits/lostfound-match-agent/constitutions/default.md

diff --git a/kits/lostfound-match-agent/constitutions/default.md b/kits/lostfound-match-agent/constitutions/default.md
new file mode 100644
index 00000000..e9110b2d
--- /dev/null
+++ b/kits/lostfound-match-agent/constitutions/default.md
@@ -0,0 +1,32 @@
+# LostFound Match Agent Constitution
+
+## Purpose
+
+The LostFound Match Agent helps lost and found administrators compare lost item reports with found item reports and identify likely matches.
+
+## Safety Rules
+
+- The agent must never claim that two reports are a guaranteed match.
+- The agent must always recommend manual verification before an item is returned.
+- The agent must not reveal sensitive ownership details unnecessarily.
+- The agent must not decide final ownership by itself.
+- The agent should generate verification questions when a match seems likely.
+- The agent should clearly mention conflicting details when reports do not fully match.
+
+## Decision Guidelines
+
+The agent should consider:
+
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity
+- conflicting details
+
+## Output Rule
+
+The agent must return only structured JSON with a match score, decision, reason, matching signals, conflicting signals, verification questions, and next action.

From 727f5fc01d9ca9b2030abf85b63f75b8be613e52 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:38:38 +0530
Subject: [PATCH 10/33] chore: add model config

---
 kits/lostfound-match-agent/model-configs/default.json | 6 ++++++
 1 file changed, 6 insertions(+)
 create mode 100644 kits/lostfound-match-agent/model-configs/default.json

diff --git a/kits/lostfound-match-agent/model-configs/default.json b/kits/lostfound-match-agent/model-configs/default.json
new file mode 100644
index 00000000..f621699b
--- /dev/null
+++ b/kits/lostfound-match-agent/model-configs/default.json
@@ -0,0 +1,6 @@
+{
+  "model": "gpt-4o-mini",
+  "temperature": 0.2,
+  "response_format": "json",
+  "purpose": "Generate a structured lost-and-found match recommendation using item descriptions, locations, dates, and verification signals."
+}

From ea56a75e64b83d15cb77a8095a281ea1583906c2 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 15:39:36 +0530
Subject: [PATCH 11/33] fix: update Lamatic config schema

---
 kits/lostfound-match-agent/lamatic.config.ts | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/kits/lostfound-match-agent/lamatic.config.ts b/kits/lostfound-match-agent/lamatic.config.ts
index ff08daf6..d75a5343 100644
--- a/kits/lostfound-match-agent/lamatic.config.ts
+++ b/kits/lostfound-match-agent/lamatic.config.ts
@@ -1,9 +1,22 @@
 export default {
   name: "LostFound Match Agent",
-  slug: "lostfound-match-agent",
-  type: "template",
   description:
     "AI workflow that compares lost item reports with found item reports and returns a match score, reasoning, verification questions, and next action.",
-  author: "Rewant Anand",
+  version: "1.0.0",
+  type: "template" as const,
+  author: {
+    name: "Rewant Anand",
+    email: "rewu.anand@gmail.com",
+  },
   tags: ["lost-and-found", "matching", "workflow", "automation", "json"],
+  steps: [
+    {
+      id: "lostfound-match-agent",
+      type: "mandatory" as const,
+    },
+  ],
+  links: {
+    github:
+      "https://github.com/Lamatic/AgentKit/tree/main/kits/lostfound-match-agent",
+  },
 };

From d217597da29a52ef2929dcf35a8ee733b20ca5d2 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:31:50 +0530
Subject: [PATCH 12/33] docs: add template README

---
 templates/lostfound-match-agent/README.md | 92 +++++++++++++++++++++++
 1 file changed, 92 insertions(+)
 create mode 100644 templates/lostfound-match-agent/README.md

diff --git a/templates/lostfound-match-agent/README.md b/templates/lostfound-match-agent/README.md
new file mode 100644
index 00000000..f4e6ff06
--- /dev/null
+++ b/templates/lostfound-match-agent/README.md
@@ -0,0 +1,92 @@
+# LostFound Match Agent
+
+## Overview
+
+LostFound Match Agent is an AI workflow that compares lost item reports with found item reports and helps administrators identify likely matches.
+
+It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are often handled manually.
+
+## Problem
+
+Lost and found teams often receive incomplete, messy, or differently written item descriptions.
+
+For example, one user may report:
+
+> Black leather wallet lost near library with student ID.
+
+Another person may report:
+
+> Dark wallet found near reading room with college card inside.
+
+Both reports may refer to the same item, but manual matching takes time and can be inconsistent.
+
+## Solution
+
+This agent compares the lost item report and found item report using:
+
+- item type
+- color
+- brand or material
+- unique identifiers
+- location similarity
+- date/time proximity
+- semantic similarity
+- conflicting details
+
+It then returns a structured match decision with a score, reasoning, verification questions, and next action.
+
+## Input
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}
+```
+
+## Output
+
+```json
+{
+  "match_score": 85,
+  "decision": "Likely Match",
+  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+  "matching_signals": [
+    "Both reports mention a wallet",
+    "Both reports mention a dark or black color",
+    "Both reports mention an ID card",
+    "The locations are similar"
+  ],
+  "conflicting_signals": [
+    "The found report does not mention cash"
+  ],
+  "verification_questions": [
+    "What name is written on the ID card?",
+    "How much cash was inside?",
+    "Does the wallet have any brand or unique mark?"
+  ],
+  "next_action": "Send this case to an admin for manual verification before returning the item."
+}
+```
+
+## Use Cases
+
+- Campus lost and found desks
+- Airport lost property departments
+- Metro station lost and found counters
+- Mall and hotel security teams
+- Lost and found management platforms
+
+## Why this matters
+
+The agent does not replace human verification. It helps admins quickly prioritize likely matches and reduce manual effort.
+
+## Assumptions
+
+- The match score is a recommendation, not a final ownership decision.
+- Valuable or sensitive items should always be manually verified.
+- The quality of the result depends on the quality of the descriptions provided.

From 4cbc877ae47cf3d63bacaa6d526ef859ba884727 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:34:20 +0530
Subject: [PATCH 13/33] chore: add template config

---
 templates/lostfound-match-agent/config.json | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 templates/lostfound-match-agent/config.json

diff --git a/templates/lostfound-match-agent/config.json b/templates/lostfound-match-agent/config.json
new file mode 100644
index 00000000..f2030ed8
--- /dev/null
+++ b/templates/lostfound-match-agent/config.json
@@ -0,0 +1,19 @@
+{
+  "name": "LostFound Match Agent",
+  "slug": "lostfound-match-agent",
+  "description": "Compares lost item reports with found item reports and returns a structured match recommendation with score, reasoning, verification questions, and next action.",
+  "category": "workflow-automation",
+  "tags": [
+    "lost-and-found",
+    "matching",
+    "automation",
+    "json",
+    "admin"
+  ],
+  "author": {
+    "name": "Rewant Anand",
+    "github": "Rewant05"
+  },
+  "version": "1.0.0",
+  "type": "template"
+}

From 5351c005cd571b4eff6837901e86d8480987d59d Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:35:46 +0530
Subject: [PATCH 14/33] chore: add template inputs

---
 templates/lostfound-match-agent/inputs.json | 32 +++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 templates/lostfound-match-agent/inputs.json

diff --git a/templates/lostfound-match-agent/inputs.json b/templates/lostfound-match-agent/inputs.json
new file mode 100644
index 00000000..73e76e31
--- /dev/null
+++ b/templates/lostfound-match-agent/inputs.json
@@ -0,0 +1,32 @@
+{
+  "lost_item_description": {
+    "type": "string",
+    "required": true,
+    "description": "Description of the lost item reported by the user."
+  },
+  "found_item_description": {
+    "type": "string",
+    "required": true,
+    "description": "Description of the found item reported by another user or admin."
+  },
+  "lost_location": {
+    "type": "string",
+    "required": false,
+    "description": "Location where the item was lost."
+  },
+  "found_location": {
+    "type": "string",
+    "required": false,
+    "description": "Location where the item was found."
+  },
+  "lost_date": {
+    "type": "string",
+    "required": false,
+    "description": "Date when the item was lost."
+  },
+  "found_date": {
+    "type": "string",
+    "required": false,
+    "description": "Date when the item was found."
+  }
+}

From 42347c0c5439578423d1a6804bb0e3653d157c06 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:36:35 +0530
Subject: [PATCH 15/33] chore: add template metadata

---
 templates/lostfound-match-agent/meta.json | 39 +++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 templates/lostfound-match-agent/meta.json

diff --git a/templates/lostfound-match-agent/meta.json b/templates/lostfound-match-agent/meta.json
new file mode 100644
index 00000000..54aace78
--- /dev/null
+++ b/templates/lostfound-match-agent/meta.json
@@ -0,0 +1,39 @@
+{
+  "title": "LostFound Match Agent",
+  "description": "An AI template that compares lost item reports with found item reports and generates a structured match recommendation.",
+  "use_case": "Lost and found item matching for campuses, airports, metro stations, malls, hotels, and public institutions.",
+  "problem": "Lost and found teams often receive incomplete or differently written item descriptions, making manual matching slow and inconsistent.",
+  "solution": "The agent compares item descriptions, locations, dates, and unique identifiers to generate a match score, reasoning, verification questions, and next action.",
+  "input_example": {
+    "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+    "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+    "lost_location": "Library",
+    "found_location": "Reading room",
+    "lost_date": "2026-05-10",
+    "found_date": "2026-05-10"
+  },
+  "output_example": {
+    "match_score": 85,
+    "decision": "Likely Match",
+    "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+    "matching_signals": [
+      "Both reports mention a wallet",
+      "Both reports mention a dark or black color",
+      "Both reports mention an ID card",
+      "The locations are similar"
+    ],
+    "conflicting_signals": [
+      "The found report does not mention cash"
+    ],
+    "verification_questions": [
+      "What name is written on the ID card?",
+      "How much cash was inside?",
+      "Does the wallet have any brand or unique mark?"
+    ],
+    "next_action": "Send this case to an admin for manual verification before returning the item."
+  },
+  "author": {
+    "name": "Rewant Anand",
+    "github": "Rewant05"
+  }
+}

From 6caf77dd5643fd5591fc1c337c38f67efccf6b1a Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:40:41 +0530
Subject: [PATCH 16/33] remove old kit files

---
 kits/lostfound-match-agent/README.md | 92 ----------------------------
 1 file changed, 92 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/README.md

diff --git a/kits/lostfound-match-agent/README.md b/kits/lostfound-match-agent/README.md
deleted file mode 100644
index f4e6ff06..00000000
--- a/kits/lostfound-match-agent/README.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# LostFound Match Agent
-
-## Overview
-
-LostFound Match Agent is an AI workflow that compares lost item reports with found item reports and helps administrators identify likely matches.
-
-It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are often handled manually.
-
-## Problem
-
-Lost and found teams often receive incomplete, messy, or differently written item descriptions.
-
-For example, one user may report:
-
-> Black leather wallet lost near library with student ID.
-
-Another person may report:
-
-> Dark wallet found near reading room with college card inside.
-
-Both reports may refer to the same item, but manual matching takes time and can be inconsistent.
-
-## Solution
-
-This agent compares the lost item report and found item report using:
-
-- item type
-- color
-- brand or material
-- unique identifiers
-- location similarity
-- date/time proximity
-- semantic similarity
-- conflicting details
-
-It then returns a structured match decision with a score, reasoning, verification questions, and next action.
-
-## Input
-
-```json
-{
-  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
-  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
-  "lost_location": "Library",
-  "found_location": "Reading room",
-  "lost_date": "2026-05-10",
-  "found_date": "2026-05-10"
-}
-```
-
-## Output
-
-```json
-{
-  "match_score": 85,
-  "decision": "Likely Match",
-  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
-  "matching_signals": [
-    "Both reports mention a wallet",
-    "Both reports mention a dark or black color",
-    "Both reports mention an ID card",
-    "The locations are similar"
-  ],
-  "conflicting_signals": [
-    "The found report does not mention cash"
-  ],
-  "verification_questions": [
-    "What name is written on the ID card?",
-    "How much cash was inside?",
-    "Does the wallet have any brand or unique mark?"
-  ],
-  "next_action": "Send this case to an admin for manual verification before returning the item."
-}
-```
-
-## Use Cases
-
-- Campus lost and found desks
-- Airport lost property departments
-- Metro station lost and found counters
-- Mall and hotel security teams
-- Lost and found management platforms
-
-## Why this matters
-
-The agent does not replace human verification. It helps admins quickly prioritize likely matches and reduce manual effort.
-
-## Assumptions
-
-- The match score is a recommendation, not a final ownership decision.
-- Valuable or sensitive items should always be manually verified.
-- The quality of the result depends on the quality of the descriptions provided.

From 6cb35d98fb731b503b80d171b6964b2efe9270fc Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:40:53 +0530
Subject: [PATCH 17/33] remove old kit files

---
 kits/lostfound-match-agent/FLOW.md | 78 ------------------------------
 1 file changed, 78 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/FLOW.md

diff --git a/kits/lostfound-match-agent/FLOW.md b/kits/lostfound-match-agent/FLOW.md
deleted file mode 100644
index 3ca57432..00000000
--- a/kits/lostfound-match-agent/FLOW.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# LostFound Match Agent Flow
-
-## Flow Purpose
-
-This flow compares a lost item report with a found item report and generates a structured match recommendation.
-
-The goal is to help lost and found administrators prioritize likely matches faster while keeping manual verification in the loop.
-
-## Flow Input
-
-```json
-{
-  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
-  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
-  "lost_location": "Library",
-  "found_location": "Reading room",
-  "lost_date": "2026-05-10",
-  "found_date": "2026-05-10"
-}
-```
-
-## Flow Steps
-
-1. Receive the lost item and found item reports.
-2. Compare item type, color, material, unique identifiers, location, and date.
-3. Identify matching signals and conflicting signals.
-4. Generate a match score from 0 to 100.
-5. Return a structured JSON response with decision, reasoning, verification questions, and next action.
-
-## Agent Prompt
-
-You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
-
-Compare the lost item report and found item report carefully.
-
-Consider:
-- item type
-- color
-- brand
-- material
-- unique identifiers
-- location similarity
-- date or time proximity
-- semantic similarity
-- conflicting details
-
-Return only valid JSON.
-
-Do not claim a guaranteed match. Always recommend manual verification before returning an item.
-
-## Expected Output
-
-```json
-{
-  "match_score": 85,
-  "decision": "Likely Match",
-  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
-  "matching_signals": [
-    "Both reports mention a wallet",
-    "Both reports mention a dark or black color",
-    "Both reports mention an ID card",
-    "The locations are similar"
-  ],
-  "conflicting_signals": [
-    "The found report does not mention cash"
-  ],
-  "verification_questions": [
-    "What name is written on the ID card?",
-    "How much cash was inside?",
-    "Does the wallet have any brand or unique mark?"
-  ],
-  "next_action": "Send this case to an admin for manual verification before returning the item."
-}
-```
-
-## Notes
-
-This flow provides a recommendation only. Final ownership confirmation should always be handled by an admin or authorized lost and found team.

From 89785e66a9a4b1e160fd567a9e9ec8fd60844e42 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:41:06 +0530
Subject: [PATCH 18/33] remove old kit files

---
 kits/lostfound-match-agent/lamatic.config.ts | 22 --------------------
 1 file changed, 22 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/lamatic.config.ts

diff --git a/kits/lostfound-match-agent/lamatic.config.ts b/kits/lostfound-match-agent/lamatic.config.ts
deleted file mode 100644
index d75a5343..00000000
--- a/kits/lostfound-match-agent/lamatic.config.ts
+++ /dev/null
@@ -1,22 +0,0 @@
-export default {
-  name: "LostFound Match Agent",
-  description:
-    "AI workflow that compares lost item reports with found item reports and returns a match score, reasoning, verification questions, and next action.",
-  version: "1.0.0",
-  type: "template" as const,
-  author: {
-    name: "Rewant Anand",
-    email: "rewu.anand@gmail.com",
-  },
-  tags: ["lost-and-found", "matching", "workflow", "automation", "json"],
-  steps: [
-    {
-      id: "lostfound-match-agent",
-      type: "mandatory" as const,
-    },
-  ],
-  links: {
-    github:
-      "https://github.com/Lamatic/AgentKit/tree/main/kits/lostfound-match-agent",
-  },
-};

From 486ca81143b3590966b9e82f6e626f2f6619d732 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:41:27 +0530
Subject: [PATCH 19/33] remove old kit files

---
 kits/lostfound-match-agent/agent.md | 86 -----------------------------
 1 file changed, 86 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/agent.md

diff --git a/kits/lostfound-match-agent/agent.md b/kits/lostfound-match-agent/agent.md
deleted file mode 100644
index 38ccc5b0..00000000
--- a/kits/lostfound-match-agent/agent.md
+++ /dev/null
@@ -1,86 +0,0 @@
-# LostFound Match Agent
-
-## Role
-
-You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
-
-Your job is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
-
-## Instructions
-
-Compare the reports using the following signals:
-
-- item type
-- color
-- brand
-- material
-- unique identifiers
-- location similarity
-- date or time proximity
-- semantic similarity between descriptions
-- conflicting details
-
-Return only valid JSON.
-
-Do not claim a guaranteed match. Always recommend manual verification before returning an item.
-
-## Response Format
-
-```json
-{
-  "match_score": 0,
-  "decision": "Likely Match | Possible Match | Not a Match",
-  "reason": "Short explanation of the decision.",
-  "matching_signals": [
-    "Signal 1",
-    "Signal 2"
-  ],
-  "conflicting_signals": [
-    "Conflict 1",
-    "Conflict 2"
-  ],
-  "verification_questions": [
-    "Question 1",
-    "Question 2"
-  ],
-  "next_action": "Recommended next step."
-}
-```
-
-## Example Input
-
-```json
-{
-  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
-  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
-  "lost_location": "Library",
-  "found_location": "Reading room",
-  "lost_date": "2026-05-10",
-  "found_date": "2026-05-10"
-}
-```
-
-## Example Output
-
-```json
-{
-  "match_score": 85,
-  "decision": "Likely Match",
-  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
-  "matching_signals": [
-    "Both reports mention a wallet",
-    "Both reports mention a dark or black color",
-    "Both reports mention an ID card",
-    "The locations are similar"
-  ],
-  "conflicting_signals": [
-    "The found report does not mention cash"
-  ],
-  "verification_questions": [
-    "What name is written on the ID card?",
-    "How much cash was inside?",
-    "Does the wallet have any brand or unique mark?"
-  ],
-  "next_action": "Send this case to an admin for manual verification before returning the item."
-}
-```

From 11d2937a996780512c9996f3cb82263022b27684 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:43:28 +0530
Subject: [PATCH 20/33] remove old kit nested files

---
 .../constitutions/default.md                  | 32 -------------------
 1 file changed, 32 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/constitutions/default.md

diff --git a/kits/lostfound-match-agent/constitutions/default.md b/kits/lostfound-match-agent/constitutions/default.md
deleted file mode 100644
index e9110b2d..00000000
--- a/kits/lostfound-match-agent/constitutions/default.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# LostFound Match Agent Constitution
-
-## Purpose
-
-The LostFound Match Agent helps lost and found administrators compare lost item reports with found item reports and identify likely matches.
-
-## Safety Rules
-
-- The agent must never claim that two reports are a guaranteed match.
-- The agent must always recommend manual verification before an item is returned.
-- The agent must not reveal sensitive ownership details unnecessarily.
-- The agent must not decide final ownership by itself.
-- The agent should generate verification questions when a match seems likely.
-- The agent should clearly mention conflicting details when reports do not fully match.
-
-## Decision Guidelines
-
-The agent should consider:
-
-- item type
-- color
-- brand
-- material
-- unique identifiers
-- location similarity
-- date or time proximity
-- semantic similarity
-- conflicting details
-
-## Output Rule
-
-The agent must return only structured JSON with a match score, decision, reason, matching signals, conflicting signals, verification questions, and next action.

From 6cc6285d908c4fe3691abcb6dd507fc4b13d6e62 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:43:41 +0530
Subject: [PATCH 21/33] remove old kit nested files

---
 .../flows/lostfound-match-agent.ts            | 135 ------------------
 1 file changed, 135 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/flows/lostfound-match-agent.ts

diff --git a/kits/lostfound-match-agent/flows/lostfound-match-agent.ts b/kits/lostfound-match-agent/flows/lostfound-match-agent.ts
deleted file mode 100644
index f663f76f..00000000
--- a/kits/lostfound-match-agent/flows/lostfound-match-agent.ts
+++ /dev/null
@@ -1,135 +0,0 @@
-/*
-# LostFound Match Agent
-
-This flow compares a lost item report with a found item report and returns a structured match recommendation.
-
-It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are handled manually.
-*/
-
-export const meta = {
-  name: "LostFound Match Agent",
-  description:
-    "Compares lost and found item reports and returns a match score, reasoning, verification questions, and next action.",
-  tags: ["lost-and-found", "matching", "automation", "json"],
-  testInput: {
-    lost_item_description:
-      "Black leather wallet lost near library. It had my student ID card and some cash.",
-    found_item_description:
-      "Dark wallet found near reading room with a college ID card inside.",
-    lost_location: "Library",
-    found_location: "Reading room",
-    lost_date: "2026-05-10",
-    found_date: "2026-05-10",
-  },
-  githubUrl:
-    "https://github.com/Rewant05/AgentKit/tree/lostfound-match-agent/kits/lostfound-match-agent",
-  documentationUrl:
-    "https://github.com/Rewant05/AgentKit/tree/lostfound-match-agent/kits/lostfound-match-agent/README.md",
-  deployUrl: "",
-  author: {
-    name: "Rewant Anand",
-    email: "rewu.anand@gmail.com",
-  },
-};
-
-export const inputs = {};
-
-export const references = {
-  prompts: {
-    lostfound_match_agent_system:
-      "@prompts/lostfound-match-agent_system.md",
-  },
-};
-
-export const nodes = [
-  {
-    id: "triggerNode_1",
-    type: "triggerNode",
-    position: {
-      x: 0,
-      y: 0,
-    },
-    data: {
-      nodeId: "graphqlNode",
-      trigger: true,
-      values: {
-        nodeName: "API Request",
-        responeType: "realtime",
-        advance_schema: "",
-      },
-    },
-  },
-  {
-    id: "LLMNode_1",
-    type: "dynamicNode",
-    position: {
-      x: 0,
-      y: 0,
-    },
-    data: {
-      nodeId: "LLMNode",
-      values: {
-        nodeName: "Generate Match Decision",
-        tools: [],
-        prompts: [
-          {
-            id: "lostfound-match-agent-system-prompt",
-            role: "system",
-            content: "@prompts/lostfound-match-agent_system.md",
-          },
-        ],
-      },
-    },
-  },
-  {
-    id: "graphqlResponseNode_1",
-    type: "dynamicNode",
-    position: {
-      x: 0,
-      y: 0,
-    },
-    data: {
-      nodeId: "graphqlResponseNode",
-      values: {
-        nodeName: "API Response",
-        outputMapping:
-          '{\n  "output": "{{LLMNode_1.output.generatedResponse}}"\n}',
-      },
-    },
-  },
-];
-
-export const edges = [
-  {
-    id: "triggerNode_1-LLMNode_1",
-    source: "triggerNode_1",
-    target: "LLMNode_1",
-    sourceHandle: "bottom",
-    targetHandle: "top",
-    type: "defaultEdge",
-  },
-  {
-    id: "LLMNode_1-graphqlResponseNode_1",
-    source: "LLMNode_1",
-    target: "graphqlResponseNode_1",
-    sourceHandle: "bottom",
-    targetHandle: "top",
-    type: "defaultEdge",
-  },
-  {
-    id: "response-graphqlResponseNode_1",
-    source: "triggerNode_1",
-    target: "graphqlResponseNode_1",
-    sourceHandle: "to-response",
-    targetHandle: "from-trigger",
-    type: "responseEdge",
-  },
-];
-
-export default {
-  meta,
-  inputs,
-  references,
-  nodes,
-  edges,
-};

From 4f41467e0e17dc583afa483141cce8be895d52db Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:43:54 +0530
Subject: [PATCH 22/33] remove old kit nested files

---
 .../prompts/lostfound-match-agent_system.md   | 45 -------------------
 1 file changed, 45 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md

diff --git a/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
deleted file mode 100644
index 657ac0c5..00000000
--- a/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
+++ /dev/null
@@ -1,45 +0,0 @@
-You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
-
-Your task is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
-
-Use the following input fields:
-- lost_item_description: {{triggerNode_1.output.lost_item_description}}
-- found_item_description: {{triggerNode_1.output.found_item_description}}
-- lost_location: {{triggerNode_1.output.lost_location}}
-- found_location: {{triggerNode_1.output.found_location}}
-- lost_date: {{triggerNode_1.output.lost_date}}
-- found_date: {{triggerNode_1.output.found_date}}
-
-Compare the reports using:
-- item type
-- color
-- brand
-- material
-- unique identifiers
-- location similarity
-- date or time proximity
-- semantic similarity between descriptions
-- conflicting details
-
-Return only valid JSON in this format:
-
-{
-  "match_score": 0,
-  "decision": "Likely Match | Possible Match | Not a Match",
-  "reason": "Short explanation of the decision.",
-  "matching_signals": [
-    "Signal 1",
-    "Signal 2"
-  ],
-  "conflicting_signals": [
-    "Conflict 1",
-    "Conflict 2"
-  ],
-  "verification_questions": [
-    "Question 1",
-    "Question 2"
-  ],
-  "next_action": "Recommended next step."
-}
-
-Do not claim a guaranteed match. Always recommend manual verification before returning an item.

From bd3c263278895799ee3d09cca4b6877dbee104dc Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Thu, 14 May 2026 16:44:50 +0530
Subject: [PATCH 23/33] delete old files

---
 kits/lostfound-match-agent/model-configs/default.json | 6 ------
 1 file changed, 6 deletions(-)
 delete mode 100644 kits/lostfound-match-agent/model-configs/default.json

diff --git a/kits/lostfound-match-agent/model-configs/default.json b/kits/lostfound-match-agent/model-configs/default.json
deleted file mode 100644
index f621699b..00000000
--- a/kits/lostfound-match-agent/model-configs/default.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
-  "model": "gpt-4o-mini",
-  "temperature": 0.2,
-  "response_format": "json",
-  "purpose": "Generate a structured lost-and-found match recommendation using item descriptions, locations, dates, and verification signals."
-}

From ba475f33d346d412f394900af702cb883361d9e2 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 13:43:08 +0530
Subject: [PATCH 24/33] move template README to kits structure

Added README.md for LostFound Match Agent detailing its purpose, problem, solution, input/output examples, use cases, and assumptions.
---
 kits/lostfound-match-agent/README.md | 92 ++++++++++++++++++++++++++++
 1 file changed, 92 insertions(+)
 create mode 100644 kits/lostfound-match-agent/README.md

diff --git a/kits/lostfound-match-agent/README.md b/kits/lostfound-match-agent/README.md
new file mode 100644
index 00000000..f4e6ff06
--- /dev/null
+++ b/kits/lostfound-match-agent/README.md
@@ -0,0 +1,92 @@
+# LostFound Match Agent
+
+## Overview
+
+LostFound Match Agent is an AI workflow that compares lost item reports with found item reports and helps administrators identify likely matches.
+
+It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are often handled manually.
+
+## Problem
+
+Lost and found teams often receive incomplete, messy, or differently written item descriptions.
+
+For example, one user may report:
+
+> Black leather wallet lost near library with student ID.
+
+Another person may report:
+
+> Dark wallet found near reading room with college card inside.
+
+Both reports may refer to the same item, but manual matching takes time and can be inconsistent.
+
+## Solution
+
+This agent compares the lost item report and found item report using:
+
+- item type
+- color
+- brand or material
+- unique identifiers
+- location similarity
+- date/time proximity
+- semantic similarity
+- conflicting details
+
+It then returns a structured match decision with a score, reasoning, verification questions, and next action.
+
+## Input
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}
+```
+
+## Output
+
+```json
+{
+  "match_score": 85,
+  "decision": "Likely Match",
+  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+  "matching_signals": [
+    "Both reports mention a wallet",
+    "Both reports mention a dark or black color",
+    "Both reports mention an ID card",
+    "The locations are similar"
+  ],
+  "conflicting_signals": [
+    "The found report does not mention cash"
+  ],
+  "verification_questions": [
+    "What name is written on the ID card?",
+    "How much cash was inside?",
+    "Does the wallet have any brand or unique mark?"
+  ],
+  "next_action": "Send this case to an admin for manual verification before returning the item."
+}
+```
+
+## Use Cases
+
+- Campus lost and found desks
+- Airport lost property departments
+- Metro station lost and found counters
+- Mall and hotel security teams
+- Lost and found management platforms
+
+## Why this matters
+
+The agent does not replace human verification. It helps admins quickly prioritize likely matches and reduce manual effort.
+
+## Assumptions
+
+- The match score is a recommendation, not a final ownership decision.
+- Valuable or sensitive items should always be manually verified.
+- The quality of the result depends on the quality of the descriptions provided.

From 5534c034d15fc75c531b57512eb894242fef0515 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:28:51 +0530
Subject: [PATCH 25/33] add Lamatic config for kits structure

---
 kits/lostfound-match-agent/lamatic.config.ts | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 kits/lostfound-match-agent/lamatic.config.ts

diff --git a/kits/lostfound-match-agent/lamatic.config.ts b/kits/lostfound-match-agent/lamatic.config.ts
new file mode 100644
index 00000000..b592f6c7
--- /dev/null
+++ b/kits/lostfound-match-agent/lamatic.config.ts
@@ -0,0 +1,18 @@
+export default {
+  name: "LostFound Match Agent",
+  description:
+    "AI workflow that compares lost item reports with found item reports and returns a match score, reasoning, verification questions, and next action.",
+  version: "1.0.0",
+  type: "template" as const,
+  author: {
+    name: "Rewant Anand",
+    github: "Rewant05",
+  },
+  tags: ["lost-and-found", "matching", "workflow", "automation", "json"],
+  steps: [
+    {
+      id: "lostfound-match-agent",
+      type: "mandatory" as const,
+    },
+  ],
+};

From 7bbdd226dbbadb94513a415f6017d1d10f5ea73c Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:29:41 +0530
Subject: [PATCH 26/33] move agent instructions to kits structure

---
 kits/lostfound-match-agent/agent.md | 86 +++++++++++++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 kits/lostfound-match-agent/agent.md

diff --git a/kits/lostfound-match-agent/agent.md b/kits/lostfound-match-agent/agent.md
new file mode 100644
index 00000000..38ccc5b0
--- /dev/null
+++ b/kits/lostfound-match-agent/agent.md
@@ -0,0 +1,86 @@
+# LostFound Match Agent
+
+## Role
+
+You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
+
+Your job is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
+
+## Instructions
+
+Compare the reports using the following signals:
+
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity between descriptions
+- conflicting details
+
+Return only valid JSON.
+
+Do not claim a guaranteed match. Always recommend manual verification before returning an item.
+
+## Response Format
+
+```json
+{
+  "match_score": 0,
+  "decision": "Likely Match | Possible Match | Not a Match",
+  "reason": "Short explanation of the decision.",
+  "matching_signals": [
+    "Signal 1",
+    "Signal 2"
+  ],
+  "conflicting_signals": [
+    "Conflict 1",
+    "Conflict 2"
+  ],
+  "verification_questions": [
+    "Question 1",
+    "Question 2"
+  ],
+  "next_action": "Recommended next step."
+}
+```
+
+## Example Input
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}
+```
+
+## Example Output
+
+```json
+{
+  "match_score": 85,
+  "decision": "Likely Match",
+  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
+  "matching_signals": [
+    "Both reports mention a wallet",
+    "Both reports mention a dark or black color",
+    "Both reports mention an ID card",
+    "The locations are similar"
+  ],
+  "conflicting_signals": [
+    "The found report does not mention cash"
+  ],
+  "verification_questions": [
+    "What name is written on the ID card?",
+    "How much cash was inside?",
+    "Does the wallet have any brand or unique mark?"
+  ],
+  "next_action": "Send this case to an admin for manual verification before returning the item."
+}
+```

From 41a65bd01c06eb8f7732ab674986b22eadd09153 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:32:09 +0530
Subject: [PATCH 27/33] feat: add flow to kits structure

---
 .../flows/lostfound-match-agent.ts            | 73 +++++++++++++++++++
 1 file changed, 73 insertions(+)
 create mode 100644 kits/lostfound-match-agent/flows/lostfound-match-agent.ts

diff --git a/kits/lostfound-match-agent/flows/lostfound-match-agent.ts b/kits/lostfound-match-agent/flows/lostfound-match-agent.ts
new file mode 100644
index 00000000..8360d425
--- /dev/null
+++ b/kits/lostfound-match-agent/flows/lostfound-match-agent.ts
@@ -0,0 +1,73 @@
+/*
+# LostFound Match Agent
+
+This flow compares a lost item report with a found item report and returns a structured match recommendation.
+
+It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are handled manually.
+*/
+
+export const meta = {
+  name: "LostFound Match Agent",
+  description:
+    "Compares lost and found item reports and returns a match score, reasoning, verification questions, and next action.",
+  tags: ["lost-and-found", "matching", "automation", "json"],
+  testInput: {
+    lost_item_description:
+      "Black leather wallet lost near library. It had my student ID card and some cash.",
+    found_item_description:
+      "Dark wallet found near reading room with a college ID card inside.",
+    lost_location: "Library",
+    found_location: "Reading room",
+    lost_date: "2026-05-10",
+    found_date: "2026-05-10"
+  },
+  author: {
+    name: "Rewant Anand",
+    github: "Rewant05"
+  }
+};
+
+export const inputs = {
+  lost_item_description: {
+    type: "string",
+    required: true,
+    description: "Description of the lost item reported by the user."
+  },
+  found_item_description: {
+    type: "string",
+    required: true,
+    description: "Description of the found item reported by another user or admin."
+  },
+  lost_location: {
+    type: "string",
+    required: false,
+    description: "Location where the item was lost."
+  },
+  found_location: {
+    type: "string",
+    required: false,
+    description: "Location where the item was found."
+  },
+  lost_date: {
+    type: "string",
+    required: false,
+    description: "Date when the item was lost."
+  },
+  found_date: {
+    type: "string",
+    required: false,
+    description: "Date when the item was found."
+  }
+};
+
+export const references = {
+  prompts: {
+    system: "@prompts/lostfound-match-agent_system.md"
+  }
+};
+
+export default {
+  meta,
+  inputs,
+  references
+};

From 48bf18bdab71171f399b6a04e62bdc102fb8b5a7 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:33:07 +0530
Subject: [PATCH 28/33] docs: move prompt to kits structure

---
 .../prompts/lostfound-match-agent_system.md   | 45 +++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md

diff --git a/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
new file mode 100644
index 00000000..8c80ecb5
--- /dev/null
+++ b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
@@ -0,0 +1,45 @@
+You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
+
+Your task is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
+
+Use the following input fields:
+- lost_item_description
+- found_item_description
+- lost_location
+- found_location
+- lost_date
+- found_date
+
+Compare the reports using:
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity between descriptions
+- conflicting details
+
+Return only valid JSON in this format:
+
+{
+  "match_score": 0,
+  "decision": "Likely Match | Possible Match | Not a Match",
+  "reason": "Short explanation of the decision.",
+  "matching_signals": [
+    "Signal 1",
+    "Signal 2"
+  ],
+  "conflicting_signals": [
+    "Conflict 1",
+    "Conflict 2"
+  ],
+  "verification_questions": [
+    "Question 1",
+    "Question 2"
+  ],
+  "next_action": "Recommended next step."
+}
+
+Do not claim a guaranteed match. Always recommend manual verification before returning an item.

From 30033971a48051c80573784c5e38506fdd0b525b Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:34:04 +0530
Subject: [PATCH 29/33] docs: add constitution to kits structure

---
 .../constitutions/default.md                  | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 kits/lostfound-match-agent/constitutions/default.md

diff --git a/kits/lostfound-match-agent/constitutions/default.md b/kits/lostfound-match-agent/constitutions/default.md
new file mode 100644
index 00000000..244379d6
--- /dev/null
+++ b/kits/lostfound-match-agent/constitutions/default.md
@@ -0,0 +1,31 @@
+# LostFound Match Agent Constitution
+
+## Purpose
+
+The LostFound Match Agent helps lost and found administrators compare lost item reports with found item reports and identify likely matches.
+
+## Safety Rules
+
+- The agent must never claim that two reports are a guaranteed match.
+- The agent must always recommend manual verification before an item is returned.
+- The agent must not decide final ownership by itself.
+- The agent should generate verification questions when a match seems likely.
+- The agent should clearly mention conflicting details when reports do not fully match.
+
+## Decision Guidelines
+
+The agent should consider:
+
+- item type
+- color
+- brand
+- material
+- unique identifiers
+- location similarity
+- date or time proximity
+- semantic similarity
+- conflicting details
+
+## Output Rule
+
+The agent must return structured JSON with a match score, decision, reason, matching signals, conflicting signals, verification questions, and next action.

From 5270683045a15e7e96bbaf27e233f0e38d098743 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:37:14 +0530
Subject: [PATCH 30/33] fix: update config for kits template structure

---
 kits/lostfound-match-agent/lamatic.config.ts | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/kits/lostfound-match-agent/lamatic.config.ts b/kits/lostfound-match-agent/lamatic.config.ts
index b592f6c7..f645a8e8 100644
--- a/kits/lostfound-match-agent/lamatic.config.ts
+++ b/kits/lostfound-match-agent/lamatic.config.ts
@@ -6,7 +6,7 @@ export default {
   type: "template" as const,
   author: {
     name: "Rewant Anand",
-    github: "Rewant05",
+    email: "rewant23429@iiitd.ac.in",
   },
   tags: ["lost-and-found", "matching", "workflow", "automation", "json"],
   steps: [
@@ -15,4 +15,8 @@ export default {
       type: "mandatory" as const,
     },
   ],
+  links: {
+    github:
+      "https://github.com/Lamatic/AgentKit/tree/main/kits/lostfound-match-agent",
+  },
 };

From 546aff01eeac4cad556a69b1977c23d3e796ea3a Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:46:41 +0530
Subject: [PATCH 31/33] Delete templates/lostfound-match-agent directory

---
 templates/lostfound-match-agent/README.md   | 92 ---------------------
 templates/lostfound-match-agent/config.json | 19 -----
 templates/lostfound-match-agent/inputs.json | 32 -------
 templates/lostfound-match-agent/meta.json   | 39 ---------
 4 files changed, 182 deletions(-)
 delete mode 100644 templates/lostfound-match-agent/README.md
 delete mode 100644 templates/lostfound-match-agent/config.json
 delete mode 100644 templates/lostfound-match-agent/inputs.json
 delete mode 100644 templates/lostfound-match-agent/meta.json

diff --git a/templates/lostfound-match-agent/README.md b/templates/lostfound-match-agent/README.md
deleted file mode 100644
index f4e6ff06..00000000
--- a/templates/lostfound-match-agent/README.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# LostFound Match Agent
-
-## Overview
-
-LostFound Match Agent is an AI workflow that compares lost item reports with found item reports and helps administrators identify likely matches.
-
-It is designed for campuses, airports, metro stations, malls, hotels, and other public places where lost and found reports are often handled manually.
-
-## Problem
-
-Lost and found teams often receive incomplete, messy, or differently written item descriptions.
-
-For example, one user may report:
-
-> Black leather wallet lost near library with student ID.
-
-Another person may report:
-
-> Dark wallet found near reading room with college card inside.
-
-Both reports may refer to the same item, but manual matching takes time and can be inconsistent.
-
-## Solution
-
-This agent compares the lost item report and found item report using:
-
-- item type
-- color
-- brand or material
-- unique identifiers
-- location similarity
-- date/time proximity
-- semantic similarity
-- conflicting details
-
-It then returns a structured match decision with a score, reasoning, verification questions, and next action.
-
-## Input
-
-```json
-{
-  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
-  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
-  "lost_location": "Library",
-  "found_location": "Reading room",
-  "lost_date": "2026-05-10",
-  "found_date": "2026-05-10"
-}
-```
-
-## Output
-
-```json
-{
-  "match_score": 85,
-  "decision": "Likely Match",
-  "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
-  "matching_signals": [
-    "Both reports mention a wallet",
-    "Both reports mention a dark or black color",
-    "Both reports mention an ID card",
-    "The locations are similar"
-  ],
-  "conflicting_signals": [
-    "The found report does not mention cash"
-  ],
-  "verification_questions": [
-    "What name is written on the ID card?",
-    "How much cash was inside?",
-    "Does the wallet have any brand or unique mark?"
-  ],
-  "next_action": "Send this case to an admin for manual verification before returning the item."
-}
-```
-
-## Use Cases
-
-- Campus lost and found desks
-- Airport lost property departments
-- Metro station lost and found counters
-- Mall and hotel security teams
-- Lost and found management platforms
-
-## Why this matters
-
-The agent does not replace human verification. It helps admins quickly prioritize likely matches and reduce manual effort.
-
-## Assumptions
-
-- The match score is a recommendation, not a final ownership decision.
-- Valuable or sensitive items should always be manually verified.
-- The quality of the result depends on the quality of the descriptions provided.
diff --git a/templates/lostfound-match-agent/config.json b/templates/lostfound-match-agent/config.json
deleted file mode 100644
index f2030ed8..00000000
--- a/templates/lostfound-match-agent/config.json
+++ /dev/null
@@ -1,19 +0,0 @@
-{
-  "name": "LostFound Match Agent",
-  "slug": "lostfound-match-agent",
-  "description": "Compares lost item reports with found item reports and returns a structured match recommendation with score, reasoning, verification questions, and next action.",
-  "category": "workflow-automation",
-  "tags": [
-    "lost-and-found",
-    "matching",
-    "automation",
-    "json",
-    "admin"
-  ],
-  "author": {
-    "name": "Rewant Anand",
-    "github": "Rewant05"
-  },
-  "version": "1.0.0",
-  "type": "template"
-}
diff --git a/templates/lostfound-match-agent/inputs.json b/templates/lostfound-match-agent/inputs.json
deleted file mode 100644
index 73e76e31..00000000
--- a/templates/lostfound-match-agent/inputs.json
+++ /dev/null
@@ -1,32 +0,0 @@
-{
-  "lost_item_description": {
-    "type": "string",
-    "required": true,
-    "description": "Description of the lost item reported by the user."
-  },
-  "found_item_description": {
-    "type": "string",
-    "required": true,
-    "description": "Description of the found item reported by another user or admin."
-  },
-  "lost_location": {
-    "type": "string",
-    "required": false,
-    "description": "Location where the item was lost."
-  },
-  "found_location": {
-    "type": "string",
-    "required": false,
-    "description": "Location where the item was found."
-  },
-  "lost_date": {
-    "type": "string",
-    "required": false,
-    "description": "Date when the item was lost."
-  },
-  "found_date": {
-    "type": "string",
-    "required": false,
-    "description": "Date when the item was found."
-  }
-}
diff --git a/templates/lostfound-match-agent/meta.json b/templates/lostfound-match-agent/meta.json
deleted file mode 100644
index 54aace78..00000000
--- a/templates/lostfound-match-agent/meta.json
+++ /dev/null
@@ -1,39 +0,0 @@
-{
-  "title": "LostFound Match Agent",
-  "description": "An AI template that compares lost item reports with found item reports and generates a structured match recommendation.",
-  "use_case": "Lost and found item matching for campuses, airports, metro stations, malls, hotels, and public institutions.",
-  "problem": "Lost and found teams often receive incomplete or differently written item descriptions, making manual matching slow and inconsistent.",
-  "solution": "The agent compares item descriptions, locations, dates, and unique identifiers to generate a match score, reasoning, verification questions, and next action.",
-  "input_example": {
-    "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
-    "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
-    "lost_location": "Library",
-    "found_location": "Reading room",
-    "lost_date": "2026-05-10",
-    "found_date": "2026-05-10"
-  },
-  "output_example": {
-    "match_score": 85,
-    "decision": "Likely Match",
-    "reason": "Both reports describe a dark wallet found near similar academic locations and mention an ID card.",
-    "matching_signals": [
-      "Both reports mention a wallet",
-      "Both reports mention a dark or black color",
-      "Both reports mention an ID card",
-      "The locations are similar"
-    ],
-    "conflicting_signals": [
-      "The found report does not mention cash"
-    ],
-    "verification_questions": [
-      "What name is written on the ID card?",
-      "How much cash was inside?",
-      "Does the wallet have any brand or unique mark?"
-    ],
-    "next_action": "Send this case to an admin for manual verification before returning the item."
-  },
-  "author": {
-    "name": "Rewant Anand",
-    "github": "Rewant05"
-  }
-}

From 370f0a7bd8b4b2f9710ac298d1514c8375da0e48 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 14:57:25 +0530
Subject: [PATCH 32/33] fix: tighten system prompt output contract

Clarify the JSON response format and update decision options.
---
 .../prompts/lostfound-match-agent_system.md         | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
index 8c80ecb5..9606d604 100644
--- a/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
+++ b/kits/lostfound-match-agent/prompts/lostfound-match-agent_system.md
@@ -1,8 +1,11 @@
+# LostFound Match Agent System Prompt
+
 You are a Lost and Found Matching Agent for institutions such as campuses, airports, malls, hotels, and metro stations.
 
 Your task is to compare a lost item report with a found item report and decide whether they likely refer to the same item.
 
 Use the following input fields:
+
 - lost_item_description
 - found_item_description
 - lost_location
@@ -11,6 +14,7 @@ Use the following input fields:
 - found_date
 
 Compare the reports using:
+
 - item type
 - color
 - brand
@@ -21,11 +25,14 @@ Compare the reports using:
 - semantic similarity between descriptions
 - conflicting details
 
-Return only valid JSON in this format:
+Return only valid JSON.
 
+The JSON response must follow this contract:
+
+```json
 {
   "match_score": 0,
-  "decision": "Likely Match | Possible Match | Not a Match",
+  "decision": "Likely Match",
   "reason": "Short explanation of the decision.",
   "matching_signals": [
     "Signal 1",
@@ -41,5 +48,3 @@ Return only valid JSON in this format:
   ],
   "next_action": "Recommended next step."
 }
-
-Do not claim a guaranteed match. Always recommend manual verification before returning an item.

From b449ddbaa6db47ae1833664ad284b510e209efc7 Mon Sep 17 00:00:00 2001
From: Rewant Anand <163150791+Rewant05@users.noreply.github.com>
Date: Sat, 16 May 2026 15:03:54 +0530
Subject: [PATCH 33/33] ```text docs: add setup environment and usage sections

Added setup instructions, environment variables, and usage examples for the Lamatic AgentKit template.
---
 kits/lostfound-match-agent/README.md | 39 ++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

diff --git a/kits/lostfound-match-agent/README.md b/kits/lostfound-match-agent/README.md
index f4e6ff06..ea138d82 100644
--- a/kits/lostfound-match-agent/README.md
+++ b/kits/lostfound-match-agent/README.md
@@ -90,3 +90,42 @@ The agent does not replace human verification. It helps admins quickly prioritiz
 - The match score is a recommendation, not a final ownership decision.
 - Valuable or sensitive items should always be manually verified.
 - The quality of the result depends on the quality of the descriptions provided.
+
+## Setup
+
+This is a Lamatic AgentKit template for a single flow. It does not include a frontend app or local runtime.
+
+To use this template:
+
+1. Open Lamatic Studio.
+2. Create a new project or open an existing project.
+3. Import or recreate the flow using the files in this template.
+4. Configure the LLM/model provider inside Lamatic Studio.
+5. Deploy the flow from Lamatic Studio.
+6. Test the flow using the sample input shown below.
+
+No local `npm install` or `npm run dev` step is required because this is a flow-only template, not a full kit with a Next.js app.
+
+## Environment Variables
+
+This template does not require any environment variables in the repository.
+
+Any required model/API credentials should be configured securely inside Lamatic Studio or the connected provider settings.
+
+Do not commit real API keys or secrets to this repository.
+
+## Usage
+
+Send a lost item report and a found item report to the flow.
+
+Example input:
+
+```json
+{
+  "lost_item_description": "Black leather wallet lost near library. It had my student ID card and some cash.",
+  "found_item_description": "Dark wallet found near reading room with a college ID card inside.",
+  "lost_location": "Library",
+  "found_location": "Reading room",
+  "lost_date": "2026-05-10",
+  "found_date": "2026-05-10"
+}