[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KFKEYV5KCDPHFRRYRJ1E3M":3,"skill-same:01M6KFKEYV5KCDPHFRRYRJ1E3M":59},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M6KFKEYV5KCDPHFRRYRJ1E3M","multi-deliverable-tracking",null,"Track and complete all required deliverables before finishing a task","xyliu-cs\u002FOpenSpace-GDPval","xyliu-cs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89236536?v=4","01M6KF8Z1V4TXS86CKSH48BY8T","xy","01M6KF8Z67443W0SHXM85JEF0B",0,"MIT","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002FSKILL.md",[],[19,20,21,22,23,24,25],"tracking","multi","multi deliverable tracking","task","complete","deliverables","track","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","af1b40a42167d09c30b3a63000aa14ace4c1e229","gdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval","https:\u002F\u002Fgithub.com\u002Fxyliu-cs","https:\u002F\u002Fxyliu-cs.github.io","PhD Student in CS, CUHK-Shenzhen.","2026-04-06 20:32:15",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add xyliu-cs\u002FOpenSpace-GDPval --skill multi-deliverable-tracking",{"tool":45,"command":46},"bunx","bunx skills add xyliu-cs\u002FOpenSpace-GDPval --skill multi-deliverable-tracking",{"tool":48,"command":49},"pnpm","pnpm dlx skills add xyliu-cs\u002FOpenSpace-GDPval --skill multi-deliverable-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},".skill_id","OTHER","其他",40,"https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002F.skill_id",[60,72,80,96,122,144],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":26},"01M6KG8MF1S664SWBDENYRSCK8","zip-export-deliverable","Ensures codebase deliverables are properly exported as ZIP archives through a dedicated finalization step","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fzip-export-deliverable\u002FSKILL.md",[],[67,68,69,24,70,71],"zip export deliverable","zip","export","codebase","as",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":26},"01M6KG8GAZWHHEK7VNJDW0ME21","zip-deliverable-finalization","Ensure codebase deliverables are properly packaged as ZIP exports in a dedicated final step","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fzip-deliverable-finalization\u002FSKILL.md",[],[79,68,24,70,71],"zip deliverable finalization",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":26},"01M6KG8CMQQ1PYMNTSRZ9VS1MD","zero-iteration-failure-analysis","Identify and handle agent failures with 0 iterations as pre-execution system issues","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fzero-iteration-failure-analysis\u002FSKILL.md",[],[87,88,89,90,91,92,93,94,71,95],"failure analysis","ZeRO","analysis","iteration","zero iteration failure analysis","with","issues","execution","system",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":107,"publishedAt":26},"01M6KG86W3PA07FT9W58YHHERM","write-file-fallback-report","Generate professional documents using write_file when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fwrite-file-fallback-report\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[108,109,110,111,112,113,114,115,116,117,118,119,120,121],"fallback","write","file","report","write file fallback report","domain","professional","sources","retrieval","generate","embedded","documents","data","knowledge",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":133,"publishedAt":26},"01M6KG82GAEY3GG77CMGCK1C2T","fallback-doc-with-delegation","Generate professional documents after tool failures using shell_agent for complex formats or write_file for simple text\u002Fmarkdown","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fwrite-file-fallback-report-enhanced\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[134,92,108,135,136,137,119,117,110,138,139,140,109,141,114,142,143],"fallback doc with delegation","doc","delegation","shell","markdown","tool","text","simple","formats","for",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":26},"01M6KG7WT7GX5NYCGEFHW22NV7","context-anchored-fallback-report","Generate documents with write_file when retrieval tools fail, with explicit guardrails against task context drift","https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fwrite-file-fallback-report-enhanced-4bc5c2\u002FSKILL.md",[150],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[108,111,152,153,117,110,154,155,109,22,156,116,92,157,119],"context","context anchored fallback report","Guardrails","Tools","drift","context drift"]