[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBFD37NPJB05G51TD03M1F":3,"skill-same:01M6XBFD37NPJB05G51TD03M1F":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},"01M6XBFD37NPJB05G51TD03M1F","deliverable-completion",null,"Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required","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\u002Fdeliverable-completion\u002FSKILL.md",[],[18,19,20,21,22,23,24],"deliverable completion","tasks","file","creation","complete","submission","when","2026-11-10 10:12:30",false,"---\nname: deliverable-completion\ndescription: Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required\n---\n\n# Deliverable Completion Protocol\n\n## Purpose\n\nThis skill addresses a common misconception during document and file creation tasks: agents sometimes search for or attempt to use a `submit_work`, `finalize`, or similar tool after creating the deliverable. **No such step is required.** Task completion is achieved when the file is successfully created with the required content.\n\n## Core Principle\n\n**File creation = Task completion**\n\nWhen a task requests you to create a document, report, script, or any file-based deliverable, the task is complete once:\n1. The file has been written to disk\n2. The file contains the required content\n3. The file is in the correct format and location\n\nThere is **no additional submission, finalization, or confirmation step** needed.\n\n## Execution Workflow\n\n### Step 1: Create the Deliverable\n\nUse the appropriate file creation method for your task:\n\n```python\n# For programmatic file creation\nwith open('deliverable.docx', 'wb') as f:\n    f.write(document_content)\n```\n\n```bash\n# For shell-based creation\necho \"content\" > output.txt\n```\n\nOr use available tools like `write_file`, `create_file`, etc.\n\n### Step 2: Verify Creation\n\nConfirm the file exists and contains expected content:\n\n```bash\nls -la deliverable.docx\n# or\ncat output.txt\n```\n\n### Step 3: Declare Completion\n\nOnce verification passes, **the task is complete**. Do not:\n- Search for a `submit_work` tool\n- Look for a `finalize_task` function\n- Attempt to \"upload\" or \"submit\" the file elsewhere\n- Add extra confirmation steps\n\nSimply report that the deliverable has been created successfully.\n\n## Common Mistakes to Avoid\n\n| ❌ Incorrect | ✅ Correct |\n|-------------|-----------|\n| Creating file, then searching for submit tool | Creating file, verifying, declaring done |\n| Assuming a finalization API exists | Treating file creation as the final step |\n| Adding unnecessary confirmation steps | Completing after successful write |\n\n## Example Task Flow\n\n**Task:** \"Create a negotiation strategy document covering BATNA, ZOPA, and timeline.\"\n\n**Correct Execution:**\n1. Write the document content\n2. Save as `negotiation_strategy.docx`\n3. Verify file exists (~43KB, contains all sections)\n4. Report: \"Negotiation strategy document created successfully\"\n5. **Task complete** — no further action needed\n\n## When This Applies\n\n- Document creation (.docx, .pdf, .md, .txt)\n- Code file generation (.py, .sh, .js)\n- Data exports (.csv, .json, .xlsx)\n- Configuration files (.yaml, .toml, .ini)\n- Any file-based deliverable\n\n## When This Does NOT Apply\n\n- Tasks explicitly requiring external submission (e.g., \"submit to API endpoint\")\n- Tasks requiring human review\u002Fapproval workflows\n- Tasks where the file is an intermediate step (not the final deliverable)","# Deliverable Completion Protocol\n\n## Purpose\n\nThis skill addresses a common misconception during document and file creation tasks: agents sometimes search for or attempt to use a `submit_work`, `finalize`, or similar tool after creating the deliverable. **No such step is required.** Task completion is achieved when the file is successfully created with the required content.\n\n## Core Principle\n\n**File creation = Task completion**\n\nWhen a task requests you to create a document, report, script, or any file-based deliverable, the task is complete once:\n1. The file has been written to disk\n2. The file contains the required content\n3. The file is in the correct format and location\n\nThere is **no additional submission, finalization, or confirmation step** needed.\n\n## Execution Workflow\n\n### Step 1: Create the Deliverable\n\nUse the appropriate file creation method for your task:\n\n```python\n# For programmatic file creation\nwith open('deliverable.docx', 'wb') as f:\n    f.write(document_content)\n```\n\n```bash\n# For shell-based creation\necho \"content\" > output.txt\n```\n\nOr use available tools like `write_file`, `create_file`, etc.\n\n### Step 2: Verify Creation\n\nConfirm the file exists and contains expected content:\n\n```bash\nls -la deliverable.docx\n# or\ncat output.txt\n```\n\n### Step 3: Declare Completion\n\nOnce verification passes, **the task is complete**. Do not:\n- Search for a `submit_work` tool\n- Look for a `finalize_task` function\n- Attempt to \"upload\" or \"submit\" the file elsewhere\n- Add extra confirmation steps\n\nSimply report that the deliverable has been created successfully.\n\n## Common Mistakes to Avoid\n\n| ❌ Incorrect | ✅ Correct |\n|-------------|-----------|\n| Creating file, then searching for submit tool | Creating file, verifying, declaring done |\n| Assuming a finalization API exists | Treating file creation as the final step |\n| Adding unnecessary confirmation steps | Completing after successful write |\n\n## Example Task Flow\n\n**Task:** \"Create a negotiation strategy document covering BATNA, ZOPA, and timeline.\"\n\n**Correct Execution:**\n1. Write the document content\n2. Save as `negotiation_strategy.docx`\n3. Verify file exists (~43KB, contains all sections)\n4. Report: \"Negotiation strategy document created successfully\"\n5. **Task complete** — no further action needed\n\n## When This Applies\n\n- Document creation (.docx, .pdf, .md, .txt)\n- Code file generation (.py, .sh, .js)\n- Data exports (.csv, .json, .xlsx)\n- Configuration files (.yaml, .toml, .ini)\n- Any file-based deliverable\n\n## When This Does NOT Apply\n\n- Tasks explicitly requiring external submission (e.g., \"submit to API endpoint\")\n- Tasks requiring human review\u002Fapproval workflows\n- Tasks where the file is an intermediate step (not the final deliverable)",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fdeliverable-completion","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 deliverable-completion",{"tool":42,"command":43},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill deliverable-completion",{"tool":45,"command":46},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill deliverable-completion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdeliverable-completion\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},".skill_id","OTHER","其他",36,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdeliverable-completion\u002F.skill_id",[57,81,98,107,137,153],{"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,20,80],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","python",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[88,89,65,20,90,80,91,92,93,94,95,79,96,97,69,72,74],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[105,65,69,106,74,92,79,20,80,72],"write special chars heredoc","shell",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"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",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[119,120,121,122,123,67,124,125,126,127,128,72,129,130,131,132,133,134,135,136],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"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",[],[144,145,146,147,72,148,97,149,150,151,152],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"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",[],[160,161,162,163,164,165,20,166,167,168],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]