Prepare a short meeting brief from Circleback calendar events, past meetings, action items, and emails. Summarize attendees, recent decisions, outstanding commitments on both sides, and unresolved questions, with links to the supporting sources.
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.
Review the instructions the agent will receive before you install.
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 the attendees' profiles or the company domain,
newest first. 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.
Keep it to a screen. Every line links to the meeting, event, or email thread it came from.
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 desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.
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.