[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CYN8NNBEKBQ7YJS4FSC95":3,"skill-same:01M78CYN8NNBEKBQ7YJS4FSC95":47},{"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":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M78CYN8NNBEKBQ7YJS4FSC95","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.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\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.\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","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fhipaa-compliance","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill hipaa-compliance",{"tool":39,"command":40},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill hipaa-compliance",{"tool":42,"command":43},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill hipaa-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"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},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"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},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"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":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]