[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KFB024ZHRRNWWWS07RQTQW":3,"skill-same:01M6KFB024ZHRRNWWWS07RQTQW":63},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6KFB024ZHRRNWWWS07RQTQW","comprehensive-soap-note",null,"Generate complete medical SOAP notes with all four sections in a single comprehensive file write operation","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\u002Fcreate-soap-note-merged\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"soap","note","comprehensive soap note","notes","generate","file","write","medical","complete","operation","with","2026-11-10 10:12:30",false,"---\nname: comprehensive-soap-note\ndescription: Generate complete medical SOAP notes with all four sections in a single comprehensive file write operation\n---\n\n# Comprehensive SOAP Note Creation\n\nThis skill defines the workflow for creating structured medical documentation (SOAP notes) by writing all required sections to a file in one comprehensive operation. This ensures completeness, consistency, and efficiency in clinical documentation.\n\n## When to Use\n\nUse this skill when you need to create:\n- Medical visit documentation\n- Patient encounter records\n- Clinical meeting notes\n- Healthcare follow-up documentation\n\nthat follow the standard SOAP (Subjective, Objective, Assessment, Plan) format.\n\n## Objective\n\nProduce a complete medical visit record containing all four SOAP sections without fragmenting the output across multiple files or incomplete drafts. The entire note should be written in a single operation to maintain consistency.\n\n## Prerequisites\n\nBefore creating the SOAP note, gather:\n- **Patient demographics**: age, gender, patient ID\n- **Visit details**: date, provider name, reason for visit\n- **Clinical data**: vitals, symptoms, exam findings, medical history\n- **Diagnostic results**: labs, imaging (if available)\n\n## Core Technique\n\nWrite the **entire SOAP note in one comprehensive file write** rather than building it incrementally. This ensures:\n- All sections are complete before writing\n- Consistency across the document\n- Reduced overhead from multiple write operations\n- No risk of partial or fragmented notes\n\n## Required Sections\n\nEvery SOAP note must include these four components:\n\n### 1. Subjective (S)\nPatient-reported information including:\n- **Chief Complaint (CC)**: Patient's primary reason for visit (in their own words when possible)\n- **History of Present Illness (HPI)**: Detailed narrative of current symptoms (use OLDCARTS or similar framework: Onset, Location, Duration, Characteristics, Aggravating\u002FRelieving factors, Timing, Severity)\n- **Past Medical History (PMH)**: Relevant conditions, surgeries, medications, allergies\n- **Family History (FH)**: Pertinent family medical history\n- **Social History (SH)**: Relevant social context (occupation, lifestyle, habits)\n- **Review of Systems (ROS)**: Systematic symptom review if applicable\n\n### 2. Objective (O)\nClinician-observed and measured data:\n- **Vital Signs**: BP, HR, RR, Temp, SpO2, weight, height (always include concrete values)\n- **Physical Examination**: System-by-system findings (HEENT, Cardiovascular, Respiratory, Abdomen, Neurological, Musculoskeletal, Skin, etc.)\n- **Diagnostic Data**: Lab results, imaging findings, EKG, other test results if available\n\n### 3. Assessment (A)\nClinical synthesis and diagnosis:\n- **Primary Diagnosis**: Main clinical diagnosis (include ICD code if applicable)\n- **Differential Diagnoses**: Alternative considerations (at least 1-2 alternatives)\n- **Clinical Reasoning**: Brief justification linking subjective and objective findings to the assessment\n- **Problem List**: Current active problems if applicable\n\n### 4. Plan (P)\nActionable next steps:\n- **Management\u002FTreatment**: Specific interventions, procedures, therapies\n- **Medications**: Prescriptions with dose, frequency, route, duration\n- **Follow-up**: Timeline and conditions for return visit\n- **Patient Education**: Instructions, lifestyle modifications, warning signs to watch\n- **Referrals**: Specialist referrals if needed\n\n## Execution Pattern\n\n```\n1. Gather all patient information and clinical data\n2. Structure content into the four SOAP sections (do not skip any section)\n3. Write the complete note to file in ONE operation\n4. Verify all four sections are present and contain substantive content\n```\n\n## Template Example\n\n```markdown\n# SOAP Note - [Patient Name\u002FID]\n## Date: [Visit Date]\n## Provider: [Provider Name]\n\n## SUBJECTIVE\n### Chief Complaint\n[Patient's reason for visit in their own words]\n\n### History of Present Illness\n[Detailed symptom narrative using OLDCARTS framework]\n\n### Past Medical History\n[Relevant conditions, surgeries, medications, allergies]\n\n### Family History\n[Relevant family medical history]\n\n### Social History\n[Occupation, lifestyle, habits, social context]\n\n## OBJECTIVE\n### Vital Signs\n- BP: [value] mmHg\n- HR: [value] bpm\n- RR: [value] breaths\u002Fmin\n- Temp: [value] °F\u002F°C\n- SpO2: [value]%\n- Weight: [value] kg\u002Flbs\n- Height: [value] cm\u002Fft\n\n### Physical Examination\n- **HEENT**: [findings]\n- **Cardiovascular**: [findings]\n- **Respiratory**: [findings]\n- **Abdomen**: [findings]\n- **Neurological**: [findings]\n- **Musculoskeletal**: [findings]\n- **Skin**: [findings]\n\n### Diagnostic Data\n[Labs, imaging, other test results with dates and values]\n\n## ASSESSMENT\n### Primary Diagnosis\n[Diagnosis with ICD code if applicable]\n\n### Differential Diagnoses\n1. [Alternative diagnosis 1]\n2. [Alternative diagnosis 2]\n\n### Clinical Reasoning\n[Brief explanation linking findings to diagnosis]\n\n## PLAN\n### Management\n- [Medications with dose\u002Ffrequency\u002Fduration]\n- [Procedures\u002Finterventions]\n- [Referrals if needed]\n\n### Follow-up\n[Timeline and conditions for return visit]\n\n### Patient Education\n[Instructions, lifestyle modifications, warning signs to watch]\n```\n\n## File Naming\n\nSave the complete note using a consistent naming convention:\n- `soap_note_\u003Cpatient_id>_\u003Cdate>.md` or\n- `soap_note_\u003Cpatient_id>_\u003Cdate>.txt`\n\n## Best Practices\n\n1. **Completeness First**: Include all four sections before writing—do not build incrementally\n2. **Specificity**: Use concrete values (vitals, dates, doses) rather than placeholders\n3. **Clinical Accuracy**: Ensure assessment logically follows from subjective and objective data\n4. **Actionable Plan**: Plan items should be specific and implementable\n5. **No Section Omission**: If data is genuinely missing, explicitly state \"Information not provided\" or \"Not applicable\" rather than skipping the section\n6. **Privacy**: Ensure no real PHI (Protected Health Information) is exposed in public logs if not authorized\n7. **Clarity**: Use medical terminology appropriately but keep patient instructions clear and understandable\n8. **Single Write Operation**: Aim to generate the full document in one iteration to reduce overhead and maintain consistency\n\n## Common Mistakes to Avoid\n\n- Writing sections separately across multiple iterations or files\n- Leaving sections incomplete or with placeholder text like `[insert here]`\n- Omitting differential diagnoses in the Assessment section\n- Creating vague, non-actionable Plan items\n- Missing vital signs or key physical exam findings in Objective\n- Skipping sections entirely when data is sparse (instead mark as \"not applicable\")\n\n## Troubleshooting\n\n### Missing Data\nIf specific clinical data is missing, explicitly state \"Information not provided\" or \"Deferred\" in the relevant section rather than skipping the section entirely.\n\n### File Size Issues\nComprehensive SOAP notes typically range 3,000-10,000+ characters depending on complexity. If the note is exceptionally long:\n- Ensure the file write command supports the content length\n- Consider using markdown format for better structure\n- Verify the complete content was written (check file size after write)\n\n### Incomplete Sections\nAfter writing, verify all four headers (Subjective, Objective, Assessment, Plan) exist and contain substantive content. If any section is incomplete, rewrite the entire note in one operation.\n\n## Quality Checklist\n\nBefore considering the SOAP note complete, verify:\n- [ ] All four SOAP sections are present\n- [ ] Subjective includes CC, HPI, and relevant history\n- [ ] Objective includes vitals with concrete values\n- [ ] Objective includes physical exam findings by system\n- [ ] Assessment includes primary diagnosis AND at least one differential\n- [ ] Plan includes specific, actionable items (medications, follow-up, education)\n- [ ] No placeholder text like `[insert here]` unless genuinely unavailable\n- [ ] File was written in a single operation\n- [ ] File naming follows the convention\n\n## Example File Size Reference\n\n- Minimal SOAP note: ~2,000-3,000 characters\n- Standard SOAP note: ~4,000-7,000 characters\n- Complex SOAP note: ~8,000-12,000+ characters\n","# Comprehensive SOAP Note Creation\n\nThis skill defines the workflow for creating structured medical documentation (SOAP notes) by writing all required sections to a file in one comprehensive operation. This ensures completeness, consistency, and efficiency in clinical documentation.\n\n## When to Use\n\nUse this skill when you need to create:\n- Medical visit documentation\n- Patient encounter records\n- Clinical meeting notes\n- Healthcare follow-up documentation\n\nthat follow the standard SOAP (Subjective, Objective, Assessment, Plan) format.\n\n## Objective\n\nProduce a complete medical visit record containing all four SOAP sections without fragmenting the output across multiple files or incomplete drafts. The entire note should be written in a single operation to maintain consistency.\n\n## Prerequisites\n\nBefore creating the SOAP note, gather:\n- **Patient demographics**: age, gender, patient ID\n- **Visit details**: date, provider name, reason for visit\n- **Clinical data**: vitals, symptoms, exam findings, medical history\n- **Diagnostic results**: labs, imaging (if available)\n\n## Core Technique\n\nWrite the **entire SOAP note in one comprehensive file write** rather than building it incrementally. This ensures:\n- All sections are complete before writing\n- Consistency across the document\n- Reduced overhead from multiple write operations\n- No risk of partial or fragmented notes\n\n## Required Sections\n\nEvery SOAP note must include these four components:\n\n### 1. Subjective (S)\nPatient-reported information including:\n- **Chief Complaint (CC)**: Patient's primary reason for visit (in their own words when possible)\n- **History of Present Illness (HPI)**: Detailed narrative of current symptoms (use OLDCARTS or similar framework: Onset, Location, Duration, Characteristics, Aggravating\u002FRelieving factors, Timing, Severity)\n- **Past Medical History (PMH)**: Relevant conditions, surgeries, medications, allergies\n- **Family History (FH)**: Pertinent family medical history\n- **Social History (SH)**: Relevant social context (occupation, lifestyle, habits)\n- **Review of Systems (ROS)**: Systematic symptom review if applicable\n\n### 2. Objective (O)\nClinician-observed and measured data:\n- **Vital Signs**: BP, HR, RR, Temp, SpO2, weight, height (always include concrete values)\n- **Physical Examination**: System-by-system findings (HEENT, Cardiovascular, Respiratory, Abdomen, Neurological, Musculoskeletal, Skin, etc.)\n- **Diagnostic Data**: Lab results, imaging findings, EKG, other test results if available\n\n### 3. Assessment (A)\nClinical synthesis and diagnosis:\n- **Primary Diagnosis**: Main clinical diagnosis (include ICD code if applicable)\n- **Differential Diagnoses**: Alternative considerations (at least 1-2 alternatives)\n- **Clinical Reasoning**: Brief justification linking subjective and objective findings to the assessment\n- **Problem List**: Current active problems if applicable\n\n### 4. Plan (P)\nActionable next steps:\n- **Management\u002FTreatment**: Specific interventions, procedures, therapies\n- **Medications**: Prescriptions with dose, frequency, route, duration\n- **Follow-up**: Timeline and conditions for return visit\n- **Patient Education**: Instructions, lifestyle modifications, warning signs to watch\n- **Referrals**: Specialist referrals if needed\n\n## Execution Pattern\n\n```\n1. Gather all patient information and clinical data\n2. Structure content into the four SOAP sections (do not skip any section)\n3. Write the complete note to file in ONE operation\n4. Verify all four sections are present and contain substantive content\n```\n\n## Template Example\n\n```markdown\n# SOAP Note - [Patient Name\u002FID]\n## Date: [Visit Date]\n## Provider: [Provider Name]\n\n## SUBJECTIVE\n### Chief Complaint\n[Patient's reason for visit in their own words]\n\n### History of Present Illness\n[Detailed symptom narrative using OLDCARTS framework]\n\n### Past Medical History\n[Relevant conditions, surgeries, medications, allergies]\n\n### Family History\n[Relevant family medical history]\n\n### Social History\n[Occupation, lifestyle, habits, social context]\n\n## OBJECTIVE\n### Vital Signs\n- BP: [value] mmHg\n- HR: [value] bpm\n- RR: [value] breaths\u002Fmin\n- Temp: [value] °F\u002F°C\n- SpO2: [value]%\n- Weight: [value] kg\u002Flbs\n- Height: [value] cm\u002Fft\n\n### Physical Examination\n- **HEENT**: [findings]\n- **Cardiovascular**: [findings]\n- **Respiratory**: [findings]\n- **Abdomen**: [findings]\n- **Neurological**: [findings]\n- **Musculoskeletal**: [findings]\n- **Skin**: [findings]\n\n### Diagnostic Data\n[Labs, imaging, other test results with dates and values]\n\n## ASSESSMENT\n### Primary Diagnosis\n[Diagnosis with ICD code if applicable]\n\n### Differential Diagnoses\n1. [Alternative diagnosis 1]\n2. [Alternative diagnosis 2]\n\n### Clinical Reasoning\n[Brief explanation linking findings to diagnosis]\n\n## PLAN\n### Management\n- [Medications with dose\u002Ffrequency\u002Fduration]\n- [Procedures\u002Finterventions]\n- [Referrals if needed]\n\n### Follow-up\n[Timeline and conditions for return visit]\n\n### Patient Education\n[Instructions, lifestyle modifications, warning signs to watch]\n```\n\n## File Naming\n\nSave the complete note using a consistent naming convention:\n- `soap_note_\u003Cpatient_id>_\u003Cdate>.md` or\n- `soap_note_\u003Cpatient_id>_\u003Cdate>.txt`\n\n## Best Practices\n\n1. **Completeness First**: Include all four sections before writing—do not build incrementally\n2. **Specificity**: Use concrete values (vitals, dates, doses) rather than placeholders\n3. **Clinical Accuracy**: Ensure assessment logically follows from subjective and objective data\n4. **Actionable Plan**: Plan items should be specific and implementable\n5. **No Section Omission**: If data is genuinely missing, explicitly state \"Information not provided\" or \"Not applicable\" rather than skipping the section\n6. **Privacy**: Ensure no real PHI (Protected Health Information) is exposed in public logs if not authorized\n7. **Clarity**: Use medical terminology appropriately but keep patient instructions clear and understandable\n8. **Single Write Operation**: Aim to generate the full document in one iteration to reduce overhead and maintain consistency\n\n## Common Mistakes to Avoid\n\n- Writing sections separately across multiple iterations or files\n- Leaving sections incomplete or with placeholder text like `[insert here]`\n- Omitting differential diagnoses in the Assessment section\n- Creating vague, non-actionable Plan items\n- Missing vital signs or key physical exam findings in Objective\n- Skipping sections entirely when data is sparse (instead mark as \"not applicable\")\n\n## Troubleshooting\n\n### Missing Data\nIf specific clinical data is missing, explicitly state \"Information not provided\" or \"Deferred\" in the relevant section rather than skipping the section entirely.\n\n### File Size Issues\nComprehensive SOAP notes typically range 3,000-10,000+ characters depending on complexity. If the note is exceptionally long:\n- Ensure the file write command supports the content length\n- Consider using markdown format for better structure\n- Verify the complete content was written (check file size after write)\n\n### Incomplete Sections\nAfter writing, verify all four headers (Subjective, Objective, Assessment, Plan) exist and contain substantive content. If any section is incomplete, rewrite the entire note in one operation.\n\n## Quality Checklist\n\nBefore considering the SOAP note complete, verify:\n- [ ] All four SOAP sections are present\n- [ ] Subjective includes CC, HPI, and relevant history\n- [ ] Objective includes vitals with concrete values\n- [ ] Objective includes physical exam findings by system\n- [ ] Assessment includes primary diagnosis AND at least one differential\n- [ ] Plan includes specific, actionable items (medications, follow-up, education)\n- [ ] No placeholder text like `[insert here]` unless genuinely unavailable\n- [ ] File was written in a single operation\n- [ ] File naming follows the convention\n\n## Example File Size Reference\n\n- Minimal SOAP note: ~2,000-3,000 characters\n- Standard SOAP note: ~4,000-7,000 characters\n- Complex SOAP note: ~8,000-12,000+ characters\n",{"name":5,"description":7},"main","af1b40a42167d09c30b3a63000aa14ace4c1e229","gdpval_bench\u002Fskills\u002Fcreate-soap-note-merged","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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add xyliu-cs\u002FOpenSpace-GDPval --skill comprehensive-soap-note",{"tool":49,"command":50},"bunx","bunx skills add xyliu-cs\u002FOpenSpace-GDPval --skill comprehensive-soap-note",{"tool":52,"command":53},"pnpm","pnpm dlx skills add xyliu-cs\u002FOpenSpace-GDPval --skill comprehensive-soap-note","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fcreate-soap-note-merged\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},".skill_id","OTHER","其他",37,"https:\u002F\u002Fgithub.com\u002Fxyliu-cs\u002FOpenSpace-GDPval\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fcreate-soap-note-merged\u002F.skill_id",[64,77,85,100,123,145],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":30},"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",[],[71,72,73,74,75,76],"zip export deliverable","zip","export","deliverables","codebase","as",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":30},"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",[],[84,72,74,75,76],"zip deliverable finalization",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":30},"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",[],[92,93,94,95,96,29,97,98,76,99],"failure analysis","ZeRO","analysis","iteration","zero iteration failure analysis","issues","execution","system",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":30},"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",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[112,25,24,113,114,115,116,117,118,23,119,120,121,122],"fallback","report","write file fallback report","domain","professional","sources","retrieval","embedded","documents","data","knowledge",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":134,"publishedAt":30},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[135,29,112,136,137,138,120,23,24,139,140,141,25,142,116,143,144],"fallback doc with delegation","doc","delegation","shell","markdown","tool","text","simple","formats","for",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":30},"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",[151],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[112,113,153,154,23,24,155,156,25,157,158,118,29,159,120],"context","context anchored fallback report","Guardrails","Tools","task","drift","context drift"]