[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HXMX74ZNAYNAAYSANC6Z3H":3,"skill-same:01M6HXMX74ZNAYNAAYSANC6Z3H":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6HXMX74ZNAYNAAYSANC6Z3H","multi-deliverable-tracking",null,"Track and complete all required deliverables before finishing a task","HKUDS\u002FAgentPilot","HKUDS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F118165258?v=4","01M6HW8VRNZP64G0P4MVJW2KKQ","✨Data Intelligence Lab@HKU✨","01M6HW8VWZVHBRHYH3T330PFWV",8029,"MIT","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002FSKILL.md",[],[19,20,21,22,23,24],"tracking","multi","multi deliverable tracking","task","complete","deliverables","2026-11-10 10:12:30",false,"---\nname: multi-deliverable-tracking\ndescription: Track and complete all required deliverables before finishing a task\n---\n\n# Multi-Deliverable Task Completion\n\n## Purpose\nEnsure ALL required outputs are completed before concluding a task, preventing premature task termination when multiple deliverables are required. **This skill includes mandatory enforcement steps that MUST be followed.**\n\n## Core Workflow\n\n### Step 1: Identify All Deliverables Upfront\n**CRITICAL: You MUST complete this step before producing ANY deliverable or taking any other action.**\n\nAt task start, explicitly enumerate EVERY required output:\n- Parse task requirements carefully for action verbs: \"create\", \"generate\", \"produce\", \"deliver\", \"write\", \"send\"\n- Count distinct deliverables (files, reports, emails, code modules, analyses, etc.)\n- Document this list visibly in working notes\n- Note any dependencies between deliverables\n\n**MANDATORY OUTPUT FORMAT:** Before any other work, output this exact format:\n```\nDELIVERABLES_IDENTIFIED:\n1. [filename\u002Fdescription] - [brief description]\n2. [filename\u002Fdescription] - [brief description]\n...\nTOTAL_DELIVERABLES: N\n```\n\n**Example identification:**\n```\nRequired Deliverables:\n1. [ ] Email to Juvoxa CEO\n2. [ ] Follow-up analysis report\nTotal: 2 deliverables\n```\n\n### Step 2: Create a Completion Tracker\n**CRITICAL: This tracker MUST be created and visible throughout task execution.**\n\nMaintain a visible checklist throughout task execution:\n```\nDELIVERABLE TRACKER\n===================\n[ ] Deliverable 1: [brief description]\n[ ] Deliverable 2: [brief description]\n[ ] Deliverable 3: [brief description]\n\nCompleted: 0\u002F3\n```\n\nUpdate this tracker AFTER each deliverable is fully completed (not just started).\n\n### Step 2.5: Filesystem Verification [MANDATORY BEFORE COMPLETION]\nBefore considering any deliverable complete, verify it exists:\n- For file deliverables: Use `list_dir` or `run_shell` (ls\u002Fcat) to confirm the file exists\n- For output deliverables: Verify the output was actually produced in the response stream\n- Document verification with: `[✓] filename verified in filesystem`\n\n### Step 3: Work Through Deliverables Systematically\n- Complete each deliverable fully before marking it done\n- Update the tracker immediately after completion\n- If a deliverable fails, note the failure but continue to others if possible\n- Return to failed items after completing others\n\n### Step 4: Final Verification Before Stopping\nBefore concluding the task, run this mandatory checklist:\n**CRITICAL ENFORCEMENT: You are BLOCKED from outputting \u003CCOMPLETE> until this verification passes.**\n\n```\nFINAL VERIFICATION (REQUIRED BEFORE \u003CCOMPLETE>)\n==================\n1. Review original task requirements\n2. Count total deliverables identified: ___\n3. Count deliverables marked complete: ___\n4. Do counts match? YES\u002FNO\n5. If NO: Identify missing deliverables and complete them\n6. If YES: Verify each deliverable exists and meets quality standards\n7. Filesystem verification (REQUIRED):\n   - [ ] file1.ext: VERIFIED (list_dir\u002Frun_shell confirmed)\n   - [ ] file2.ext: VERIFIED (list_dir\u002Frun_shell confirmed)\n\n**BLOCKING RULE:** If counts do not match OR any file cannot be verified in the filesystem, you MUST:\n1. NOT output \u003CCOMPLETE>\n2. Identify the missing\u002Funverified deliverables\n3. Complete and verify them\n4. Re-run this verification checklist\n\n**Only output \u003CCOMPLETE> when all deliverables are verified present in the filesystem or output stream.**\n```\n\n**Only stop when all deliverables are verified complete.**\n\n### Step 5: Self-Check Questions\nBefore marking task complete, ask:\n- \"Did I create EVERY output the task requested?\"\n- \"Are there any deliverables I started but didn't finish?\"\n- \"Would someone reviewing my work see all required outputs?\"\n- \"Have I verified EACH deliverable exists in the filesystem using list_dir or run_shell?\"\n- \"Is my DELIVERABLES_IDENTIFIED output present and accurate?\"\n\n## Common Pitfalls to Avoid\n\n❌ **Stopping after first deliverable** - Just because one output is done doesn't mean the task is complete\n❌ **Stopping after first deliverable** - Just because one output is done doesn't mean the task is complete\n\n❌ **Outputting \u003CCOMPLETE> without filesystem verification** - You must verify files exist before completion\n\n❌ **Skipping DELIVERABLES_IDENTIFIED output** - This mandatory output must appear before any work begins\n\n❌ **Assuming implicit completion** - Don't assume related outputs are \"part of\" a main deliverable unless explicitly stated\n\n❌ **Losing track mid-task** - The tracker must stay visible and updated throughout\n\n❌ **Counting drafts as complete** - Only mark done when the deliverable meets quality standards\n\n## Code Example: Tracker Template\n\n```python\n# Deliverable tracking template\ndeliverables = {\n    \"email_to_ceo\": {\"status\": \"pending\", \"file\": \"ceo_email.txt\"},\n    \"analysis_report\": {\"status\": \"pending\", \"file\": \"analysis.pdf\"},\n    \"summary_doc\": {\"status\": \"pending\", \"file\": \"summary.docx\"},\n}\n\ndef mark_complete(name):\n    deliverables[name][\"status\"] = \"complete\"\n    print(f\"✓ {name} completed\")\n    print(f\"Progress: {sum(1 for d in deliverables.values() if d['status'] == 'complete')}\u002F{len(deliverables)}\")\n\ndef all_complete():\n    return all(d[\"status\"] == \"complete\" for d in deliverables.values())\n```\n\n## When to Apply This Skill\n\nUse this pattern whenever a task involves:\n- Multiple files to create\n- Several analyses or reports\n- Multiple communications (emails, messages)\n- Code with multiple modules\u002Fcomponents\n- Any task with enumerated requirements (1), 2), 3)...)\n\n## Remember\n**The task is NOT complete until ALL deliverables are complete.** One done ≠ all done.\n","# Multi-Deliverable Task Completion\n\n## Purpose\nEnsure ALL required outputs are completed before concluding a task, preventing premature task termination when multiple deliverables are required. **This skill includes mandatory enforcement steps that MUST be followed.**\n\n## Core Workflow\n\n### Step 1: Identify All Deliverables Upfront\n**CRITICAL: You MUST complete this step before producing ANY deliverable or taking any other action.**\n\nAt task start, explicitly enumerate EVERY required output:\n- Parse task requirements carefully for action verbs: \"create\", \"generate\", \"produce\", \"deliver\", \"write\", \"send\"\n- Count distinct deliverables (files, reports, emails, code modules, analyses, etc.)\n- Document this list visibly in working notes\n- Note any dependencies between deliverables\n\n**MANDATORY OUTPUT FORMAT:** Before any other work, output this exact format:\n```\nDELIVERABLES_IDENTIFIED:\n1. [filename\u002Fdescription] - [brief description]\n2. [filename\u002Fdescription] - [brief description]\n...\nTOTAL_DELIVERABLES: N\n```\n\n**Example identification:**\n```\nRequired Deliverables:\n1. [ ] Email to Juvoxa CEO\n2. [ ] Follow-up analysis report\nTotal: 2 deliverables\n```\n\n### Step 2: Create a Completion Tracker\n**CRITICAL: This tracker MUST be created and visible throughout task execution.**\n\nMaintain a visible checklist throughout task execution:\n```\nDELIVERABLE TRACKER\n===================\n[ ] Deliverable 1: [brief description]\n[ ] Deliverable 2: [brief description]\n[ ] Deliverable 3: [brief description]\n\nCompleted: 0\u002F3\n```\n\nUpdate this tracker AFTER each deliverable is fully completed (not just started).\n\n### Step 2.5: Filesystem Verification [MANDATORY BEFORE COMPLETION]\nBefore considering any deliverable complete, verify it exists:\n- For file deliverables: Use `list_dir` or `run_shell` (ls\u002Fcat) to confirm the file exists\n- For output deliverables: Verify the output was actually produced in the response stream\n- Document verification with: `[✓] filename verified in filesystem`\n\n### Step 3: Work Through Deliverables Systematically\n- Complete each deliverable fully before marking it done\n- Update the tracker immediately after completion\n- If a deliverable fails, note the failure but continue to others if possible\n- Return to failed items after completing others\n\n### Step 4: Final Verification Before Stopping\nBefore concluding the task, run this mandatory checklist:\n**CRITICAL ENFORCEMENT: You are BLOCKED from outputting \u003CCOMPLETE> until this verification passes.**\n\n```\nFINAL VERIFICATION (REQUIRED BEFORE \u003CCOMPLETE>)\n==================\n1. Review original task requirements\n2. Count total deliverables identified: ___\n3. Count deliverables marked complete: ___\n4. Do counts match? YES\u002FNO\n5. If NO: Identify missing deliverables and complete them\n6. If YES: Verify each deliverable exists and meets quality standards\n7. Filesystem verification (REQUIRED):\n   - [ ] file1.ext: VERIFIED (list_dir\u002Frun_shell confirmed)\n   - [ ] file2.ext: VERIFIED (list_dir\u002Frun_shell confirmed)\n\n**BLOCKING RULE:** If counts do not match OR any file cannot be verified in the filesystem, you MUST:\n1. NOT output \u003CCOMPLETE>\n2. Identify the missing\u002Funverified deliverables\n3. Complete and verify them\n4. Re-run this verification checklist\n\n**Only output \u003CCOMPLETE> when all deliverables are verified present in the filesystem or output stream.**\n```\n\n**Only stop when all deliverables are verified complete.**\n\n### Step 5: Self-Check Questions\nBefore marking task complete, ask:\n- \"Did I create EVERY output the task requested?\"\n- \"Are there any deliverables I started but didn't finish?\"\n- \"Would someone reviewing my work see all required outputs?\"\n- \"Have I verified EACH deliverable exists in the filesystem using list_dir or run_shell?\"\n- \"Is my DELIVERABLES_IDENTIFIED output present and accurate?\"\n\n## Common Pitfalls to Avoid\n\n❌ **Stopping after first deliverable** - Just because one output is done doesn't mean the task is complete\n❌ **Stopping after first deliverable** - Just because one output is done doesn't mean the task is complete\n\n❌ **Outputting \u003CCOMPLETE> without filesystem verification** - You must verify files exist before completion\n\n❌ **Skipping DELIVERABLES_IDENTIFIED output** - This mandatory output must appear before any work begins\n\n❌ **Assuming implicit completion** - Don't assume related outputs are \"part of\" a main deliverable unless explicitly stated\n\n❌ **Losing track mid-task** - The tracker must stay visible and updated throughout\n\n❌ **Counting drafts as complete** - Only mark done when the deliverable meets quality standards\n\n## Code Example: Tracker Template\n\n```python\n# Deliverable tracking template\ndeliverables = {\n    \"email_to_ceo\": {\"status\": \"pending\", \"file\": \"ceo_email.txt\"},\n    \"analysis_report\": {\"status\": \"pending\", \"file\": \"analysis.pdf\"},\n    \"summary_doc\": {\"status\": \"pending\", \"file\": \"summary.docx\"},\n}\n\ndef mark_complete(name):\n    deliverables[name][\"status\"] = \"complete\"\n    print(f\"✓ {name} completed\")\n    print(f\"Progress: {sum(1 for d in deliverables.values() if d['status'] == 'complete')}\u002F{len(deliverables)}\")\n\ndef all_complete():\n    return all(d[\"status\"] == \"complete\" for d in deliverables.values())\n```\n\n## When to Apply This Skill\n\nUse this pattern whenever a task involves:\n- Multiple files to create\n- Several analyses or reports\n- Multiple communications (emails, messages)\n- Code with multiple modules\u002Fcomponents\n- Any task with enumerated requirements (1), 2), 3)...)\n\n## Remember\n**The task is NOT complete until ALL deliverables are complete.** One done ≠ all done.\n",{"name":5,"description":7},"main","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Flegacy\u002Fv1\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking",944,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot","https:\u002F\u002Fgithub.com\u002FHKUDS","https:\u002F\u002Fsites.google.com\u002Fview\u002Fchaoh","2026-11-12 22:26:39",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add HKUDS\u002FAgentPilot --skill multi-deliverable-tracking",{"tool":44,"command":45},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill multi-deliverable-tracking",{"tool":47,"command":48},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill multi-deliverable-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},".skill_id","OTHER","其他",40,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002F.skill_id",[59,79,98,123,146,169],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":25},"01M6HYB297NDABRERJRVG0K8R0","agentpilot","Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fplugins\u002Fagentpilot\u002Fskills\u002Fagentpilot\u002FSKILL.md",[],[61,66,67,68,69,70,71,72,73,74,75,76,77,78],"prepare","requests","with","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":25},"01M6HYAYWXTTE1J7DJM0MFNQ4H","remember","Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fskills\u002Fremember\u002FSKILL.md",[],[81,86,87,88,89,90,91,92,93,94,95,96,97],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":25},"01M6HYAVMPM4SBDV60R2B5HPV8","skill-discovery","Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fskill-discovery\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[110,111,112,89,113,114,115,116,117,118,119,120,121,122],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":25},"01M6HYAR811B3RB0M50RBEDGN6","delegate-task","Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fdelegate-task\u002FSKILL.md",[129],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[131,22,132,89,133,134,135,136,137,112,88,73,138,139,140,141,142,143,144,145],"delegate","delegate task","time","improve","desktop automation","worker","community","autonomous","tool","stack","for","share","tasks","automation","MCP",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":25},"01M6HYAM9FSGV6E52AYENDQXYH","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[153,154,155,156,157,158,159,160,161,162,163,164,165,166,141,167,168],"write special chars ts check","write","check","type","files","filters","only","template","file","python","typescript","output","Existing","type-checking","errors","script",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":25},"01M6HYAH05HGV7SVWSVR8PJRQD","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[176,177,154,68,141,168,178,179,180,181,182,160,161,183,184,162],"write special chars readback","readback","helper","post","via","scripts","read","verification","cleanup"]