find-in-circleback
Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword,…
Turn a meeting into work — read its Granola notes, extract the commitments that belong to this user, and carry each one out or draft it (a code change, a ticket, a reply) with a trace back to the note. Use when the user says "do the follow-ups from", "implement what we agreed",
Claude Code
$ npx -y skills add paradevai/paradev --skill follow-up-from-granola --agent claude-code
Codex
$ npx skills add paradevai/paradev --skill follow-up-from-granola -a codex -y
Cursor
$ npx skills add paradevai/paradev --skill follow-up-from-granola -a cursor -y
Gemini CLI
$ npx skills add paradevai/paradev --skill follow-up-from-granola -a gemini-cli -y
GitHub Copilot
$ npx skills add paradevai/paradev --skill follow-up-from-granola -a github-copilot -y
OpenCode
$ npx skills add paradevai/paradev --skill follow-up-from-granola -a opencode -y
Windsurf
$ npx skills add paradevai/paradev --skill follow-up-from-granola -a windsurf -y
name: follow-up-from-granola description: Turn a meeting into work — read its Granola notes, extract the commitments that belong to this user, and carry each one out or draft it (a code change, a ticket, a reply) with a trace back to the note. Use when the user says "do the follow-ups from", "implement what we agreed", "make tickets from", or points at a meeting after a sync, planning session, or customer call. argument-hint: the meeting (title, date, or ID) to act on, and optionally which kind of follow-up allowed-tools: mcp__granola__*
A meeting produces commitments, and most of them evaporate because nobody turned them into tasks. The job is to read the notes, find the commitments that are this user's to act on, and take each one as far as the workspace allows — without inventing work the meeting did not ask for.
Fetch the meeting with `get_meetings`. If the user gave a title or a date, find it with `list_meetings` first and confirm it is the right instance — a recurring meeting has many. Read the notes end to end: action items sit in a section, but commitments also hide in the discussion ("I'll take a look at that", "we should ship that first").
For each commitment record what, who owns it, by when, and the sentence in the notes it comes from. Keep only what the notes support. When ownership is unclear, check `get_meeting_transcript` for who actually said it; if it is still unclear, list it as unassigned rather than handing it to the user.
review, citing the meeting.
connected, with the note's wording and the meeting in the body.
they asked for exactly that.
them; do not act on it.
Ask before acting only when a commitment is ambiguous or expensive. A clear "fix the flaky test" in the notes does not need a second confirmation.
Finish with one line per commitment: what you did with it (changed, filed, drafted, skipped and why) and the meeting and line it came from. The user should be able to check every item against the notes.
items; verify each against the discussion before treating it as a commitment.
eventually" is not a commitment; a name and a timeframe are.
the user asked for their follow-ups.
gets re-litigated at the next one.
Paradev is an open-source Codex App and Conductor alternative. Orchestrate an army coding agents in parallel with your own subscriptions.
Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword,…
Build a brief for an upcoming meeting from Circleback — the calendar event, the history with the same people and company, open…
Work the action items Circleback captured — find what is assigned to this user, do the ones the workspace can do, and update…
Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and…
Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels,…
Answer "what did we say, decide, or promise" from Granola meeting notes — narrow to the meetings that can hold the answer, read…
Direct actions on one Orchestrator session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's…
Your capability catalog — read this at boot. Lists the temporal date-range skills and the external integrations (reached via the…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…