searching-getitdone-api-docs
Skill0 starsChanged 9 days agoMITView on GitHub
Answers questions about the GetItDone developer API from its own documentation. Use when the user asks 'what does the 429 problem code mean in the GetItDone API', 'how do I authenticate against the GetItDone API', 'how does this GetItDone REST endpoint work', 'where is the GetItDone API reference', 'how do I connect an integration to GetItDone', or wants GetItDone developer docs. Reads documentation 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
- reviewing-workloadSkill
- 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
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
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 the operation below …
- Distinctive: line 30
If the top result is a guide or error page and the snippet is not enough, fetch its Markdown-twin URL to read the full page.
- Distinctive: line 37
If nothing relevant comes back, say the docs do not cover it.
- Distinctive: line 38
Keep API keys and tokens out of examples.
≈ “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/searching-getitdone-api-docs/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->GetItDone developer docs lookup
Answer developer questions from GetItDone's published documentation, with links, instead of from memory.
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 the operation below inside getitdone:execute_typescript as external_search_docs.
getitdone:search_docs: ranked results from GetItDone's developer documentation (REST operations, error and problem codes, guide pages), each with its public URL and, for guide and error pages, a Markdown-twin URL.
Workflow
- Turn the question into a short query: the operation name, the status or problem code, or two or three keywords.
- Call
getitdone:search_docs. - If the top result is a guide or error page and the snippet is not enough, fetch its Markdown-twin URL to read the full page.
- Answer in a few sentences. Quote the exact field names, codes, and paths from the docs.
- End with the public URL of each page you used.
Rules
getitdone:search_docssearches GetItDone's developer documentation, not the user's tasks or workspace notes. For task content, useinvestigating-tasks.- If nothing relevant comes back, say the docs do not cover it. Do not fill the gap with guessed endpoints or fields.
- Keep API keys and tokens out of examples. Use placeholders.
- This skill only reads the docs. Never call
getitdone:create_task,getitdone:update_task,getitdone:complete_task_occurrence,getitdone:link_task_dependency, orgetitdone:archive_taskfrom it.
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.

