[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EHTEEXHP2C6KWX9NH4B0J":3,"skill-same:01M75EHTEEXHP2C6KWX9NH4B0J":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75EHTEEXHP2C6KWX9NH4B0J","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":23,"version":24,"description":7},"ECC direct-port adaptation","1.0.0","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fhipaa-compliance",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agisota\u002Fold-one --skill hipaa-compliance",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill hipaa-compliance",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill hipaa-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fhipaa-compliance\u002FSKILL.md",true,[],[49,56,63,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","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\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]