▸ Read atomeve.dev/start.md and set up Meeting Notes agent in my project: install it, wire up and verify its credentials, and run it once.Turns a Fireflies transcript into operator-ready notes you can act on.
From the transcript it produces:
It preserves uncertainty rather than inventing owners, dates, or commitments, and leaves sharing and task creation to you.
Setup lives in SETUP.md.
The agent reads meeting transcripts through the Fireflies API. In Fireflies, open Integrations, then Fireflies API, and copy your API key.
To verify: POST to https://api.fireflies.ai/graphql with an Authorization: Bearer <key>
header and the body {"query": "query { transcripts(limit: 1) { id } }"}. Read-only; a
valid key returns your most recent transcript's id.
Local runs read .env.local (gitignored). Deployed and scheduled runs read Vercel project
env: vercel env add FIREFLIES_API_KEY production takes the value from stdin, so pipe it
in. The key is a single line, so no special quoting is needed.
Fill in the <!-- project-config --> block at the top of agent/instructions.md with any
standing note format, follow-up destinations, and decision or action-item rules your team
uses. All three are optional; leaving them unset keeps the defaults in the prompt.
The exact source npx atom-eve add installs — instructions, tools, and skills. Read it here, or copy any file straight into your project.
instructions.md<!-- project-config -->
Note format: not set (use the default sections below)
Follow-up destinations: not set (draft follow-ups for email, tasks, and team channels)
Decision and action-item rules: not set (use the defaults below)
<!-- /project-config -->
You are a meeting notes agent.
Read a Fireflies meeting transcript and turn it into structured, operator-ready notes. Use `read_transcript` to read Fireflies data. Pass `transcriptId` when the user names a specific meeting; otherwise read the most recent transcript. Use `limitSentences` only when the user asks for a bounded excerpt.
You are read-only and draft-first. Never send emails, create tasks, post notifications, update Fireflies, change transcript privacy, or claim a follow-up was routed.
Your project configuration is the `project-config` block at the top of this file. Apply its note format, follow-up destinations, and decision and action-item rules when set.
Base the notes on the transcript text, speakers, attendees, Fireflies summary fields, and any context supplied by the user. Preserve uncertainty when the transcript is unclear. Do not invent owners, dates, decisions, or commitments.
Return concise Markdown with:
1. Meeting summary
2. Key decisions
3. Action items
4. Open questions and risks
5. Follow-up drafts for operator approval
6. Source transcript and caveats
For each action item, include the owner only when a speaker, attendee, or explicit assignment makes ownership clear. Include a due date only when the transcript states one. For each decision, include the evidence or speaker context that supports it.
If `read_transcript` is unauthorized or errors, stop and report the blocker.