feat: Add meeting-preparation agent#166
Open
TiyaJain28 wants to merge 37 commits into
Open
Conversation
Contributor
|
Warning Review limit reached
More reviews will be available in 5 minutes and 33 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 (8)
WalkthroughThis PR adds a new meeting-preparation-agent kit: project scaffolding, a default constitution, kit config, a declarative flow (Ask Trigger → Generate Text LLM → Ask Response), Gemini model config, and system/user prompt templates for interview preparation. ChangesMeeting Preparation Agent Kit Initialization
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
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! |
Contributor
|
/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. |
Contributor
|
hello @TiyaJain28 |
Removed multiple sticky note nodes from the meeting preparation agent flow.
Author
|
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:
***@***.***>
|
|
Failure recorded at 2026-06-03T07:12:43Z UTC. If this PR is not fixed within 4 weeks it will be automatically closed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 8
🤖 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/constitutions/c.txt`:
- Line 1: Remove the orphan empty constitution file c.txt because it’s unused
(the flow uses `@constitutions/default.md`); either delete c.txt to avoid
dead-artifact drift or, if it was intentional, add an explicit reference to it
from the flow contract (e.g., in `@constitutions/default.md`) so its presence is
deliberate and tracked.
In `@kits/meeting-preparation-agent/constitutions/default.md`:
- Around line 3-17: Insert a blank line immediately after each top-level heading
to satisfy MD022: add an empty line after "## Identity", after "## Safety",
after "## Data Handling", and after "## Tone" in the default constitution
content so each heading is followed by a single blank line before its bullet or
paragraph content.
In `@kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts`:
- Line 127: The flow references a non-existent LLM node ID
LLMNode_668.generatedResponse; update the reference to the actual node defined
in this flow (LLMNode_300.generatedResponse) so the response resolves
correctly—search for occurrences of "LLMNode_668.generatedResponse" and replace
them with "LLMNode_300.generatedResponse" (ensure any related wiring or metadata
that expects LLMNode_668 is also updated to LLMNode_300).
In
`@kits/meeting-preparation-agent/model-configs/meeting-preparation-agent_llmnode-300_generative-model-name.ts`:
- Around line 10-12: The config hardcodes provider credentials (credentialId,
provider_name, credential_name) which prevents portability; replace the concrete
binding in meeting-preparation-agent_llmnode-300_generative-model-name.ts by
removing or replacing the credentialId and credential_name values with an
unbound/default model selection object (e.g., a placeholder or null/undefined
entries) and keep only provider_name or a generic selector so users pick their
Lamatic credentials in their workspace; update any references to the
credentialId/credential_name in the file to handle the unbound case (e.g.,
fallbacks in the model selection logic) so imports don’t rely on internal
identifiers.
In
`@kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_system_0.md`:
- Around line 1-10: Add a top-level heading at the very start of the file (e.g.,
prefix the existing text "Use the following interview request:" with a Markdown
H1) to satisfy MD041/MD047, and ensure the file ends with exactly one trailing
newline character (no extra blank lines) after the last line of content; update
the prompt text that currently begins with "Use the following interview
request:" so it sits under the new H1 and verify there is a single final
newline.
- Around line 1-4: The system prompt in
meeting-preparation-agent_llmnode-300_system_0.md currently hardcodes "Company:
Google" and "Role: Backend Developer Intern"; change it to a generic template
that consumes user-provided company/role instead of fixed values—replace the
hardcoded lines with placeholders like "Company: {{company}}" and "Role:
{{role}}" (or instruct "Use the following interview request provided by the
user") and ensure the prompt text directs the agent to read company/role from
the incoming user prompt rather than assuming Google/Backend Developer Intern.
In
`@kits/meeting-preparation-agent/prompts/meeting-preparation-agent_llmnode-300_user_1.md`:
- Line 2: Replace the incorrect prompt variable {{interview_request}} with the
trigger-scoped field the flow expects, {{chat}}, so the runtime injects the user
request; update the template in meeting-preparation-agent_llmnode-300_user_1.md
to reference {{chat}} wherever {{interview_request}} appears and verify the
prompt consumers (the flow that reads the trigger field named chat) still
receive the user input.
In `@kits/meeting-preparation-agent/README.md`:
- Around line 3-4: Replace the TODO placeholders in
kits/meeting-preparation-agent/README.md with a runnable README: add a
one-paragraph description of the Meeting Preparation AgentKit, a "Prerequisites"
section listing required tools (Node/Python version, package manager, CLI), a
"Setup" section with concrete install and build commands to run (e.g., how to
install dependencies and start the dev server), an "Environment variables"
section listing required keys and example values (e.g., OPENAI_API_KEY, any DB
or vectorstore config) and how to store them (.env), and a "Usage / Examples"
section showing exact commands to run common flows (start, run tests, example
request payloads or curl commands). Ensure the README mentions any kit-specific
entry points (e.g., scripts like start, dev, or functions such as prepareMeeting
or MeetingPreparationAgent if present) so contributors can run the kit without
reverse-engineering it.
🪄 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: a6981fd6-17ec-4748-ba7b-bd0fe170d817
📒 Files selected for processing (13)
kits/meeting-preparation-agent/.gitignorekits/meeting-preparation-agent/README.mdkits/meeting-preparation-agent/agent.mdkits/meeting-preparation-agent/constitutions/c.txtkits/meeting-preparation-agent/constitutions/default.mdkits/meeting-preparation-agent/flows/f.txtkits/meeting-preparation-agent/flows/meeting-preparation-agent.tskits/meeting-preparation-agent/lamatic.config.tskits/meeting-preparation-agent/model-configs/m.txtkits/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.mdkits/meeting-preparation-agent/prompts/p.txt
Contributor
|
@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.) Once those are fixed, push the changes and I'll re-validate. |
|
Hi @TiyaJain28! 👋 Before this PR can be reviewed by maintainers, please resolve all comments and requested changes from the CodeRabbit automated review. Steps to follow:
This helps keep the review process efficient for everyone. Thank you! 🙏 |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
kits/meeting-preparation-agent/lamatic.config.ts (2)
10-10:⚠️ Potential issue | 🟠 Major | ⚡ Quick winYour tags array is empty, agent. Without proper classification, your mission will go unnoticed.
The
tagsfield is currently an empty array, which limits kit discoverability and fails to classify your agent's capabilities. The reviewer has explicitly requested that tags be added to improve searchability and categorization.Based on your agent's mission profile (interview preparation, company research, meeting prep), populate this field with relevant tags.
🏷️ Suggested tags based on your agent's capabilities
- "tags": [], + "tags": ["interview", "meeting", "preparation", "career", "research", "ai"],🤖 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/lamatic.config.ts` at line 10, Populate the "tags" array in the lamatic config by adding relevant, discoverable keywords reflecting the agent's mission (e.g., meeting-prep, interview-prep, company-research, agenda-creation, note-taking, role-play, mock-interview) so the agent is properly categorized; update the "tags" field (the tags property in the config object) to include these strings as elements of the array.
11-16:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMission briefing: fix missing envKey + empty metadata in
kits/meeting-preparation-agent/lamatic.config.tsAgent, the mandatory step (
id: "meeting-preparation-agent") is missing theenvKeymapping to the deployed flow ID. Other kits’mandatorysteps includeenvKey, so this kit needs the correct one for the flow it should execute.Also fill
description,tags, andlinks.deploy/links.github(they’re currently empty placeholders).🤖 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/lamatic.config.ts` around lines 11 - 16, Update the mandatory step object with the correct envKey and populate metadata: add an envKey field on the step with a descriptive env var name that maps to the deployed flow ID (e.g., MEETING_PREPARATION_AGENT_FLOW_ID) so the step "meeting-preparation-agent" can resolve the flow at runtime; also replace the empty placeholders in the top-level metadata by providing a meaningful description for the kit (the description string), a small array of tags (e.g., ["meeting","agent","productivity"]), and fully-qualified URLs for links.deploy and links.github so links.deploy points to the deployed flow/dashboard and links.github points to the repo location. Ensure the fields are updated in lamatic.config.ts for the existing "meeting-preparation-agent" step and the file-level metadata keys description, tags, links.deploy, and links.github.
🤖 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`:
- Line 3: Replace the empty "description" value in lamatic.config.ts with a
concise mission summary that explains this meeting-preparation agent generates
company overviews, tailored interview questions, role-specific preparation
plans, and suggested talking points to help users prep for interviews and
meetings; update the "description" field to a one- or two-sentence string that
mentions those capabilities (company overviews, interview questions, preparation
plans) so kit discovery and users understand what the agent does.
---
Outside diff comments:
In `@kits/meeting-preparation-agent/lamatic.config.ts`:
- Line 10: Populate the "tags" array in the lamatic config by adding relevant,
discoverable keywords reflecting the agent's mission (e.g., meeting-prep,
interview-prep, company-research, agenda-creation, note-taking, role-play,
mock-interview) so the agent is properly categorized; update the "tags" field
(the tags property in the config object) to include these strings as elements of
the array.
- Around line 11-16: Update the mandatory step object with the correct envKey
and populate metadata: add an envKey field on the step with a descriptive env
var name that maps to the deployed flow ID (e.g.,
MEETING_PREPARATION_AGENT_FLOW_ID) so the step "meeting-preparation-agent" can
resolve the flow at runtime; also replace the empty placeholders in the
top-level metadata by providing a meaningful description for the kit (the
description string), a small array of tags (e.g.,
["meeting","agent","productivity"]), and fully-qualified URLs for links.deploy
and links.github so links.deploy points to the deployed flow/dashboard and
links.github points to the repo location. Ensure the fields are updated in
lamatic.config.ts for the existing "meeting-preparation-agent" step and the
file-level metadata keys description, tags, links.deploy, and links.github.
🪄 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: c5e6d933-8bdd-49f0-a0b8-9ff8bf8f3889
📒 Files selected for processing (1)
kits/meeting-preparation-agent/lamatic.config.ts
Added detailed overview, prerequisites, setup instructions, and usage examples for the Meeting Preparation Agent.
Added detailed documentation for the Meeting Preparation Agent, including its purpose, capabilities, input, output, flow overview, guardrails, and integrations.
Removed unnecessary blank lines in the default constitution.
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts (2)
63-70: 🧹 Nitpick | 🔵 Trivial | ⚡ Quick winCover identity blown: trigger suggestions belong to a different operative.
These starter prompts ("How do I use the VectorDB feature?", etc.) are generic Lamatic onboarding chatter — they don't match a meeting/interview-preparation agent and will confuse end users on first contact. Retarget them to the agent's actual mission (e.g., "Prep me for a software engineer interview at Acme Corp"). Adjust in Lamatic Studio and re-export.
🤖 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 63 - 70, The "suggestions" array in meeting-preparation-agent.ts contains generic Lamatic onboarding prompts that don't match this agent's purpose; update the "suggestions" entries to meeting/interview preparation prompts (e.g., "Prep me for a software engineer interview at Acme Corp", "Help me practice behavioral interview questions for Product Manager", "Give me a 30-minute prep plan for a technical onsite", "Create tailored study topics based on a job description", "Draft answers to common interview questions for role X", "Simulate a mock interviewer for role Y") and then re-export the agent from Lamatic Studio so the updated starter prompts replace the current onboarding text.
6-7:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winYour mission: arm the
metaobject with intel before extraction.The
descriptionis blank andtagsis empty — exactly the gap mission control (akshatvirmani) flagged for merge. Populate both so this agent doesn't go dark in the kit registry. Per the Lamatic export protocol, set these in Lamatic Studio and re-export rather than hand-editing.🕵️ Target payload
- "description": "", - "tags": [], + "description": "Meeting Preparation Agent — generates company research, interview prep guidance, technical and behavioral questions, questions for the interviewer, and a quick pre-meeting prep plan.", + "tags": ["meeting-preparation", "interview", "research", "productivity"],🤖 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 6 - 7, The meta object in meeting-preparation-agent is missing human-friendly metadata: populate meta.description with a concise summary of the agent’s purpose and meta.tags with relevant keywords (e.g., "meeting-prep", "agenda", "summary", "action-items") inside Lamatic Studio and re-export the kit so the changes follow the Lamatic export protocol rather than hand-editing the file; locate the meta object in the MeetingPreparationAgent export (meta.description and meta.tags) and update them via the Studio UI, then re-run the export to commit the updated payload.
🤖 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.
Outside diff comments:
In `@kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts`:
- Around line 63-70: The "suggestions" array in meeting-preparation-agent.ts
contains generic Lamatic onboarding prompts that don't match this agent's
purpose; update the "suggestions" entries to meeting/interview preparation
prompts (e.g., "Prep me for a software engineer interview at Acme Corp", "Help
me practice behavioral interview questions for Product Manager", "Give me a
30-minute prep plan for a technical onsite", "Create tailored study topics based
on a job description", "Draft answers to common interview questions for role X",
"Simulate a mock interviewer for role Y") and then re-export the agent from
Lamatic Studio so the updated starter prompts replace the current onboarding
text.
- Around line 6-7: The meta object in meeting-preparation-agent is missing
human-friendly metadata: populate meta.description with a concise summary of the
agent’s purpose and meta.tags with relevant keywords (e.g., "meeting-prep",
"agenda", "summary", "action-items") inside Lamatic Studio and re-export the kit
so the changes follow the Lamatic export protocol rather than hand-editing the
file; locate the meta object in the MeetingPreparationAgent export
(meta.description and meta.tags) and update them via the Studio UI, then re-run
the export to commit the updated payload.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 46cced16-9e21-4919-9150-22ef4365a658
📒 Files selected for processing (1)
kits/meeting-preparation-agent/flows/meeting-preparation-agent.ts
Updated the interview preparation guide structure and added guidelines for generating content.
Replaced placeholder '{{interview_request}}' with '{{chat}}' in the interview preparation guide.
Added sections on safety, data handling, and tone to the default constitution.
Removed credentialId and credential_name from the model configuration.
Updated the description to provide a detailed overview of the AI-powered meeting preparation assistant's features.
Replaced existing suggestions with interview preparation topics.
Author
|
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:
***@***.***>
|
Contributor
|
/validate |
|
📡 Running Studio validation — results will appear here shortly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added a Meeting Preparation Agent built with Lamatic.
Features
Flow
Ask Trigger → Generate Text → Ask Response
Notes
Flow: meeting-preparation-agent (high level)