[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBP3CWMX2E9VTM4QFW7W4Q":3,"skill-same:01M6XBP3CWMX2E9VTM4QFW7W4Q":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":13,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M6XBP3CWMX2E9VTM4QFW7W4Q","multi-deliverable-tracking",null,"Track and complete all required deliverables before finishing a task","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002FSKILL.md",[],[18,19,20,21,22,23,24],"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","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill multi-deliverable-tracking",{"tool":42,"command":43},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill multi-deliverable-tracking",{"tool":45,"command":46},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill multi-deliverable-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},".skill_id","OTHER","其他",40,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fmulti-deliverable-tracking\u002F.skill_id",[57,82,99,108,138,154],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":25},"01M6XCCXD3NCM2YKR3WNGBASPC","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","file","python",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":25},"01M6XCCT7E3J922Q345PBGSHPN","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[89,90,65,80,91,81,92,93,94,95,96,79,97,98,69,72,74],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":25},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[106,65,69,107,74,93,79,80,81,72],"write special chars heredoc","shell",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":25},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[120,121,122,123,124,67,125,126,127,128,129,72,130,131,132,133,134,135,136,137],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":25},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[145,146,147,148,72,149,98,150,151,152,153],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":25},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[161,162,163,164,165,166,80,167,168,169],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]