Find statements, decisions, and commitments in Circleback meeting records. Search by people, company, tags, or dates, then use notes and transcripts to distinguish discussion from agreement and identify the meeting behind each answer.
Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword, read the notes before the transcript, and cite the meeting behind every claim. Use when the user asks what happened on a call, what a customer or teammate said, what was agreed, or refers to a meeting, sync, demo, or interview.
Run score Not tested
See how to installSearches Circleback meeting records to find what people said, decided, or promised. It can narrow meetings by attendees, company, tags, or dates, and reads meeting notes before consulting transcripts. When exact wording or numbers matter, it checks the transcript. Answers identify the meeting and date; for commitments or deadlines, they also name the speaker.
Use it to check what was agreed in a sales conversation, find who committed to a deadline, or trace how a topic came up in recurring meetings. It distinguishes discussion, recorded follow-ups, and explicit agreement. If meeting records conflict, it reports the differences instead of silently choosing one account.
The Circleback search and reading tools are required, and answers rely on records they can retrieve. AI-generated insights are not treated as definitive meeting records. If a meeting was not recorded, the skill can only check the calendar for a scheduled event. If it finds no matching record, it reports the search filters used.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Circleback keeps notes, action items, insights, and a transcript for every captured meeting. The job is to find the right meeting, read what it records, and separate what was decided from what was discussed.
SearchMeetings matches keywords against titles and notes, and titles rarely
contain the topic. Resolve people with FindProfiles and companies with
FindCompanies, then search with profiles or domains and the date range
the user gave you. Do not invent a date range to narrow results — if the user
said "recently", say which window you used. Tags (ListTags) find a recurring
series. Keep the intent argument honest: it is the user's question, and it
shapes which excerpts the tool returns.
ReadMeetings (up to 50 IDs at once) returns notes, attendees, action items,
and insights — enough for "what was decided". Use SearchTranscripts to find
where a phrase was said across meetings, and GetTranscriptsForMeetings when
the exact words matter: a commitment, a number, a quote the user wants
verbatim. Quote the line; never present a paraphrase as a quote.
An "agreed" line is a decision. An action item is a recorded follow-up, not proof that anyone agreed to what it follows from; call it a decision only when the notes or transcript show the agreement. A topic in the notes with no owner and no outcome was discussed, not decided; say so. Two meetings that disagree are a finding to report, not something to reconcile silently — the later one is not automatically right.
Every claim names the meeting and its date. For anything the user may act on
— a promise to a customer, a deadline — also say who said it. When nothing
matches, state the filters you searched (people, domain, dates, tags) so an
empty answer can be checked. A meeting that was never captured leaves only a
calendar event, which SearchCalendarEvents can confirm.
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 how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify a UI change or reproduce a bug in the running desktop app using the Chrome DevTools Protocol (CDP), a browser debugging interface. Follow the real user journey and compare screenshots with measurements such as route, scroll position, and persisted state.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.