Skip to content
cccskills
FreePublished on GitHubEnglish overview

prep-with-circleback

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.

OriginalShow the original 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.

ParadevAI/Paradev15,724 stars(GitHub 15,724 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Preparing for an upcoming customer call
  • Checking attendees and their roles
  • Reviewing open commitments on both sides
  • Identifying unresolved questions before a partner meeting

Overview

What it does

This skill creates a short pre-meeting brief from Circleback calendar events, past meetings, open tasks, and emails. It lists attendees and their roles, recent decisions and dates, outstanding actions for both you and the other party, and questions that remain unresolved. Each item links to the supporting meeting, event, or email thread.

When it helps

Use it before a customer or partner meeting when you need to understand the current status and know what to confirm. It reviews the latest two or three meetings with the same people or company, and may also consult the first meeting for a long-running relationship. The brief focuses on open issues and fits roughly on one screen instead of recounting every past discussion.

Example requests

  • “Summarize what I should know for today’s customer meeting.”
  • “Separate the outstanding tasks for us and for the other company.”
  • “List the unresolved questions to raise at the next partner meeting.”

Notes

The skill uses tools to search Circleback events, meetings, tasks, and email. If no date range is given, calendar search covers today and tomorrow. Roles come from profiles or records; unknown roles are marked as unknown. Generated insights are not presented as confirmed facts. For recurring meetings, confirm the event date before reviewing history.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

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).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt searches Circleback records and specifies how to label unknown roles and generated insights.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingCircleback search tools are required, but connection setup is not described.

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.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Brief before the meeting

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.

1. Anchor on the event

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.

2. Pull the history with these people

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.

3. Find the open loops on both sides

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.

4. Write the brief in that order

  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.

Anti-patterns

  • Summarizing every past meeting. The brief is about what is open, not a history lesson.
  • Guessing roles from titles. Take names and roles from the profile and the notes; say "unknown" otherwise.
  • Presenting insights as facts. Generated insights get a "Circleback suggests" label or get left out.
  • Prepping for the wrong meeting. A recurring series has one event per week; confirm the date before pulling history.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

10x

FreeSummary

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.

  • Find unused Superset features worth exploring
  • Set up scheduled agent tasks
  • Start parallel work in separate workspaces
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

automate

FreeSummary

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.

  • Scheduling a daily or weekly agent task
  • Starting agent work when a GitHub pull request opens
  • Triggering tasks from selected Slack reactions
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

browser

FreeSummary

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.

  • Preview a locally running web app
  • Capture screenshots of a page
  • Inspect console errors
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

build-a-stripe-integration

FreeSummary

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.

  • Choose Stripe products for payments or recurring billing
  • Implement Checkout or invoice flows
  • Investigate Stripe code that compiles but behaves incorrectly
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

cdp-verification

FreeSummary

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.

  • Reproducing a UI bug in the running app
  • Verifying a UI change end to end
  • Checking behavior after a route or workspace switch
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

ci-triage

FreeSummary

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.

  • Investigating failed PR checks
  • Separating intermittent test failures from code defects
  • Checking whether the base branch already fails
ParadevAI/Paradev15.7KUpdated Oct 29, 2026

See all skills by ParadevAI

Report a problem with this skill