reviewing-workload
Skill0 starsChanged 9 days agoMITView on GitHub
Summarizes what is on the user's plate in GetItDone: tasks due, in progress, in review, and blocked, per workspace or project. Use when the user asks 'what's on my plate this week', 'what should I work on next', 'what's due', 'what's blocked right now', 'give me a status update on this project', 'show my to-do list', or wants a workload or project status overview. Read-only.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 0 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every tool in this skill comes from the getitdone MCP server, the GetItDone connector, and is written here as getitdone:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example getitdone:list_tasks.
- Very specific: line 22
If the tool list shows only getitdone:search_tools and getitdone:execute_typescript, the server is in Code Mode: call each operation below …
- Very specific: line 31
Call getitdone:list_workspaces.
- Very specific: line 32
If the user named a project, call getitdone:list_projects and use its id as the getitdone:list_tasks filter.
- Very specific: line 33
Call getitdone:list_tasks.
- Very specific: line 44
Do not change anything from this skill: never call getitdone:create_task, getitdone:update_task, getitdone:complete_task_occurrence, …
- Very specific: line 46
If a project the user named is not in getitdone:list_projects, say it does not exist.
- Very specific: line 47
If a workspace id the user gave is not one of theirs, say so and offer getitdone:list_workspaces.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from plugins/getitdone/skills/reviewing-workload/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->GetItDone workload review
Turn the workspace's task list into a short, prioritized view of what needs attention. Read only.
Connecting and calling the tools
Every tool in this skill comes from the getitdone MCP server, the GetItDone connector, and is written here as getitdone:<tool>.
- Tools listed by name: call them directly, for example
getitdone:list_tasks. - Only
getitdone:search_toolsandgetitdone:execute_typescriptlisted (Code Mode, the default): callgetitdone:search_toolsfirst, then call each tool insidegetitdone:execute_typescriptasexternal_<tool>(for exampleexternal_list_tasks); the program mustreturnits result. Scopes, confirmations and gates are identical on both surfaces. - "Tool not found": switch to the Code Mode route instead of retrying the direct call. If
getitdone:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects GetItDone and approves that scope. - No
getitdonetools at all: GetItDone is not connected yet. Follow thesetup-getitdoneskill.
Tools you will use
If the tool list shows only getitdone:search_tools and getitdone:execute_typescript, the server is in Code Mode: call each operation below inside getitdone:execute_typescript as external_<name>, and use one program to run several independent reads together.
getitdone:list_workspaces: the workspaces the account belongs to, with their ids. Pass an id asworkspaceIdto target one.getitdone:list_projects: the projects in the workspace with their ids.getitdone:list_tasks: the latest version of each task with name, short id, status (TODO,IN_PROGRESS,IN_REVIEW,COMPLETED,BLOCKED), priority, due date, projects, whether it is blocked, and how many tasks it blocks. Filters by status, priority, and project.getitdone:get_task_details: notes, attachments, and the dependency chain for one task, when a summary line is not enough.
Workflow
- Call
getitdone:list_workspaces. If the user belongs to more than one and did not name one, ask which, or use the one they usually work in and say which you used. - If the user named a project, call
getitdone:list_projectsand use its id as thegetitdone:list_tasksfilter. - Call
getitdone:list_tasks. Leave outCOMPLETEDtasks unless the user asks for them. - Present, in this order:
- Blocked tasks, with how many tasks each one blocks.
- Overdue tasks and tasks due in the window the user asked about (default: the next 7 days), sorted by due date then priority.
- In progress and in review.
- A count of the remaining
TODOtasks.
- For the top blocked task, call
getitdone:get_task_detailsand name what blocks it. - Close with at most three suggested next actions drawn from the list, such as the blocker that unblocks the most tasks.
Rules
- Do not change anything from this skill: never call
getitdone:create_task,getitdone:update_task,getitdone:complete_task_occurrence,getitdone:link_task_dependency, orgetitdone:archive_task. Hand off tocapturing-tasksfor changes. - Refer to tasks by short id and name so the user can find them in the app.
- If a project the user named is not in
getitdone:list_projects, say it does not exist. Do not guess another one. - If a workspace id the user gave is not one of theirs, say so and offer
getitdone:list_workspaces.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

