[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KFBFDAS41HXZMRJD2P406R":3,"skill-same:01M6KFBFDAS41HXZMRJD2P406R":69},{"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":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6KFBFDAS41HXZMRJD2P406R","delegated-file-edit-verification",null,"Verify delegated file-edit results directly in the target workspace before accepting success, and rerun with absolute paths if the delegate's report conflicts with reality.","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\u002Fdelegated-file-edit-verification\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35],"verification","file","edit","delegated file edit verification","report","verify","workspace","delegate","results","conflicts","paths","with","2026-11-10 10:12:30",false,"---\nname: delegated-file-edit-verification\ndescription: Verify delegated file-edit results directly in the target workspace before accepting success, and rerun with absolute paths if the delegate's report conflicts with reality.\n---\n\n# Delegated File Edit Verification\n\nUse this workflow whenever another agent, subprocess, or delegated tool claims it successfully created or modified a file. The goal is to prevent false acceptance of incomplete, misplaced, or incorrect edits.\n\nThis skill is especially useful for structured files such as spreadsheets, CSVs, databases, and generated artifacts, but the same pattern applies to any delegated file-edit task.\n\n## Core principle\n\nNever accept a delegated \"done\" message on summary alone.\n\nImmediately verify the result yourself in the target workspace using direct commands that inspect:\n- file existence\n- exact path\n- expected structure\n- expected size or counts\n- key headers, fields, or identifiers\n\nIf the delegate's summary and your verification disagree, treat the task as incomplete. Re-run the task using absolute paths and explicit acceptance checks.\n\n## When to use this\n\nUse this workflow when:\n- a sub-agent says it wrote or updated a file\n- the task depends on a specific workspace or output location\n- the output is structured and can be checked mechanically\n- prior executions showed path confusion, stale files, or inconsistent summaries\n- correctness matters more than trusting the delegate's narrative\n\n## Procedure\n\n### 1. Record the intended output contract before delegating\n\nBefore handing off the task, write down the minimum facts that must be true if the task succeeds.\n\nInclude:\n- absolute target path\n- required file name\n- required file type\n- expected sheets, tabs, tables, or sections\n- expected row counts or approximate size\n- required headers or columns\n- any sentinel values that should appear\n\nExample contract:\n- file exists at `\u002Fworkspace\u002Fresults\u002Freport.xlsx`\n- workbook contains sheets `summary` and `data`\n- `data` sheet has more than 1,000 rows\n- headers include `id`, `created_at`, `status`\n\nDo not rely on vague goals like \"updated spreadsheet correctly.\"\n\n### 2. Delegate with explicit acceptance criteria\n\nWhen delegating, include:\n- the absolute input path\n- the absolute output path\n- the exact required structure\n- a request to report what was changed\n- a request to include paths actually used\n\nGood delegation prompt:\n- Read `\u002Fworkspace\u002Finput\u002Fsource.xlsx`\n- Write the cleaned workbook to `\u002Fworkspace\u002Foutput\u002Fcleaned.xlsx`\n- Ensure sheets `summary` and `records` exist\n- Ensure `records` includes headers `id`, `date`, `amount`\n- Report the exact absolute path written and row counts per sheet\n\n### 3. Verify immediately after the delegate reports success\n\nDo not move on. Run direct checks in the target workspace right away.\n\nFor all files, verify:\n- the file exists at the expected absolute path\n- modification time is recent\n- file size is plausible\n- there is not a second similarly named file in another directory\n\nFor structured files, verify the internal structure too:\n- workbook sheet names\n- CSV header row\n- row counts\n- required columns\n- sample records or sentinel values\n\n### 4. Prefer direct machine checks over narrative summaries\n\nTrust commands and file inspection, not the delegate's prose.\n\nExamples of useful checks:\n- list the exact file path\n- print sheet names\n- count rows\n- print header names\n- inspect a few sample rows\n- compare timestamps before and after\n\n### 5. If verification conflicts with the delegated summary, mark the task incomplete\n\nExamples of conflicts:\n- delegate says file exists, but it does not\n- delegate claims sheet `data` exists, but workbook contains different sheets\n- reported row count differs materially from actual count\n- expected headers are missing\n- output was written to a relative or unexpected location\n- the delegate inspected one file but wrote another\n\nWhen this happens:\n- do not accept the result\n- state the exact mismatch\n- rerun the task\n- require absolute paths for every input and output\n- require a final report tied to those exact paths\n\n### 6. Re-run with absolute paths and constrained scope\n\nThe most common recovery is to eliminate ambiguity.\n\nOn rerun:\n- provide absolute paths only\n- restate the acceptance contract\n- instruct the delegate to verify its own output before reporting success\n- ask it to print the exact path and structural facts used\n\nExample rerun instruction:\n- Re-run using only these absolute paths:\n  - input: `\u002Fworkspace\u002Finput\u002Fsource.xlsx`\n  - output: `\u002Fworkspace\u002Foutput\u002Fcleaned.xlsx`\n- Before reporting success, verify:\n  - file exists\n  - workbook sheets are `summary` and `records`\n  - `records` row count exceeds 1000\n  - headers include `id`, `date`, `amount`\n- Report the exact output path, sheet names, row counts, and headers\n\n### 7. Re-verify after the rerun\n\nRepeat your independent verification. Only accept the task when your checks match the expected contract.\n\n## Verification checklist\n\nUse this checklist before accepting a delegated file-edit result:\n\n- [ ] I know the exact absolute output path.\n- [ ] I confirmed the file exists there.\n- [ ] I checked modification time or other evidence it was freshly written.\n- [ ] I verified the file's internal structure.\n- [ ] I checked row counts, record counts, or comparable size indicators.\n- [ ] I checked key headers, fields, or identifiers.\n- [ ] My direct inspection matches the delegate's report.\n- [ ] If there was any mismatch, I reran with absolute paths.\n\n## Examples\n\n## Example: generic file existence check\n\nUse direct shell checks first.\n\n```text\nls -l \u002Fworkspace\u002Foutput\u002Fresult.xlsx\nstat \u002Fworkspace\u002Foutput\u002Fresult.xlsx\nfind \u002Fworkspace -name 'result.xlsx' -o -name '*result*'\n```\n\nInterpretation:\n- confirm the file exists where expected\n- compare timestamps and sizes\n- detect misplaced outputs\n\n## Example: CSV verification\n\n```text\ntest -f \u002Fworkspace\u002Foutput\u002Fdata.csv\nhead -n 3 \u002Fworkspace\u002Foutput\u002Fdata.csv\npython - \u003C\u003C'PY'\nimport csv\npath = \"\u002Fworkspace\u002Foutput\u002Fdata.csv\"\nwith open(path, newline=\"\") as f:\n    reader = csv.reader(f)\n    rows = list(reader)\nprint(\"rows_including_header:\", len(rows))\nprint(\"headers:\", rows[0])\nPY\n```\n\nCheck:\n- file exists\n- headers are correct\n- row count is plausible\n\n## Example: spreadsheet verification\n\n```text\npython - \u003C\u003C'PY'\nfrom openpyxl import load_workbook\npath = \"\u002Fworkspace\u002Foutput\u002Freport.xlsx\"\nwb = load_workbook(path, read_only=True, data_only=True)\nprint(\"sheets:\", wb.sheetnames)\nfor ws in wb.worksheets:\n    print(ws.title, ws.max_row, ws.max_column)\n    headers = [c for c in next(ws.iter_rows(min_row=1, max_row=1, values_only=True))]\n    print(\"headers:\", headers)\nPY\n```\n\nCheck:\n- expected sheets exist\n- row counts are plausible\n- key headers are present\n\n## Example: delegate summary conflict\n\nDelegate says:\n- wrote `\u002Fworkspace\u002Foutput\u002Freport.xlsx`\n- created sheet `data`\n- row count is 2,500\n\nYour verification shows:\n- file exists at `.\u002Freport.xlsx` instead\n- workbook has sheets `Sheet1` and `summary`\n- no `data` sheet exists\n\nCorrect response:\n- mark the task incomplete\n- do not accept the delegated summary\n- rerun using absolute paths and explicit checks\n\n## Recommended response template when verification fails\n\nUse a concise recovery message like this:\n\n- Your report conflicts with direct verification.\n- Expected output: `\u002Fabsolute\u002Fpath\u002Fto\u002Foutput.ext`\n- Observed issue: file missing \u002F wrong sheets \u002F wrong row count \u002F missing headers\n- Treating task as incomplete.\n- Re-run using only absolute paths.\n- Before reporting success, include:\n  - exact output path\n  - structure summary\n  - counts\n  - key headers\n\n## Anti-patterns to avoid\n\nDo not:\n- accept \"done\" without checking the file yourself\n- trust relative paths when workspace ambiguity is possible\n- rely on a delegate's sample output without checking the actual artifact\n- accept a file just because a similarly named file exists somewhere\n- assume a workbook or dataset matches the report without verifying sheets and counts\n- treat conflicting evidence as \"probably fine\"\n\n## Why this works\n\nDelegated file-edit failures often come from:\n- writing to the wrong directory\n- inspecting a different file than the one modified\n- stale files from earlier runs\n- mistaken row counts or sheet names\n- overconfident summaries that skip verification\n\nThis workflow catches those failures early by making acceptance depend on direct evidence in the target workspace.\n\n## Success criterion\n\nA delegated file-edit task is complete only when:\n1. the expected artifact exists at the exact intended path, and\n2. independent verification confirms its required structure and content, and\n3. that verification agrees with the delegated report.\n\nIf any of these fail, rerun with absolute paths.","# Delegated File Edit Verification\n\nUse this workflow whenever another agent, subprocess, or delegated tool claims it successfully created or modified a file. The goal is to prevent false acceptance of incomplete, misplaced, or incorrect edits.\n\nThis skill is especially useful for structured files such as spreadsheets, CSVs, databases, and generated artifacts, but the same pattern applies to any delegated file-edit task.\n\n## Core principle\n\nNever accept a delegated \"done\" message on summary alone.\n\nImmediately verify the result yourself in the target workspace using direct commands that inspect:\n- file existence\n- exact path\n- expected structure\n- expected size or counts\n- key headers, fields, or identifiers\n\nIf the delegate's summary and your verification disagree, treat the task as incomplete. Re-run the task using absolute paths and explicit acceptance checks.\n\n## When to use this\n\nUse this workflow when:\n- a sub-agent says it wrote or updated a file\n- the task depends on a specific workspace or output location\n- the output is structured and can be checked mechanically\n- prior executions showed path confusion, stale files, or inconsistent summaries\n- correctness matters more than trusting the delegate's narrative\n\n## Procedure\n\n### 1. Record the intended output contract before delegating\n\nBefore handing off the task, write down the minimum facts that must be true if the task succeeds.\n\nInclude:\n- absolute target path\n- required file name\n- required file type\n- expected sheets, tabs, tables, or sections\n- expected row counts or approximate size\n- required headers or columns\n- any sentinel values that should appear\n\nExample contract:\n- file exists at `\u002Fworkspace\u002Fresults\u002Freport.xlsx`\n- workbook contains sheets `summary` and `data`\n- `data` sheet has more than 1,000 rows\n- headers include `id`, `created_at`, `status`\n\nDo not rely on vague goals like \"updated spreadsheet correctly.\"\n\n### 2. Delegate with explicit acceptance criteria\n\nWhen delegating, include:\n- the absolute input path\n- the absolute output path\n- the exact required structure\n- a request to report what was changed\n- a request to include paths actually used\n\nGood delegation prompt:\n- Read `\u002Fworkspace\u002Finput\u002Fsource.xlsx`\n- Write the cleaned workbook to `\u002Fworkspace\u002Foutput\u002Fcleaned.xlsx`\n- Ensure sheets `summary` and `records` exist\n- Ensure `records` includes headers `id`, `date`, `amount`\n- Report the exact absolute path written and row counts per sheet\n\n### 3. Verify immediately after the delegate reports success\n\nDo not move on. Run direct checks in the target workspace right away.\n\nFor all files, verify:\n- the file exists at the expected absolute path\n- modification time is recent\n- file size is plausible\n- there is not a second similarly named file in another directory\n\nFor structured files, verify the internal structure too:\n- workbook sheet names\n- CSV header row\n- row counts\n- required columns\n- sample records or sentinel values\n\n### 4. Prefer direct machine checks over narrative summaries\n\nTrust commands and file inspection, not the delegate's prose.\n\nExamples of useful checks:\n- list the exact file path\n- print sheet names\n- count rows\n- print header names\n- inspect a few sample rows\n- compare timestamps before and after\n\n### 5. If verification conflicts with the delegated summary, mark the task incomplete\n\nExamples of conflicts:\n- delegate says file exists, but it does not\n- delegate claims sheet `data` exists, but workbook contains different sheets\n- reported row count differs materially from actual count\n- expected headers are missing\n- output was written to a relative or unexpected location\n- the delegate inspected one file but wrote another\n\nWhen this happens:\n- do not accept the result\n- state the exact mismatch\n- rerun the task\n- require absolute paths for every input and output\n- require a final report tied to those exact paths\n\n### 6. Re-run with absolute paths and constrained scope\n\nThe most common recovery is to eliminate ambiguity.\n\nOn rerun:\n- provide absolute paths only\n- restate the acceptance contract\n- instruct the delegate to verify its own output before reporting success\n- ask it to print the exact path and structural facts used\n\nExample rerun instruction:\n- Re-run using only these absolute paths:\n  - input: `\u002Fworkspace\u002Finput\u002Fsource.xlsx`\n  - output: `\u002Fworkspace\u002Foutput\u002Fcleaned.xlsx`\n- Before reporting success, verify:\n  - file exists\n  - workbook sheets are `summary` and `records`\n  - `records` row count exceeds 1000\n  - headers include `id`, `date`, `amount`\n- Report the exact output path, sheet names, row counts, and headers\n\n### 7. Re-verify after the rerun\n\nRepeat your independent verification. Only accept the task when your checks match the expected contract.\n\n## Verification checklist\n\nUse this checklist before accepting a delegated file-edit result:\n\n- [ ] I know the exact absolute output path.\n- [ ] I confirmed the file exists there.\n- [ ] I checked modification time or other evidence it was freshly written.\n- [ ] I verified the file's internal structure.\n- [ ] I checked row counts, record counts, or comparable size indicators.\n- [ ] I checked key headers, fields, or identifiers.\n- [ ] My direct inspection matches the delegate's report.\n- [ ] If there was any mismatch, I reran with absolute paths.\n\n## Examples\n\n## Example: generic file existence check\n\nUse direct shell checks first.\n\n```text\nls -l \u002Fworkspace\u002Foutput\u002Fresult.xlsx\nstat \u002Fworkspace\u002Foutput\u002Fresult.xlsx\nfind \u002Fworkspace -name 'result.xlsx' -o -name '*result*'\n```\n\nInterpretation:\n- confirm the file exists where expected\n- compare timestamps and sizes\n- detect misplaced outputs\n\n## Example: CSV verification\n\n```text\ntest -f \u002Fworkspace\u002Foutput\u002Fdata.csv\nhead -n 3 \u002Fworkspace\u002Foutput\u002Fdata.csv\npython - \u003C\u003C'PY'\nimport csv\npath = \"\u002Fworkspace\u002Foutput\u002Fdata.csv\"\nwith open(path, newline=\"\") as f:\n    reader = csv.reader(f)\n    rows = list(reader)\nprint(\"rows_including_header:\", len(rows))\nprint(\"headers:\", rows[0])\nPY\n```\n\nCheck:\n- file exists\n- headers are correct\n- row count is plausible\n\n## Example: spreadsheet verification\n\n```text\npython - \u003C\u003C'PY'\nfrom openpyxl import load_workbook\npath = \"\u002Fworkspace\u002Foutput\u002Freport.xlsx\"\nwb = load_workbook(path, read_only=True, data_only=True)\nprint(\"sheets:\", wb.sheetnames)\nfor ws in wb.worksheets:\n    print(ws.title, ws.max_row, ws.max_column)\n    headers = [c for c in next(ws.iter_rows(min_row=1, max_row=1, values_only=True))]\n    print(\"headers:\", headers)\nPY\n```\n\nCheck:\n- expected sheets exist\n- row counts are plausible\n- key headers are present\n\n## Example: delegate summary conflict\n\nDelegate says:\n- wrote `\u002Fworkspace\u002Foutput\u002Freport.xlsx`\n- created sheet `data`\n- row count is 2,500\n\nYour verification shows:\n- file exists at `.\u002Freport.xlsx` instead\n- workbook has sheets `Sheet1` and `summary`\n- no `data` sheet exists\n\nCorrect response:\n- mark the task incomplete\n- do not accept the delegated summary\n- rerun using absolute paths and explicit checks\n\n## Recommended response template when verification fails\n\nUse a concise recovery message like this:\n\n- Your report conflicts with direct verification.\n- Expected output: `\u002Fabsolute\u002Fpath\u002Fto\u002Foutput.ext`\n- Observed issue: file missing \u002F wrong sheets \u002F wrong row count \u002F missing headers\n- Treating task as incomplete.\n- Re-run using only absolute paths.\n- Before reporting success, include:\n  - exact output path\n  - structure summary\n  - counts\n  - key headers\n\n## Anti-patterns to avoid\n\nDo not:\n- accept \"done\" without checking the file yourself\n- trust relative paths when workspace ambiguity is possible\n- rely on a delegate's sample output without checking the actual artifact\n- accept a file just because a similarly named file exists somewhere\n- assume a workbook or dataset matches the report without verifying sheets and counts\n- treat conflicting evidence as \"probably fine\"\n\n## Why this works\n\nDelegated file-edit failures often come from:\n- writing to the wrong directory\n- inspecting a different file than the one modified\n- stale files from earlier runs\n- mistaken row counts or sheet names\n- overconfident summaries that skip verification\n\nThis workflow catches those failures early by making acceptance depend on direct evidence in the target workspace.\n\n## Success criterion\n\nA delegated file-edit task is complete only when:\n1. the expected artifact exists at the exact intended path, and\n2. independent verification confirms its required structure and content, and\n3. that verification agrees with the delegated report.\n\nIf any of these fail, rerun with absolute paths.",{"name":5,"description":7},"main","af1b40a42167d09c30b3a63000aa14ace4c1e229","gdpval_bench\u002Fskills\u002Fdelegated-file-edit-verification","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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add xyliu-cs\u002FOpenSpace-GDPval --skill delegated-file-edit-verification",{"tool":55,"command":56},"bunx","bunx skills add xyliu-cs\u002FOpenSpace-GDPval --skill delegated-file-edit-verification",{"tool":58,"command":59},"pnpm","pnpm dlx skills add xyliu-cs\u002FOpenSpace-GDPval --skill delegated-file-edit-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdelegated-file-edit-verification\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},".skill_id","OTHER","其他",46,"https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fdelegated-file-edit-verification\u002F.skill_id",[70,83,91,106,130,150],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":36},"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",[],[77,78,79,80,81,82],"zip export deliverable","zip","export","deliverables","codebase","as",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":36},"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",[],[90,78,80,81,82],"zip deliverable finalization",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":36},"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",[],[98,99,100,101,102,35,103,104,82,105],"failure analysis","ZeRO","analysis","iteration","zero iteration failure analysis","issues","execution","system",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":117,"publishedAt":36},"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",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[118,119,25,28,120,121,122,123,124,125,126,127,128,129],"fallback","write","write file fallback report","domain","professional","sources","retrieval","generate","embedded","documents","data","knowledge",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":36},"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",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,35,118,141,142,143,127,125,25,144,145,146,119,147,122,148,149],"fallback doc with delegation","doc","delegation","shell","markdown","tool","text","simple","formats","for",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":36},"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",[156],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[118,28,158,159,125,25,160,161,119,162,163,124,35,164,127],"context","context anchored fallback report","Guardrails","Tools","task","drift","context drift"]