[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XBEWE5ASN8254AX7GA92P6":3,"skill-same:01M6XBEWE5ASN8254AX7GA92P6":61},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":13,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6XBEWE5ASN8254AX7GA92P6","create-soap-note",null,"Generate structured medical SOAP notes with all required sections in a single comprehensive file write.","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\u002Fcreate-soap-note\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29],"create","soap","note","create soap note","notes","generate","file","write","structured","medical","with","single","2026-11-10 10:12:30",false,"---\nname: create-soap-note\ndescription: Generate structured medical SOAP notes with all required sections in a single comprehensive file write.\n---\n\n# Create SOAP Note\n\nThis skill defines the workflow for creating structured medical documentation (SOAP notes) by writing comprehensive content directly to a file. It ensures all standard sections are included and properly formatted.\n\n## Objective\n\nProduce a complete medical visit record containing Subjective, Objective, Assessment, and Plan sections without fragmenting the output across multiple files or incomplete drafts.\n\n## Prerequisites\n\n- Patient demographic information (age, gender, ID).\n- Visit details (date, provider, reason for visit).\n- Clinical data (vitals, symptoms, exam findings, history).\n\n## Workflow Steps\n\n### 1. Prepare Content Structure\nOrganize the note into the four standard SOAP sections. Do not omit any section even if data is sparse (note \"not applicable\" or \"deferred\" where appropriate).\n\n### 2. Draft Comprehensive Content\nWrite the full content for each section in one continuous operation. Avoid placeholders like `[insert here]` unless data is genuinely missing and must be flagged for follow-up.\n\n- **Subjective (S):**\n  - Chief Complaint (CC)\n  - History of Present Illness (HPI)\n  - Past Medical History (PMH)\n  - Family\u002FSocial History (FH\u002FSH)\n  - Review of Systems (ROS)\n- **Objective (O):**\n  - Vitals (BP, HR, Temp, Resp, O2 Sat, Weight\u002FHeight)\n  - Physical Exam (by system)\n  - Diagnostic Results (Labs, Imaging)\n- **Assessment (A):**\n  - Primary Diagnosis\n  - Differential Diagnoses\n  - Problem List\n- **Plan (P):**\n  - Management\u002FTreatment\n  - Medications\n  - Follow-up Instructions\n  - Patient Education\n\n### 3. Write to File\nSave the complete note to a single file (e.g., `soap_note_\u003Cpatient_id>_\u003Cdate>.md` or `.txt`). Ensure the file is saved in one write operation to maintain consistency.\n\n### 4. Review for Completeness\nVerify that all four headers exist and contain substantive content.\n\n## Template Example\n\n```markdown\n# SOAP Note - [Patient Name] - [Date]\n\n## Subjective\n**Chief Complaint:** [Reason for visit]\n**HPI:** [Detailed history]\n**PMH:** [Conditions, surgeries]\n**Social\u002FFamily History:** [Relevant details]\n\n## Objective\n**Vitals:** [List values]\n**Physical Exam:** [Findings by system]\n**Labs\u002FImaging:** [Results]\n\n## Assessment\n**Diagnoses:**\n1. [Primary Diagnosis]\n2. [Differential]\n\n## Plan\n**Management:** [Steps taken]\n**Medications:** [Prescriptions]\n**Follow-up:** [Timeline]\n**Education:** [Instructions given]\n```\n\n## Best Practices\n\n- **Privacy:** Ensure no real PHI (Protected Health Information) is exposed in public logs if not authorized.\n- **Clarity:** Use medical terminology appropriately but keep patient instructions clear.\n- **Efficiency:** Aim to generate the full document in one iteration to reduce overhead.\n\n## Troubleshooting\n\n- **Missing Data:** If specific clinical data is missing, explicitly state \"Information not provided\" in the relevant section rather than skipping the section.\n- **File Size:** If the note is exceptionally long, ensure the file write command supports the content length.","# Create SOAP Note\n\nThis skill defines the workflow for creating structured medical documentation (SOAP notes) by writing comprehensive content directly to a file. It ensures all standard sections are included and properly formatted.\n\n## Objective\n\nProduce a complete medical visit record containing Subjective, Objective, Assessment, and Plan sections without fragmenting the output across multiple files or incomplete drafts.\n\n## Prerequisites\n\n- Patient demographic information (age, gender, ID).\n- Visit details (date, provider, reason for visit).\n- Clinical data (vitals, symptoms, exam findings, history).\n\n## Workflow Steps\n\n### 1. Prepare Content Structure\nOrganize the note into the four standard SOAP sections. Do not omit any section even if data is sparse (note \"not applicable\" or \"deferred\" where appropriate).\n\n### 2. Draft Comprehensive Content\nWrite the full content for each section in one continuous operation. Avoid placeholders like `[insert here]` unless data is genuinely missing and must be flagged for follow-up.\n\n- **Subjective (S):**\n  - Chief Complaint (CC)\n  - History of Present Illness (HPI)\n  - Past Medical History (PMH)\n  - Family\u002FSocial History (FH\u002FSH)\n  - Review of Systems (ROS)\n- **Objective (O):**\n  - Vitals (BP, HR, Temp, Resp, O2 Sat, Weight\u002FHeight)\n  - Physical Exam (by system)\n  - Diagnostic Results (Labs, Imaging)\n- **Assessment (A):**\n  - Primary Diagnosis\n  - Differential Diagnoses\n  - Problem List\n- **Plan (P):**\n  - Management\u002FTreatment\n  - Medications\n  - Follow-up Instructions\n  - Patient Education\n\n### 3. Write to File\nSave the complete note to a single file (e.g., `soap_note_\u003Cpatient_id>_\u003Cdate>.md` or `.txt`). Ensure the file is saved in one write operation to maintain consistency.\n\n### 4. Review for Completeness\nVerify that all four headers exist and contain substantive content.\n\n## Template Example\n\n```markdown\n# SOAP Note - [Patient Name] - [Date]\n\n## Subjective\n**Chief Complaint:** [Reason for visit]\n**HPI:** [Detailed history]\n**PMH:** [Conditions, surgeries]\n**Social\u002FFamily History:** [Relevant details]\n\n## Objective\n**Vitals:** [List values]\n**Physical Exam:** [Findings by system]\n**Labs\u002FImaging:** [Results]\n\n## Assessment\n**Diagnoses:**\n1. [Primary Diagnosis]\n2. [Differential]\n\n## Plan\n**Management:** [Steps taken]\n**Medications:** [Prescriptions]\n**Follow-up:** [Timeline]\n**Education:** [Instructions given]\n```\n\n## Best Practices\n\n- **Privacy:** Ensure no real PHI (Protected Health Information) is exposed in public logs if not authorized.\n- **Clarity:** Use medical terminology appropriately but keep patient instructions clear.\n- **Efficiency:** Aim to generate the full document in one iteration to reduce overhead.\n\n## Troubleshooting\n\n- **Missing Data:** If specific clinical data is missing, explicitly state \"Information not provided\" in the relevant section rather than skipping the section.\n- **File Size:** If the note is exceptionally long, ensure the file write command supports the content length.",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fcreate-soap-note","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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill create-soap-note",{"tool":47,"command":48},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill create-soap-note",{"tool":50,"command":51},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill create-soap-note","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fcreate-soap-note\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},".skill_id","OTHER","其他",30,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fcreate-soap-note\u002F.skill_id",[62,85,101,110,140,156],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":30},"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",[],[69,25,70,71,72,73,74,75,76,77,78,79,80,81,82,83,24,84],"check","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","python",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":30},"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",[],[92,93,25,24,94,84,95,96,97,98,99,83,100,28,73,76,78],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":30},"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",[],[108,25,73,109,78,96,83,24,84,76],"write special chars heredoc","shell",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":30},"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",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[122,123,124,125,126,71,127,128,129,130,131,76,132,133,134,135,136,137,138,139],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":30},"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",[],[147,148,149,150,76,151,28,152,153,154,155],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":30},"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",[],[163,164,165,166,167,168,24,169,170,171],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]