[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79P1THN2SHR8YCH2SW7XE9R":3,"skill-same:01M79P1THN2SHR8YCH2SW7XE9R":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79P1THN2SHR8YCH2SW7XE9R","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.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\nmetadata:\n  version: \"1.0.0\"\n  origin: ECC direct-port adaptation\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,"metadata":24,"description":7},{"origin":25,"version":26},"ECC direct-port adaptation","1.0.0","main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Fhipaa-compliance","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill hipaa-compliance",{"tool":40,"command":41},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill hipaa-compliance",{"tool":43,"command":44},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill hipaa-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",true,[],[49,55,61,67,73,79],{"skillNo":50,"name":51,"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":52,"categories":53,"keywords":54,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"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":58,"categories":59,"keywords":60,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"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":64,"categories":65,"keywords":66,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"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":70,"categories":71,"keywords":72,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"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":76,"categories":77,"keywords":78,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"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":82,"categories":83,"keywords":84,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]