[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KHY0TEDFWBPJMPEY9YY952":3,"skill-same:01M6KHY0TEDFWBPJMPEY9YY952":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M6KHY0TEDFWBPJMPEY9YY952","deliverable-completion",null,"Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required","AG064\u002FOpenSpace","AG064","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184930299?v=4","01M6KHVFG7TB73NHX3RDYSTMH2","01M6KHVFMM7XA2PZA9Z83PHS3V",0,"MIT","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdeliverable-completion\u002FSKILL.md",[],[18,19,20,21,22],"deliverable completion","tasks","file","creation","complete","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","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Fdeliverable-completion","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace","https:\u002F\u002Fgithub.com\u002FAG064","AG064, E.Mi.\r\n\r\nA person who thinks all the time, yet all they have to think about is nothing. I want to improve the world and work on open source projects","2026-10-08 06:53:48",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add AG064\u002FOpenSpace --skill deliverable-completion",{"tool":41,"command":42},"bunx","bunx skills add AG064\u002FOpenSpace --skill deliverable-completion",{"tool":44,"command":45},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill deliverable-completion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdeliverable-completion\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},".skill_id","OTHER","其他",36,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdeliverable-completion\u002F.skill_id",[56,79,96,105,135,151],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":23},"01M6KKMPWA0B5SCCH766F8M5EA","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[63,64,65,66,67,68,69,70,71,72,73,74,75,76,20,77,78],"write special chars ts check","check","write","filters","Existing","type-checking","for","errors","script","output","type","files","only","template","python","typescript",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":23},"01M6KKMJXVBNVEY3TRK055F4A7","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[86,87,65,76,88,89,20,77,90,91,92,93,94,69,71,95],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper","with",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":23},"01M6KKMEGX9M9NC105J0W3Q5B9","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[65,103,77,69,92,76,104,20,71],"write special chars heredoc","shell",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":116,"publishedAt":23},"01M6KKM8EJ2AATVHZBNB916WT0","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[117,118,119,120,78,121,122,123,124,125,69,126,127,128,129,130,131,132,133,134],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":23},"01M6KKM39PHYK627F19GE2B9XN","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[142,143,144,145,69,146,95,147,148,149,150],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":23},"01M6KKKY7T2P61Y0JH54CDEJKQ","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[158,159,160,161,162,163,20,164,165,166],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]