feat: add LostFound Match Agent template#158
Conversation
WalkthroughThis mission introduces the LostFound Match Agent template to the AgentKit repository. The PR adds four files that collectively define a new template for matching lost versus found item reports using comparison signals including type, color, brand, identifiers, location proximity, date proximity, and semantic similarity. ChangesLostFound Match Agent Template
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Validation ResultsNew Contributions Detected
Check Results
🎉 All checks passed! This contribution follows the AgentKit structure. |
|
Hi Lamatic team, the validation checks have passed and this PR has received the passing-checks label. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@templates/lostfound-match-agent/meta.json`:
- Around line 15-34: Add a formal output schema file describing the agent's
response contract to validate the fields shown in output_example: create an
outputs.json that defines each top-level property (match_score, decision,
reason, matching_signals, conflicting_signals, verification_questions,
next_action) with types, required=true where appropriate, descriptions, and
constraints (e.g., match_score numeric 0–100, arrays of strings for
signals/questions). Ensure the schema keys exactly match the example in
meta.json so integrators can validate agent responses and catch breaking
changes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: ff8ecfab-c3ed-4cf2-a1b6-1753d77bdc6b
📒 Files selected for processing (4)
templates/lostfound-match-agent/README.mdtemplates/lostfound-match-agent/config.jsontemplates/lostfound-match-agent/inputs.jsontemplates/lostfound-match-agent/meta.json
| "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." | ||
| }, |
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial | ⚡ Quick win
Agent, consider documenting the output contract.
The output example demonstrates a well-structured match result with match_score, decision, reason, matching_signals, conflicting_signals, verification_questions, and next_action. However, there's no formal output schema (like an outputs.json file) defining types, constraints, or required fields for this structure.
While not critical for a template, a formal output schema would help integrators validate agent responses and catch breaking changes.
📋 Proposed addition: outputs.json schema
Consider adding templates/lostfound-match-agent/outputs.json:
{
"match_score": {
"type": "number",
"required": true,
"description": "Match confidence score between 0-100"
},
"decision": {
"type": "string",
"required": true,
"description": "Match decision category (e.g., Likely Match, Possible Match, No Match)"
},
"reason": {
"type": "string",
"required": true,
"description": "Human-readable explanation of the decision"
},
"matching_signals": {
"type": "array",
"required": true,
"description": "List of signals supporting the match"
},
"conflicting_signals": {
"type": "array",
"required": true,
"description": "List of signals contradicting the match"
},
"verification_questions": {
"type": "array",
"required": true,
"description": "Questions to verify ownership"
},
"next_action": {
"type": "string",
"required": true,
"description": "Recommended next step for the administrator"
}
}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@templates/lostfound-match-agent/meta.json` around lines 15 - 34, Add a formal
output schema file describing the agent's response contract to validate the
fields shown in output_example: create an outputs.json that defines each
top-level property (match_score, decision, reason, matching_signals,
conflicting_signals, verification_questions, next_action) with types,
required=true where appropriate, descriptions, and constraints (e.g.,
match_score numeric 0–100, arrays of strings for signals/questions). Ensure the
schema keys exactly match the example in meta.json so integrators can validate
agent responses and catch breaking changes.
2 participants
PR Checklist
1. Select Contribution Type
kits/<category>/<kit-name>/)bundles/<bundle-name>/)templates/<template-name>/)2. General Requirements
kebab-caseand matches the flow IDREADME.md(purpose, setup, usage)3. File Structure (Check what applies)
config.jsonpresent with valid metadata (name, description, tags, steps, author, env keys)flows/<flow-name>/(where applicable) include:config.json(Lamatic flow export)inputs.jsonmeta.jsonREADME.md.env.examplewith placeholder values only (kits only)config.jsonnode graphs (changes via Lamatic Studio export)4. Validation
npm install && npm run devworks locally (kits: UI runs; bundles/templates: flows are valid)Files Added
lost_item_description,found_item_description) and optional fields (lost_location,found_location,lost_date,found_date)Workflow Overview
The LostFound Match Agent is a lost-and-found item matching template that:
Target use cases: Campuses, airports, metro stations, malls, hotels, and other public institutions with lost-and-found operations.
Note: The actual workflow implementation (flow.json with node types and execution logic) is not included in the visible repository files—it exists in Lamatic Studio as indicated in the PR objectives.