find-in-circleback
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 commitments on both sides, and what is still unresolved. Use when the user asks to prep for a call, "what do I need to know before", who someone is, or
Claude Code
$ npx -y skills add paradevai/paradev --skill prep-with-circleback --agent claude-code
Codex
$ npx skills add paradevai/paradev --skill prep-with-circleback -a codex -y
Cursor
$ npx skills add paradevai/paradev --skill prep-with-circleback -a cursor -y
Gemini CLI
$ npx skills add paradevai/paradev --skill prep-with-circleback -a gemini-cli -y
GitHub Copilot
$ npx skills add paradevai/paradev --skill prep-with-circleback -a github-copilot -y
OpenCode
$ npx skills add paradevai/paradev --skill prep-with-circleback -a opencode -y
Windsurf
$ npx skills add paradevai/paradev --skill prep-with-circleback -a windsurf -y
name: prep-with-circleback description: Build a brief for an upcoming meeting from Circleback — the calendar event, the history with the same people and company, open commitments on both sides, and what is still unresolved. Use when the user asks to prep for a call, "what do I need to know before", who someone is, or where things stand with a customer or partner. argument-hint: the meeting, person, or company to prepare for allowed-tools: mcp__circleback__SearchCalendarEvents, mcp__circleback__SearchMeetings, mcp__circleback__ReadMeetings, mcp__circleback__FindProfiles, mcp__circleback__FindCompanies, mcp__circleback__SearchActionItems, mcp__circleback__SearchEmails
A good brief is short, and every line in it comes from a source the user can open. The job is to reconstruct where things stand with these people from what Circleback captured, and to lead with what is unresolved.
`SearchCalendarEvents` for the window the user means (default: today and tomorrow). Take the attendees and organizer from the event — that is the guest list, not your guess. If the user named a person or company instead, resolve them with `FindProfiles` or `FindCompanies` and skip the calendar.
`SearchMeetings` filtered by one key attendee's profile or the company domain (a profiles filter matches only meetings every listed profile attended); sort the results by date yourself. Read the last two or three with `ReadMeetings`. For a long relationship read the most recent and the first: the first records what they wanted, the most recent records what they got.
The meetings you just read already carry their action items, each with a status and an assignee. Take the open ones from there first, yours and theirs. Reach for `SearchActionItems` (status PENDING, by assignee profile) only for what those meetings cannot show: a standalone item, or one from a call you did not read. An open item from the last call is the first thing the other side will ask about. `SearchEmails` fills the gap between meetings when a thread continued in writing.
1. Who is coming and their role, one line each. 2. Where things stand: the last decision and the date it was made. 3. Open on our side, open on theirs, with the meeting each came from. 4. Unresolved questions the user should be ready for.
Keep it to a screen. Every line links to the meeting, event, or email thread it came from.
history lesson.
the notes; say "unknown" otherwise.
suggests" label or get left out.
week; confirm the date before pulling history.
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,…
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…
Turn a meeting into work — read its Granola notes, extract the commitments that belong to this user, and carry each one out or…
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…