Skip to content

feat: Add meeting-preparation agent#166

Merged
akshatvirmani merged 50 commits into
Lamatic:mainfrom
TiyaJain28:main
Jun 7, 2026
Merged

feat: Add meeting-preparation agent#166
akshatvirmani merged 50 commits into
Lamatic:mainfrom
TiyaJain28:main

Conversation

@TiyaJain28

@TiyaJain28 TiyaJain28 commented May 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Added a Meeting Preparation Agent built with Lamatic.

Features

  • Generates company overview and research
  • Provides interview preparation guidance
  • Suggests technical interview questions
  • Suggests behavioral interview questions
  • Generates questions to ask the interviewer
  • Creates a quick preparation plan before meetings

Flow

Ask Trigger → Generate Text → Ask Response

Notes

  • Built using Lamatic Studio
  • Exported following AgentKit contribution guidelines
  • Includes prompts, model configurations, constitutions, and flow definitions
  • kits/meeting-preparation-agent/.gitignore — ignores .lamatic/, node_modules/, .env, .env.local
  • kits/meeting-preparation-agent/README.md — complete README describing the Meeting Preparation Agent: overview, prerequisites, setup, usage with example interview request, example outputs, license
  • kits/meeting-preparation-agent/agent.md — populated agent documentation: purpose, capabilities, inputs/outputs, flow overview, guardrails, integrations
  • kits/meeting-preparation-agent/lamatic.config.ts — kit metadata (type: "template", version 1.0.0), author, tags ["interview","career","job-preparation","ai-assistant"], single mandatory step, links object present (github/deploy fields in file; githubUrl empty in flow meta)
  • kits/meeting-preparation-agent/constitutions/default.md — default constitution: identity, safety refusal rules, anti-jailbreak, uncertainty/fabrication rules, PII/data-handling guidance, tone guidance
  • kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts — declarative flow defining meta, inputs, references (prompts, constitution, model-config), nodes, and edges
  • kits/meeting-preparation-agent/model-configs/meeting-preparation-agent_llmnode-300_generative-model-name.ts — LLM model config exporting generativeModelName using generator/text with model_name "gemini/gemini-2.5-flash" (configName: "configA")
  • kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.md — system prompt template instructing structured interview/meeting prep output (Company Overview, Preparation Tips, 5 technical questions, 5 behavioral questions, Questions to ask interviewer, 30-minute prep plan), tailoring guidance and presentation format
  • kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_user_1.md — user prompt template that injects user interview request ({{chat}}/interview details) to drive the generation

Flow (meeting-preparation-agent) — node types and behavior:

  • Nodes:
    • triggerNode (id: triggerNode_1, "Ask Trigger"): UI entry point for user input; includes suggestions, placeholders, policy link, UI options (copy button, feedback, color/branding).
    • dynamicNode (id: LLMNode_300, "Generate Text"): LLM execution node that loads system + user prompt templates, model config reference (generativeModelName -> model-config module), empty tools/memories/messages; produces generatedResponse.
    • responseNode (id: responseNode_triggerNode_1, "Ask Response"): maps LLMNode_300.generatedResponse into output content for display.
  • Edges/flow:
    • triggerNode_1 → LLMNode_300 (defaultEdge): user input flows into the LLM node for generation.
    • LLMNode_300 → responseNode_triggerNode_1 (defaultEdge): generatedResponse routed to response node.
    • triggerNode_1 → responseNode_triggerNode_1 (responseEdge): direct response-edge present for response mapping/flow control alongside LLM path.
  • High-level summary: The flow accepts a user interview/meeting request via the Ask Trigger UI, runs the Generate Text dynamic LLM node using provided system+user prompts and the configured generative model, and returns a structured meeting/interview preparation package (company overview, tailored prep tips, technical & behavioral questions, questions to ask interviewer, and a quick 30-minute prep plan) through the Ask Response node.

@coderabbitai

coderabbitai Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@TiyaJain28, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 991b6ef4-de4d-4c28-9c18-ff96941a2390

📥 Commits

Reviewing files that changed from the base of the PR and between a1d29d2 and ffc646c.

📒 Files selected for processing (7)
  • kits/meeting-preparation-agent/README.md
  • kits/meeting-preparation-agent/agent.md
  • kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts
  • kits/meeting-preparation-agent/lamatic.config.ts
  • kits/meeting-preparation-agent/model-configs/meeting-preparation-agent_llmnode-300_generative-model-name.ts
  • kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.md
  • kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_user_1.md

Walkthrough

This 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.

Changes

Meeting Preparation Agent Kit Initialization

