Turn a meeting transcript into structured notes and one Linear ticket per action item. Assign owners from the discussion or the team’s ownership map, and flag unclear assignments in unassigned tickets for follow-up.
The per-meeting runbook for turning a finished call's transcript into structured notes and Linear tickets — the notes format, action-item phrasing, ownership routing from memory, and when to flag instead of guess.
Review the instructions the agent will receive before you install.
Pull the calendar event (title, attendees, agenda) via google_calendar. The
transcript itself is a Google Doc — Calendar events for recorded/transcribed
meetings carry it as an attachment link. Follow that link and read the doc's
content via google_drive (resolve the file from the attachment, then read
its contents). If the event has no transcript attachment, skip it — it hasn't
been transcribed yet. This is the entire input for the session — no other
meeting's context loads in.
Read the notes template, the phrasing convention for an action item, and the ownership map (who owns which area or project) from memory. Skim recent past meetings on the same topic for continuity — a decision this call revisits should reference the earlier one, not restate it as new.
Write the notes in the standard three-part shape:
| Section | Content |
|---|---|
| Decisions | What was agreed, stated as a fact ("Ship Friday"), not a discussion point |
| Discussion | The context and trade-offs behind each decision, condensed |
| Next steps | Every action item, phrased "[Owner] will [do X] by [when]" |
Attach the notes to the meeting record so they live where the team already looks for them.
| Signal | Routing |
|---|---|
| Owner named explicitly in the transcript ("Sarah will handle the migration") | Assign to that person |
| Owner implied by the ownership map (topic maps to a known area owner) | Assign to the mapped owner |
| No explicit owner and no confident map match | Do not guess — flag it (Step 6) |
Create one ticket per action item in {{linear_team}}: title is the action phrased as a task, description is the decision/discussion context plus a link back to the meeting record, assignee is the owner resolved in Step 4.
File any action item without a confident owner as an unassigned ticket in {{linear_team}}, with the ambiguity spelled out in the description ("raised by X, no clear owner — needs triage") instead of guessing an assignee.
Once the notes are attached and every action item is either filed-and-assigned or filed-and-flagged, the session is done. Don't touch any ticket that already existed before this meeting.
</workflow> <guardrails> - **Only create.** The agent never closes, reassigns, or edits a ticket that existed before this session — Linear writes are new tickets only. - **Flag instead of guess.** An action item without a confident owner is filed unassigned with the ambiguity noted, never routed to a person on a guess. - **One meeting, one session.** Nothing carries over between meetings; a call is scoped entirely to its own event and transcript. - **Scoped secrets.** Calendar, Drive, and Linear access is brokered through connectors; no raw credential reaches the model or a log. - **No chat posts.** The meeting record and Linear are the only outputs — this skill does not post to Slack, email, or any other channel. </guardrails> </skill>No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.