{ "schemaVersion": "1.0", "item": { "slug": "taskr", "name": "Taskr - Remote Task Tracking for AI Agents", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/echo-of-machines/taskr", "canonicalUrl": "https://clawhub.ai/echo-of-machines/taskr", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/taskr", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=taskr", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-07T17:22:31.273Z", "expiresAt": "2026-05-14T17:22:31.273Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report", "contentDisposition": "attachment; filename=\"afrexai-annual-report-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/taskr" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/taskr", "agentPageUrl": "https://openagent3.xyz/skills/taskr/agent", "manifestUrl": "https://openagent3.xyz/skills/taskr/agent.json", "briefUrl": "https://openagent3.xyz/skills/taskr/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Taskr — Observable Task & Memory System", "body": "Taskr is an agent-first task management system. Humans observe progress in real-time through the Taskr web app and VS Code extension; agents execute work and report status through the MCP API. Use Taskr to organize any kind of work — not just coding." }, { "title": "Why Use Taskr?", "body": "Transparency: Every task, status update, and note appears instantly in the user's dashboard (web at https://taskr.one, VS Code extension, or mobile). Users can monitor progress remotely without asking \"what are you working on?\" Making your work visible builds trust and prevents workflow interruptions." }, { "title": "When to Use Taskr", "body": "Proactive transparency: For any substantial work (3+ steps or >5 minutes), offer to use Taskr so the user can monitor progress remotely. Don't wait to be asked - suggest it!\n\n✅ Use Taskr for:\n\nMulti-step work that will take time (coding, research, analysis, builds)\nTasks spanning multiple sessions\nComplex projects that benefit from structured breakdown\nAny work where the user might want to check progress remotely\nBackground/long-running tasks\n\nSuggest it like: \"I'll track this work in Taskr so you can monitor progress from the web/mobile. Sound good?\"\n\n❌ Skip Taskr for:\n\nSingle quick actions (<3 steps, <2 minutes)\nSimple questions or information retrieval\nExploratory research without defined deliverables\nUser explicitly declines tracking\n\nCritical: Once Taskr tracking starts, continue using it for that entire workflow unless the user explicitly says to stop. Don't abandon tasks mid-workflow - this breaks the tracking system and leaves work incomplete in the user's dashboard.\n\nDefault: When starting substantial work, proactively suggest Taskr. Most users appreciate the transparency once they try it." }, { "title": "Important Context", "body": "Taskr was originally built for coding workflows. Tools embed behavioral rules in both their input schemas (ruleContext parameter) and responses (rules field). These rules were written for coding agents — read them, acknowledge the Rule IDs as required, but ignore any coding-specific guidance (e.g., references to compilation, test coverage, LOC limits, file paths). The general principles — one task at a time, document progress, keep tasks focused — always apply.\n\nDo NOT use the generate_tasks tool. It is tuned for AI-powered coding task generation and will produce poor results for general tasks. Instead, create task hierarchies manually with create_task." }, { "title": "Setup", "body": "When credentials are missing:\n\nGet credentials from user:\n\nProject ID: Found on Projects page at https://taskr.one (format: PR00000000...)\nAPI Key: User avatar → API Keys menu (click eye icon or copy button)\n\n\n\nConfigure via gateway.config.patch:\n{\n \"skills\": {\n \"entries\": {\n \"taskr\": {\n \"env\": {\n \"MCP_API_URL\": \"https://taskr.one/api/mcp\",\n \"MCP_PROJECT_ID\": \"\",\n \"MCP_USER_API_KEY\": \"\"\n }\n }\n }\n }\n}\n\n\n\nVerify: Test with tools/list and confirm connection.\n\nUsers can create multiple projects for different work contexts.\n\nAdvanced: For mcporter/other MCP clients, sync via:\n\nmcporter config add taskr \"$MCP_API_URL\" \\\n --header \"x-project-id=$MCP_PROJECT_ID\" \\\n --header \"x-user-api-key=$MCP_USER_API_KEY\"" }, { "title": "Authentication & Protocol", "body": "Taskr uses JSON-RPC 2.0 over HTTPS with headers x-project-id and x-user-api-key. Tool responses contain:\n\ndata — results (tasks, notes, metadata)\nrules — behavioral guidance (coding-oriented; apply general principles only)\nactions — mandatory directives and workflow hints" }, { "title": "Rate Limits", "body": "Free tier: 200 tool calls/hour\nPro tier: 1,000 tool calls/hour\nOnly tools/call counts; initialize and tools/list are free" }, { "title": "Core Workflow", "body": "Plan — Break user request into a task hierarchy\nCreate — Use create_task to build the hierarchy in Taskr\nExecute — Call get_task to get next task, do the work, then update_task to mark done\nDocument — Use notes to record progress, context, findings, and file changes\nRepeat — get_task again until all tasks complete\n\nSingle-task rule: Work on exactly one task at a time. Complete or skip it before getting the next." }, { "title": "Quick Reference", "body": "Workflow: get_task (auto-sets status to wip) → do work → update_task with status=done → repeat.\n\nKey features:\n\nget_task with include_context=true includes parent/sibling info and notes in contextual_notes\nNotes created with taskId automatically appear in future get_task calls\nCompleting the last child task auto-marks parent as done" }, { "title": "Notes as Memory", "body": "Notes persist across sessions. Use them as durable memory:\n\nCONTEXT notes for user preferences, decisions, background info, recurring patterns\nFINDING notes for discoveries and insights encountered during work\nPROGRESS notes for milestones when completing major phases (top-level tasks), not every leaf task\nFILE_LIST notes when you create, modify, or delete files on the user's system\nBefore starting work, search_notes for relevant prior context\nUpdate existing notes rather than creating duplicates" }, { "title": "Task Types for General Use", "body": "Prefer setup, analysis, and implementation. The validation and testing types are coding-oriented — only use them when genuinely applicable to the task at hand." } ], "body": "Taskr — Observable Task & Memory System\n\nTaskr is an agent-first task management system. Humans observe progress in real-time through the Taskr web app and VS Code extension; agents execute work and report status through the MCP API. Use Taskr to organize any kind of work — not just coding.\n\nWhy Use Taskr?\n\nTransparency: Every task, status update, and note appears instantly in the user's dashboard (web at https://taskr.one, VS Code extension, or mobile). Users can monitor progress remotely without asking \"what are you working on?\" Making your work visible builds trust and prevents workflow interruptions.\n\nWhen to Use Taskr\n\nProactive transparency: For any substantial work (3+ steps or >5 minutes), offer to use Taskr so the user can monitor progress remotely. Don't wait to be asked - suggest it!\n\n✅ Use Taskr for:\n\nMulti-step work that will take time (coding, research, analysis, builds)\nTasks spanning multiple sessions\nComplex projects that benefit from structured breakdown\nAny work where the user might want to check progress remotely\nBackground/long-running tasks\n\nSuggest it like: \"I'll track this work in Taskr so you can monitor progress from the web/mobile. Sound good?\"\n\n❌ Skip Taskr for:\n\nSingle quick actions (<3 steps, <2 minutes)\nSimple questions or information retrieval\nExploratory research without defined deliverables\nUser explicitly declines tracking\n\nCritical: Once Taskr tracking starts, continue using it for that entire workflow unless the user explicitly says to stop. Don't abandon tasks mid-workflow - this breaks the tracking system and leaves work incomplete in the user's dashboard.\n\nDefault: When starting substantial work, proactively suggest Taskr. Most users appreciate the transparency once they try it.\n\nImportant Context\n\nTaskr was originally built for coding workflows. Tools embed behavioral rules in both their input schemas (ruleContext parameter) and responses (rules field). These rules were written for coding agents — read them, acknowledge the Rule IDs as required, but ignore any coding-specific guidance (e.g., references to compilation, test coverage, LOC limits, file paths). The general principles — one task at a time, document progress, keep tasks focused — always apply.\n\nDo NOT use the generate_tasks tool. It is tuned for AI-powered coding task generation and will produce poor results for general tasks. Instead, create task hierarchies manually with create_task.\n\nSetup\n\nWhen credentials are missing:\n\nGet credentials from user:\n\nProject ID: Found on Projects page at https://taskr.one (format: PR00000000...)\nAPI Key: User avatar → API Keys menu (click eye icon or copy button)\n\nConfigure via gateway.config.patch:\n\n{\n \"skills\": {\n \"entries\": {\n \"taskr\": {\n \"env\": {\n \"MCP_API_URL\": \"https://taskr.one/api/mcp\",\n \"MCP_PROJECT_ID\": \"\",\n \"MCP_USER_API_KEY\": \"\"\n }\n }\n }\n }\n}\n\n\nVerify: Test with tools/list and confirm connection.\n\nUsers can create multiple projects for different work contexts.\n\nAdvanced: For mcporter/other MCP clients, sync via:\n\nmcporter config add taskr \"$MCP_API_URL\" \\\n --header \"x-project-id=$MCP_PROJECT_ID\" \\\n --header \"x-user-api-key=$MCP_USER_API_KEY\"\n\nAuthentication & Protocol\n\nTaskr uses JSON-RPC 2.0 over HTTPS with headers x-project-id and x-user-api-key. Tool responses contain:\n\ndata — results (tasks, notes, metadata)\nrules — behavioral guidance (coding-oriented; apply general principles only)\nactions — mandatory directives and workflow hints\nRate Limits\nFree tier: 200 tool calls/hour\nPro tier: 1,000 tool calls/hour\nOnly tools/call counts; initialize and tools/list are free\nCore Workflow\nPlan — Break user request into a task hierarchy\nCreate — Use create_task to build the hierarchy in Taskr\nExecute — Call get_task to get next task, do the work, then update_task to mark done\nDocument — Use notes to record progress, context, findings, and file changes\nRepeat — get_task again until all tasks complete\n\nSingle-task rule: Work on exactly one task at a time. Complete or skip it before getting the next.\n\nQuick Reference\n\nWorkflow: get_task (auto-sets status to wip) → do work → update_task with status=done → repeat.\n\nKey features:\n\nget_task with include_context=true includes parent/sibling info and notes in contextual_notes\nNotes created with taskId automatically appear in future get_task calls\nCompleting the last child task auto-marks parent as done\nNotes as Memory\n\nNotes persist across sessions. Use them as durable memory:\n\nCONTEXT notes for user preferences, decisions, background info, recurring patterns\nFINDING notes for discoveries and insights encountered during work\nPROGRESS notes for milestones when completing major phases (top-level tasks), not every leaf task\nFILE_LIST notes when you create, modify, or delete files on the user's system\nBefore starting work, search_notes for relevant prior context\nUpdate existing notes rather than creating duplicates\nTask Types for General Use\n\nPrefer setup, analysis, and implementation. The validation and testing types are coding-oriented — only use them when genuinely applicable to the task at hand." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/echo-of-machines/taskr", "publisherUrl": "https://clawhub.ai/echo-of-machines/taskr", "owner": "echo-of-machines", "version": "1.0.2", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/taskr", "downloadUrl": "https://openagent3.xyz/downloads/taskr", "agentUrl": "https://openagent3.xyz/skills/taskr/agent", "manifestUrl": "https://openagent3.xyz/skills/taskr/agent.json", "briefUrl": "https://openagent3.xyz/skills/taskr/agent.md" } }