feat: Add meeting-preparation agent#166
Conversation
|
Warning Review limit reached
More reviews will be available in 12 minutes and 37 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (7)
WalkthroughThis PR adds a new meeting-preparation-agent kit: project scaffolding and gitignore, full README and agent docs, a default constitution, kit config, a declarative flow (Ask Trigger → Generate Text LLMNode_300 → Ask Response), Gemini model config, and system/user prompt templates for interview preparation. ChangesMeeting Preparation Agent Kit Initialization
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)
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 |
|
I've updated the contribution structure and re-uploaded the exported Lamatic files. The Meeting Preparation Agent includes prompts, model configurations, constitutions, and flow definitions generated from Lamatic Studio. Please let me know if any further changes are needed. Thank you for reviewing! |
|
/validate |
|
📡 Running Studio validation — results will appear here shortly. |
Studio Runtime Validation (Phase 2)✅ Studio validation passed. The kit loaded successfully in Lamatic Studio. This PR is ready for final review and merge. |
|
hello @TiyaJain28 |
Removed multiple sticky note nodes from the meeting preparation agent flow.
|
Hi @akshatvirmani,
Done. I removed the unsupported sticky note nodes from the flow and pushed
the changes. Thanks for pointing that out.
Please let me know if there's anything else that needs to be updated.
…On Tue, 2 Jun 2026 at 22:35, Akshat Virmani ***@***.***> wrote:
*akshatvirmani* left a comment (Lamatic/AgentKit#166)
<#166 (comment)>
hello @TiyaJain28 <https://github.com/TiyaJain28>
can you remove the sticky notes from the flow please?
other than that looks good.
—
Reply to this email directly, view it on GitHub
<#166?email_source=notifications&email_token=BTHJMMM64LI2OS42RPL3CET454COFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRQGQ4DMNRYHA2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4604866884>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BTHJMMIWGXFBMWVJDFTXCCD454COFAVCNFSM6AAAAACZQZVYRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMBUHA3DMOBYGQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BTHJMMPT5Y54WRBQDOQUOED454COFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRQGQ4DMNRYHA2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/BTHJMMPEZP7HBIHNUXWM4UD454COFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRQGQ4DMNRYHA2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi @akshatvirmani,
I've addressed the review comments and pushed the latest changes:
-
Updated lamatic.config.ts to use type: "template"
-
Added descriptions and relevant tags
-
Replaced all TODO placeholders in README.md and agent.md
-
Removed placeholder files (c.txt, f.txt, m.txt, p.txt)
-
Fixed the response node reference to LLMNode_300.generatedResponse
-
Updated prompts to be dynamic and role/company driven
-
Removed workspace-specific credential bindings from the model
configuration
-
Fixed markdown lint issues
-
Updated starter suggestions to match the interview-preparation use case
The latest changes have been pushed. Please re-validate when you get a
chance.
Thank you!
…On Wed, 3 Jun 2026 at 12:56, Akshat Virmani ***@***.***> wrote:
*akshatvirmani* left a comment (Lamatic/AgentKit#166)
<#166 (comment)>
@TiyaJain28 <https://github.com/TiyaJain28> can you check the above
comments by coderabbit and github action?
A few things to fix before we can merge:
Make sure lamatic.config.ts has type: "template". ( The PR looks like a
template not a kit since there's no apps/ directory.)
Replace the TODO placeholders in README.md and agent.md with actual
content.
Delete the placeholder files c.txt, f.txt, m.txt, p.txt
Add a description and tags in the flow's meta object
Once those are fixed, push the changes and I'll re-validate.
—
Reply to this email directly, view it on GitHub
<#166?email_source=notifications&email_token=BTHJMMNPXE3SSLN5ZVFB753457HJPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRGAYDGMZRGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4610033108>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BTHJMMORXIZU4ODUMHBYNAD457HJPAVCNFSM6AAAAACZQZVYRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMJQGAZTGMJQHA>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BTHJMMIXPD2BKPNHL553A43457HJPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRGAYDGMZRGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/BTHJMMOYHTNBCKV2W7DZUU3457HJPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRRGAYDGMZRGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
/validate |
|
📡 Running Studio validation — results will appear here shortly. |
|
Can you update the github link and deployed link(if any) in kits/meeting-preparation-agent/lamatic.config.ts? |
Updated GitHub link in lamatic.config.ts
|
Done.
…On Thu, 4 Jun 2026 at 17:53, Akshat Virmani ***@***.***> wrote:
*akshatvirmani* left a comment (Lamatic/AgentKit#166)
<#166 (comment)>
@TiyaJain28 <https://github.com/TiyaJain28>
Can you update the github link and deployed link(if any) in
kits/meeting-preparation-agent/lamatic.config.ts?
—
Reply to this email directly, view it on GitHub
<#166?email_source=notifications&email_token=BTHJMMMZ4C5GHAPOJ6GLJW346FS4JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGIYDQNZTGY42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4622087369>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BTHJMMPJEL7LWR77X2POUM346FS4JAVCNFSM6AAAAACZQZVYRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMRSGA4DOMZWHE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BTHJMMMTQHRQ5YNDQO3JV4D46FS4JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGIYDQNZTGY42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/BTHJMMMBW2JXC3TQVHLV3G346FS4JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGIYDQNZTGY42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Actionable comments posted: 4
♻️ Duplicate comments (1)
kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts (1)
11-13:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMission: Fill required kit metadata links before deployment.
Line 11, Line 12, and Line 13 are still empty, which leaves the kit metadata incomplete and misses previously requested PR updates.
Suggested patch
- "githubUrl": "", - "documentationUrl": "", - "deployUrl": "", + "githubUrl": "https://github.com/Lamatic/AgentKit/tree/main/kits/meeting-preparation-agent", + "documentationUrl": "https://github.com/Lamatic/AgentKit/blob/main/kits/meeting-preparation-agent/README.md", + "deployUrl": "<your-deployed-kit-url>",🤖 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 `@kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts` around lines 11 - 13, The kit metadata object currently has empty fields "githubUrl", "documentationUrl", and "deployUrl"; update these keys in meeting-preparation-agent.ts to non-empty, accurate links (real repo URL for githubUrl, user-facing docs page for documentationUrl, and deployment/demo URL for deployUrl) or provide sensible placeholder URLs if the real links aren’t available yet, then commit the change so the kit metadata is complete before deployment.
🤖 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 `@kits/meeting-preparation-agent/lamatic.config.ts`:
- Around line 23-25: The links.github value in lamatic.config.ts currently
points to an external repo; update the "links.github" string for the kit to
reference the AgentKit path for this kit (i.e., the repository path pointing to
kits/meeting-preparation-agent) by replacing the existing URL with the AgentKit
tree URL for this kit, for example
"https://github.com/<ORG>/AgentKit/tree/main/kits/meeting-preparation-agent"
(substitute the correct org/name).
- Around line 10-17: The config has a syntax error: the closing of the "tags"
array is not followed by a comma before the next property "steps", causing the
TypeScript file to be invalid; fix it by inserting a comma after the closing
bracket of the "tags" array so the object properly separates properties (update
the lamatic.config.ts object where "tags" and "steps" are defined).
In
`@kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.md`:
- Around line 1-2: The Markdown heading "# Interview Preparation Assistant" is
missing a blank line before the following paragraph ("You are an expert
interview preparation assistant."), triggering the MD022 lint rule; insert a
single blank line between the heading and that body text so the file
(meeting-preparation-agent_llmnode-300_system_0.md) has the heading on its own
line followed by an empty line and then the paragraph.
In `@kits/meeting-preparation-agent/README.md`:
- Around line 16-39: Add an explicit "Environment variables" section to
README.md (below the existing "Setup" heading) listing each required variable
name, its purpose, and an example value; include at minimum variables for
Lamatic workspace/auth (e.g., LAMATIC_WORKSPACE or LAMATIC_API_KEY), model
selection/credentials (e.g., MODEL_NAME, MODEL_API_KEY or OPENAI_API_KEY), and
any deployment flags (e.g., FLOW_ID or DEPLOY_ENV), and show one-line export
examples and required scopes/permissions; ensure the section references how
these tie into the existing "Setup" and "Usage" instructions so users can see
where to place credentials and example values for local vs production
deployments.
---
Duplicate comments:
In `@kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts`:
- Around line 11-13: The kit metadata object currently has empty fields
"githubUrl", "documentationUrl", and "deployUrl"; update these keys in
meeting-preparation-agent.ts to non-empty, accurate links (real repo URL for
githubUrl, user-facing docs page for documentationUrl, and deployment/demo URL
for deployUrl) or provide sensible placeholder URLs if the real links aren’t
available yet, then commit the change so the kit metadata is complete before
deployment.
🪄 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: 80cf2794-40bb-452b-8ab6-f772a9195553
📒 Files selected for processing (8)
kits/meeting-preparation-agent/README.mdkits/meeting-preparation-agent/agent.mdkits/meeting-preparation-agent/constitutions/default.mdkits/meeting-preparation-agent/flows/meeting-preparation-agent.tskits/meeting-preparation-agent/lamatic.config.tskits/meeting-preparation-agent/model-configs/meeting-preparation-agent_llmnode-300_generative-model-name.tskits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.mdkits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_user_1.md
|
Great! |
Updated README.md to enhance formatting and clarity of sections, including prerequisites, setup instructions, environment variables, and example output.
Updated URLs for GitHub, documentation, and deployment in the meeting preparation agent configuration. Removed unused node and edge definitions.
|
Fixed!
…On Thu, 4 Jun 2026 at 18:14, Akshat Virmani ***@***.***> wrote:
*akshatvirmani* left a comment (Lamatic/AgentKit#166)
<#166 (comment)>
Great!
Can you solve the other coderabbit comments as well? In three files
changes are required @TiyaJain28 <https://github.com/TiyaJain28>
—
Reply to this email directly, view it on GitHub
<#166?email_source=notifications&email_token=BTHJMMK4JS5JWA574HNQQ2D46FVLFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGIZDKMRRGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4622252121>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BTHJMMJ23FPYUPD5QXAIR2D46FVLFAVCNFSM6AAAAACZQZVYRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMRSGI2TEMJSGE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BTHJMMJPERTHVELTXIKR6AT46FVLFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGIZDKMRRGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y>
and Android
<https://github.com/notifications/mobile/android/BTHJMMMXSV3CSKBWAVMIISL46FVLFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGIZDKMRRGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
/validate |
|
📡 Running Studio validation — results will appear here shortly. |
|
@TiyaJain28 the phase 2 of our testing is failing for the PR. Your flow file flows/debugpilot-flow.ts is missing the nodes and edges exports, these come from the Lamatic Studio export and contain the actual flow graph. Please open your flow in Lamatic Studio, click the three-dot menu → Export(from inside the flow), and replace your current flow file with the exported .ts file. That would work |
Updated the Meeting Preparation Agent documentation to clarify capabilities, input/output details, and flow overview.
Removed duplicate sections and added a new Technology section.
|
Hi! |
|
/validate |
|
📡 Running Studio validation — results will appear here shortly. |
Summary
Added a Meeting Preparation Agent built with Lamatic.
Features
Flow
Ask Trigger → Generate Text → Ask Response
Notes
Flow (meeting-preparation-agent) — node types and behavior: