FreePublished on GitHubEnglish overview

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.

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

Run score Not tested

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

Overview

What it does

Review action items assigned to you by Circleback and work on the ones that can be handled in the workspace. This can include making code changes and opening them for review, creating tickets in a connected tracker, or drafting a message. If requested, the skill can also add an action item or change its assignee. For each item, it reports what it did and which meeting the item came from.

When it helps

Use it after meetings to see what you agreed to do, or to work through open items from this week’s customer meetings. If an item’s title is unclear, the linked meeting can provide context. It can also point out older items that a later meeting resolved.

Example requests

“Show me my open action items from this week’s meetings.”
“Work on the code changes and tickets from this meeting.”

Notes

A connection to Circleback is required. Ticket creation uses a connected tracking tool. Messages remain drafts unless you explicitly ask to send them. Items that require work outside the workspace stay open, and code changes are marked done only after they are merged.

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 limits sending to explicit requests and defines when status or ownership may change.
Easy setupDoes it need few tools or API keys, and are they documented?: BPartly lackingIt requires Circleback and a connected tracker, but gives no setup procedure.

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

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.

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