capturing-tasks
Skill0 starsChanged 9 days agoMITView on GitHub
Creates, updates, links, completes, and archives GetItDone tasks, showing extracted tasks before creating them and asking before archiving. Use when the user asks to 'turn these meeting notes into tasks', 'add a task', 'create a to-do', 'add a repeating habit', 'T-123 is waiting on T-120', 'mark this done', 'I did my workout yesterday', 'change the due date', or 'archive finished tasks'. Nothing is permanently deleted.
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-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
- reviewing-workloadSkill
- 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
10 rules. About 0 are common, 1 is distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 35
Call getitdone:list_workspaces and confirm the target workspace if the user has more than one.
- Very specific: line 37
If a project is named, call getitdone:list_projects.
- Very specific: line 38
Call getitdone:list_tasks and check for tasks with the same or a very close title.
- Very specific: line 39
Call getitdone:create_task for each approved task.
- Very specific: line 41
When the user says one task is waiting on another, restate it ("T-124 is blocked by T-120"), then call getitdone:link_task_dependency.
- Distinctive: line 49
If a dependency link is refused because it would create a loop, report which tasks form the loop.
- Very specific: line 50
If the write operations are missing, the user did not grant tasks:write.
≈ “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/capturing-tasks/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Capture and update GetItDone tasks
Make changes to the user's tasks after showing them what will change. Needs the tasks:write scope, plus projects:read to file tasks under a project.
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>. Call getitdone:search_tools first for the exact argument shapes.
getitdone:list_workspaces: confirm which workspace to write to.getitdone:list_projects: project ids, to file a task under a project that exists.getitdone:list_tasks: find existing tasks, so you update instead of creating duplicates.getitdone:create_task: create a task. Supports a start date (defer until), a due date, a project id, and a recurrence ("every weekday", "the 1st of each month"). Returns the new task with its short id.getitdone:update_task: change a task by short id: name, status, priority, start date, due date, notes, story points, project, or repeat schedule. Returns the task's current state.getitdone:complete_task_occurrence: mark one day of a repeating task done, by short id and aYYYY-MM-DDday (today if omitted). Past days and early future days are allowed.getitdone:link_task_dependency: record that one task is blocked by another, or remove that link with actionremove. Links that would create a loop are refused.getitdone:archive_task: archive or unarchive a task by short id. Archived tasks are hidden from the main list.
Workflow
- Call
getitdone:list_workspacesand confirm the target workspace if the user has more than one. - For notes or a longer text, extract one task per action item: a short imperative title, and priority, dates, project, or recurrence only when the text states them. Show the list and ask for changes once.
- If a project is named, call
getitdone:list_projects. If it is not there, say so instead of inventing it or writing its name into the task. - Call
getitdone:list_tasksand check for tasks with the same or a very close title. Offer to update those instead of creating new ones. - Call
getitdone:create_taskfor each approved task. Report each new short id. - For changes to existing tasks, restate the change ("T-123: TODO to IN_PROGRESS"), then call
getitdone:update_taskand echo the returned state. - When the user says one task is waiting on another, restate it ("T-124 is blocked by T-120"), then call
getitdone:link_task_dependency. - For a repeating task, use
getitdone:complete_task_occurrencefor the day the user named instead of changing the task's status. - For archiving, list the tasks by short id and name and get a yes before calling
getitdone:archive_taskon each.
Rules
- There is no permanent delete. If the user asks to delete a task, offer to archive it and say archive is reversible.
- Resolve relative dates ("Friday", "yesterday", "next week") to a calendar date and state it before writing.
- If a dependency link is refused because it would create a loop, report which tasks form the loop.
- If the write operations are missing, the user did not grant
tasks:write. Say so and tell them to reconnect with that scope. - A
SCOPE_MISSINGresult names the scope needed. Pass that on instead of retrying.
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.