Layer / File(s) Summary
Kit scaffolding and initialization
kits/meeting-preparation-agent/.gitignore, kits/meeting-preparation-agent/README.md, kits/meeting-preparation-agent/agent.md, kits/meeting-preparation-agent/lamatic.config.ts
Project scaffolding and kit metadata added: .gitignore ignores .lamatic/, node_modules/, .env/.env.local; README and agent docs populated with end-to-end documentation; kit config exported.
Agent constitution and behavioral guardrails
kits/meeting-preparation-agent/constitutions/default.md
Adds default constitution with identity, safety rules, uncertainty rule, data-handling constraints, and tone guidance.
Flow architecture and orchestration
kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts
Declarative flow exported with meta, inputs, references, nodes (Ask Trigger, Generate Text LLMNode_300, Ask Response), edges wiring trigger → LLM → response, and default export.
LLM model configuration
kits/meeting-preparation-agent/model-configs/meeting-preparation-agent_llmnode-300_generative-model-name.ts
Default-exported generative model configuration for LLMNode_300 specifying a generator/text entry with model/provider identifiers (gemini/gemini-2.5-flash, provider gemini).
System and user prompt templates
kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.md, kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_user_1.md
System prompt defines interview-package structure (company overview, tips, 5 technical + 5 behavioral questions, interviewer questions, 30-min plan); user prompt injects {{chat}} and requests a complete interview preparation guide.

Suggested reviewers

  • amanintech
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'feat: Add meeting-preparation agent' clearly and concisely summarizes the main change—adding a new meeting preparation agent to the repository.
Description check ✅ Passed The PR description covers the key aspects: summarizes the addition, lists core features, describes the flow architecture, and provides implementation notes. All essential information about the meeting preparation agent is present.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@TiyaJain28

Copy link
Copy Markdown
Contributor Author

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!

@TiyaJain28 TiyaJain28 closed this May 28, 2026
@TiyaJain28 TiyaJain28 reopened this May 28, 2026
@TiyaJain28 TiyaJain28 closed this May 28, 2026
@TiyaJain28 TiyaJain28 reopened this May 28, 2026
@akshatvirmani

Copy link
Copy Markdown
Contributor

/validate

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

📡 Running Studio validation — results will appear here shortly.

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Studio Runtime Validation (Phase 2)

Studio validation passed. The kit loaded successfully in Lamatic Studio.

This PR is ready for final review and merge.

@akshatvirmani

Copy link
Copy Markdown
Contributor

hello @TiyaJain28
can you remove the sticky notes from the flow please?
other than that looks good.

Removed multiple sticky note nodes from the meeting preparation agent flow.
@TiyaJain28

TiyaJain28 commented Jun 2, 2026 via email

Copy link
Copy Markdown
Contributor Author

@TiyaJain28

TiyaJain28 commented Jun 3, 2026 via email

Copy link
Copy Markdown
Contributor Author

@akshatvirmani

Copy link
Copy Markdown
Contributor

/validate

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

📡 Running Studio validation — results will appear here shortly.

@akshatvirmani

Copy link
Copy Markdown
Contributor

@TiyaJain28

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
@TiyaJain28

TiyaJain28 commented Jun 4, 2026 via email

Copy link
Copy Markdown
Contributor Author

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

♻️ Duplicate comments (1)
kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts (1)

11-13: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Mission: 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

📥 Commits

Reviewing files that changed from the base of the PR and between d8b1db3 and a1d29d2.

📒 Files selected for processing (8)
  • kits/meeting-preparation-agent/README.md
  • kits/meeting-preparation-agent/agent.md
  • kits/meeting-preparation-agent/constitutions/default.md
  • kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts
  • kits/meeting-preparation-agent/lamatic.config.ts
  • kits/meeting-preparation-agent/model-configs/meeting-preparation-agent_llmnode-300_generative-model-name.ts
  • kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.md
  • kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_user_1.md

Comment thread kits/meeting-preparation-agent/lamatic.config.ts Outdated
Comment thread kits/meeting-preparation-agent/lamatic.config.ts
Comment thread kits/meeting-preparation-agent/README.md
@akshatvirmani

Copy link
Copy Markdown
Contributor

Great!
Can you solve the other coderabbit comments as well? In three files changes are required @TiyaJain28

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.
@TiyaJain28

TiyaJain28 commented Jun 5, 2026 via email

Copy link
Copy Markdown
Contributor Author

@akshatvirmani

Copy link
Copy Markdown
Contributor

/validate

@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

📡 Running Studio validation — results will appear here shortly.

@akshatvirmani

Copy link
Copy Markdown
Contributor

@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

@TiyaJain28

Copy link
Copy Markdown
Contributor Author

Hi!
The flow file already had the nodes and edges exports. The earlier version on GitHub was missing them, but the latest version has both. I've also fixed a bug where the response node was referencing the wrong node ID (LLMNode_668 instead of LLMNode_300). All changes have been pushed. Please revalidate when you get a chance!

@akshatvirmani

Copy link
Copy Markdown
Contributor

/validate

@github-actions

github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

📡 Running Studio validation — results will appear here shortly.

@akshatvirmani akshatvirmani merged commit 5d15d95 into Lamatic:main Jun 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants