[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73113383VBKCBDQZ6C877H1":3,"skill-same:01M73113383VBKCBDQZ6C877H1":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73113383VBKCBDQZ6C877H1","hipaa-compliance",null,"HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare compliance requirements.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: hipaa-compliance\ndescription: HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare compliance requirements.\norigin: ECC direct-port adaptation\nversion: \"1.0.0\"\n---\n\n# HIPAA Compliance\n\nUse this as the HIPAA-specific entrypoint when a task is clearly about US healthcare compliance. This skill intentionally stays thin and canonical:\n\n- `healthcare-phi-compliance` remains the primary implementation skill for PHI\u002FPII handling, data classification, audit logging, encryption, and leak prevention.\n- `healthcare-reviewer` remains the specialized reviewer when code, architecture, or product behavior needs a healthcare-aware second pass.\n- `security-review` still applies for general auth, input-handling, secrets, API, and deployment hardening.\n\n## When to Use\n\n- The request explicitly mentions HIPAA, PHI, covered entities, business associates, or BAAs\n- Building or reviewing US healthcare software that stores, processes, exports, or transmits PHI\n- Assessing whether logging, analytics, LLM prompts, storage, or support workflows create HIPAA exposure\n- Designing patient-facing or clinician-facing systems where minimum necessary access and auditability matter\n\n## How It Works\n\nTreat HIPAA as an overlay on top of the broader healthcare privacy skill:\n\n1. Start with `healthcare-phi-compliance` for the concrete implementation rules.\n2. Apply HIPAA-specific decision gates:\n   - Is this data PHI?\n   - Is this actor a covered entity or business associate?\n   - Does a vendor or model provider require a BAA before touching the data?\n   - Is access limited to the minimum necessary scope?\n   - Are read\u002Fwrite\u002Fexport events auditable?\n3. Escalate to `healthcare-reviewer` if the task affects patient safety, clinical workflows, or regulated production architecture.\n\n## HIPAA-Specific Guardrails\n\n- Never place PHI in logs, analytics events, crash reports, prompts, or client-visible error strings.\n- Never expose PHI in URLs, browser storage, screenshots, or copied example payloads.\n- Require authenticated access, scoped authorization, and audit trails for PHI reads and writes.\n- Treat third-party SaaS, observability, support tooling, and LLM providers as blocked-by-default until BAA status and data boundaries are clear.\n- Follow minimum necessary access: the right user should only see the smallest PHI slice needed for the task.\n- Prefer opaque internal IDs over names, MRNs, phone numbers, addresses, or other identifiers.\n\n## Examples\n\n### Example 1: Product request framed as HIPAA\n\nUser request:\n\n> Add AI-generated visit summaries to our clinician dashboard. We serve US clinics and need to stay HIPAA compliant.\n\nResponse pattern:\n\n- Activate `hipaa-compliance`\n- Use `healthcare-phi-compliance` to review PHI movement, logging, storage, and prompt boundaries\n- Verify whether the summarization provider is covered by a BAA before any PHI is sent\n- Escalate to `healthcare-reviewer` if the summaries influence clinical decisions\n\n### Example 2: Vendor\u002Ftooling decision\n\nUser request:\n\n> Can we send support transcripts and patient messages into our analytics stack?\n\nResponse pattern:\n\n- Assume those messages may contain PHI\n- Block the design unless the analytics vendor is approved for HIPAA-bound workloads and the data path is minimized\n- Require redaction or a non-PHI event model when possible\n\n## Related Skills\n\n- `healthcare-phi-compliance`\n- `healthcare-reviewer`\n- `healthcare-emr-patterns`\n- `healthcare-eval-harness`\n- `security-review`\n","# HIPAA Compliance\n\nUse this as the HIPAA-specific entrypoint when a task is clearly about US healthcare compliance. This skill intentionally stays thin and canonical:\n\n- `healthcare-phi-compliance` remains the primary implementation skill for PHI\u002FPII handling, data classification, audit logging, encryption, and leak prevention.\n- `healthcare-reviewer` remains the specialized reviewer when code, architecture, or product behavior needs a healthcare-aware second pass.\n- `security-review` still applies for general auth, input-handling, secrets, API, and deployment hardening.\n\n## When to Use\n\n- The request explicitly mentions HIPAA, PHI, covered entities, business associates, or BAAs\n- Building or reviewing US healthcare software that stores, processes, exports, or transmits PHI\n- Assessing whether logging, analytics, LLM prompts, storage, or support workflows create HIPAA exposure\n- Designing patient-facing or clinician-facing systems where minimum necessary access and auditability matter\n\n## How It Works\n\nTreat HIPAA as an overlay on top of the broader healthcare privacy skill:\n\n1. Start with `healthcare-phi-compliance` for the concrete implementation rules.\n2. Apply HIPAA-specific decision gates:\n   - Is this data PHI?\n   - Is this actor a covered entity or business associate?\n   - Does a vendor or model provider require a BAA before touching the data?\n   - Is access limited to the minimum necessary scope?\n   - Are read\u002Fwrite\u002Fexport events auditable?\n3. Escalate to `healthcare-reviewer` if the task affects patient safety, clinical workflows, or regulated production architecture.\n\n## HIPAA-Specific Guardrails\n\n- Never place PHI in logs, analytics events, crash reports, prompts, or client-visible error strings.\n- Never expose PHI in URLs, browser storage, screenshots, or copied example payloads.\n- Require authenticated access, scoped authorization, and audit trails for PHI reads and writes.\n- Treat third-party SaaS, observability, support tooling, and LLM providers as blocked-by-default until BAA status and data boundaries are clear.\n- Follow minimum necessary access: the right user should only see the smallest PHI slice needed for the task.\n- Prefer opaque internal IDs over names, MRNs, phone numbers, addresses, or other identifiers.\n\n## Examples\n\n### Example 1: Product request framed as HIPAA\n\nUser request:\n\n> Add AI-generated visit summaries to our clinician dashboard. We serve US clinics and need to stay HIPAA compliant.\n\nResponse pattern:\n\n- Activate `hipaa-compliance`\n- Use `healthcare-phi-compliance` to review PHI movement, logging, storage, and prompt boundaries\n- Verify whether the summarization provider is covered by a BAA before any PHI is sent\n- Escalate to `healthcare-reviewer` if the summaries influence clinical decisions\n\n### Example 2: Vendor\u002Ftooling decision\n\nUser request:\n\n> Can we send support transcripts and patient messages into our analytics stack?\n\nResponse pattern:\n\n- Assume those messages may contain PHI\n- Block the design unless the analytics vendor is approved for HIPAA-bound workloads and the data path is minimized\n- Require redaction or a non-PHI event model when possible\n\n## Related Skills\n\n- `healthcare-phi-compliance`\n- `healthcare-reviewer`\n- `healthcare-emr-patterns`\n- `healthcare-eval-harness`\n- `security-review`\n",{"name":5,"origin":24,"version":25,"description":7},"ECC direct-port adaptation","1.0.0","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Fhipaa-compliance",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SriramGandhiS\u002FSkills --skill hipaa-compliance",{"tool":41,"command":42},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill hipaa-compliance",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill hipaa-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",true,[],[50,57,62,68,75,82],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]