Skip to content
cccskills
FreePublished on GitHub

work-circleback-action-items

Work through your assigned tasks from Circleback meetings, using meeting notes to clarify each request. Make code changes, create tickets, or draft replies, then update task status only when the underlying work is actually finished.

OriginalShow the original description

Work the action items Circleback captured — find what is assigned to this user, do the ones the workspace can do, and update status only for work that is actually finished. Use when the user asks what they owe, "do my action items", "what's still open from", or wants to close, reassign, or add an action item.

See how to install

Good for

  • Review your open tasks from this week's meetings
  • Turn meeting tasks into code changes or tickets
  • Draft replies requested during a meeting
  • Update task status or reassign an owner

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Work the action items

Circleback turns meetings into action items with an owner and a status. The job is to work the ones that belong to this user, and to keep the list true: an item is done when the work is done, not when it is convenient.

1. Start from the assignee, not the search box

SearchActionItems with status PENDING returns the user's own open items. For someone else's, resolve them with FindProfiles and pass their profile ID. Filter by date range or tags when the user scopes the request ("from this week's customer calls"), and read the linked meeting with ReadMeetings when an item's title does not say enough to act on.

2. Sort each item by what the workspace can do

  • A code change — make it here, open it for review, and cite the meeting.
  • A ticket or issue — file it through the connected tracker with the item's wording and the meeting in the body.
  • A message or reply — draft it; never send unless the user asked for exactly that.
  • Something outside the workspace — leave it open and say so.

3. Update status only for finished work

UpdateActionItem to DONE after the change is merged, the ticket exists, or the user confirms they did the part you could not. Reassign only when the notes make the real owner clear or the user asks. CreateActionItem only when the user asks for a new one; a follow-up you discovered goes in your report first.

4. Report the list

One line per item: what it was, what you did (changed, filed, drafted, left open and why), and the meeting it came from. Items that turned out stale — done in a later meeting, or superseded — are worth pointing out rather than quietly closing.

Anti-patterns

  • Marking done to clean up the list. A closed item that was not finished resurfaces as a broken promise.
  • Deleting instead of closing. Deletion erases the record; it is only for an item the user says should never have existed.
  • Doing other people's items. Work assigned to a teammate is theirs to close; list it, do not take it.
  • Acting on the title alone. The linked meeting says what "fix the export" actually meant.

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
superset-sh/superset15.3KUpdated Oct 18, 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
superset-sh/superset15.3KUpdated Oct 18, 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
superset-sh/superset15.3KUpdated Oct 18, 2026

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
superset-sh/superset15.3KUpdated Oct 18, 2026

cdp-verification

FreeSummary

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.

  • Reproducing reported bugs in the running app
  • Comparing UI behavior before and after a fix
  • Checking state across navigation and reopening
superset-sh/superset15.3KUpdated Oct 18, 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
superset-sh/superset15.3KUpdated Oct 18, 2026

See all skills by superset-sh

Report a problem with this skill