[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E4M2YREBYSNG4Y2S2S4NH2":3,"skill-same:01M7E4M2YREBYSNG4Y2S2S4NH2":99},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M7E4M2YREBYSNG4Y2S2S4NH2","implementing-hipaa-security-rule-safeguards",null,"Implement the HIPAA Security Rule (45 CFR Part 164 Subpart C) to protect electronic protected health information (ePHI): conduct the required risk analysis, deploy the administrative, physical, and technical safeguards, handle required vs addressable implementation specifications, execute Business Associate Agreements, and stand up breach-notification readiness. Use when an organization is a HIPAA covered entity or business associate, when protecting ePHI, when preparing for an OCR audit or responding to a breach, when performing a HIPAA Security Risk Analysis, when drafting or reviewing a BAA, or when mapping security controls to the §164.308\u002F310\u002F312\u002F314\u002F316 safeguards. Notes the 2025 NPRM proposed changes (not yet final). Keywords: HIPAA, HIPAA Security Rule, ePHI, PHI, 45 CFR 164, risk analysis, administrative safeguards, physical safeguards, technical safeguards, addressable, required, Business Associate Agreement, BAA, OCR, breach notification, HITECH, covered entity, business associate.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-hipaa-security-rule-safeguards\ndescription: >-\n  Implement the HIPAA Security Rule (45 CFR Part 164 Subpart C) to protect electronic\n  protected health information (ePHI): conduct the required risk analysis, deploy the\n  administrative, physical, and technical safeguards, handle required vs addressable\n  implementation specifications, execute Business Associate Agreements, and stand up\n  breach-notification readiness. Use when an organization is a HIPAA covered entity or\n  business associate, when protecting ePHI, when preparing for an OCR audit or responding\n  to a breach, when performing a HIPAA Security Risk Analysis, when drafting or reviewing a\n  BAA, or when mapping security controls to the §164.308\u002F310\u002F312\u002F314\u002F316 safeguards. Notes\n  the 2025 NPRM proposed changes (not yet final). Keywords: HIPAA, HIPAA Security Rule,\n  ePHI, PHI, 45 CFR 164, risk analysis, administrative safeguards, physical safeguards,\n  technical safeguards, addressable, required, Business Associate Agreement, BAA, OCR,\n  breach notification, HITECH, covered entity, business associate.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- hipaa\n- hipaa-security-rule\n- ephi\n- phi\n- 45-cfr-164\n- risk-analysis\n- baa\n- breach-notification\n- ocr\n- compliance\n- governance\nversion: \"1.0\"\nauthor: andrewibrah\nlicense: Apache-2.0\nnist_csf:\n- GV.OC-03\n- GV.RM-01\n- ID.RA-01\n- ID.RA-05\n- PR.DS-01\n- PR.AA-01\n- DE.CM-01\nmitre_attack:\n- T1078\n- T1566\n- T1486\n- T1530\n- T1048\n---\n\n# Implementing HIPAA Security Rule Safeguards\n\n## When to Use\n\n- When an organization is a **covered entity** (health plan, clearinghouse, or provider transmitting electronic transactions) or a **business associate** handling **ePHI** on their behalf.\n- When standing up or maturing controls to protect **electronic protected health information**.\n- When performing the mandatory **HIPAA Security Risk Analysis** (§164.308(a)(1)(ii)(A)) — the single most-cited gap in OCR enforcement.\n- When preparing for an **OCR audit\u002Finvestigation** or responding to a suspected **breach**.\n- When drafting, reviewing, or remediating a **Business Associate Agreement (BAA)**.\n- When mapping existing security controls to the HIPAA safeguard standards and implementation specifications.\n\n> Scope note: this skill covers the **Security Rule** (ePHI). The **Privacy Rule** (uses\u002Fdisclosures of all PHI) and the **Breach Notification Rule** are related but distinct; this skill touches breach readiness and BAAs where they intersect security.\n\n## Prerequisites\n\n- A clear determination of the organization's **role** (covered entity vs business associate) and where ePHI lives, flows, and is stored (an ePHI data map).\n- An **asset inventory** of systems that create, receive, maintain, or transmit ePHI.\n- Knowledge of the current rule's structure (45 CFR §§164.302–318) and the **required vs addressable** distinction.\n- Awareness that a **2025 NPRM** proposes significant changes (see Workflow step 7 and `references\u002Fstandards.md`) — track but do not assume them as in force.\n\n## Workflow\n\n### 1. Conduct the Security Risk Analysis (§164.308(a)(1)(ii)(A))\nThis is **required** and foundational. Inventory ePHI and systems, identify threats and vulnerabilities, assess current controls, determine likelihood and impact, and assign risk levels. (Pair with the NIST 800-30 methodology and HHS's SRA Tool.) Output is a documented, dated risk analysis — the artifact OCR asks for first.\n\n### 2. Implement Administrative Safeguards (§164.308)\nThe largest section. Includes the **Security Management Process** (risk analysis, risk management, sanction policy, information-system activity review), assigned **security responsibility** (a named Security Official), **workforce security**, **information access management**, **security awareness and training**, **security incident procedures**, **contingency planning** (data backup, disaster recovery, emergency-mode operation), **evaluation**, and **BAAs** with business associates.\n\n### 3. Implement Physical Safeguards (§164.310)\n**Facility access controls**, **workstation use** and **workstation security**, and **device and media controls** (disposal, media re-use, accountability, data backup and storage).\n\n### 4. Implement Technical Safeguards (§164.312)\n**Access control** (unique user ID, emergency access, automatic logoff, encryption\u002Fdecryption), **audit controls**, **integrity** (mechanisms to authenticate ePHI), **person\u002Fentity authentication**, and **transmission security** (integrity controls + encryption).\n\n### 5. Resolve \"Required\" vs \"Addressable\" specifications\nUnder the current rule, each implementation specification is **Required** (must implement) or **Addressable** (assess whether reasonable and appropriate; if so implement, if not document why and implement an equivalent alternative). **Addressable does not mean optional** — it means make and document a risk-based decision.\n\n### 6. Execute Business Associate Agreements (§164.314 \u002F §164.308(b))\nEvery business associate that touches ePHI needs a BAA binding it to safeguard ePHI, report incidents, and flow requirements to subcontractors. Maintain the BAA inventory.\n\n### 7. Track the 2025 NPRM proposed changes (NOT yet final)\nHHS OCR published an NPRM (Jan 6, 2025) proposing to **remove the required\u002Faddressable distinction** (make nearly all specifications required), and to mandate **MFA**, **encryption of ePHI at rest and in transit**, **asset inventory and network maps**, **vulnerability scans every 6 months**, **annual penetration testing**, **72-hour restoration of certain systems\u002Fdata**, and **annual risk-analysis updates**. **These are proposals** — the current rule remains in force until a final rule is published and effective. Plan toward them, but comply with what is current.\n\n### 8. Stand up breach-notification readiness (45 CFR §§164.400–414)\nDefine how you detect, assess (the four-factor risk assessment), and report breaches of unsecured PHI: to **individuals** and **HHS** (and **media** for breaches affecting 500+ in a state\u002Fjurisdiction), within the required timelines. Encryption to NIST standards renders PHI \"secured\" and is a safe harbor from breach notification.\n\n### 9. Document everything (§164.316)\nMaintain policies, procedures, and records of actions\u002Fdecisions in writing, **retain for six years**, review periodically, and update in response to environmental or operational change.\n\n## Key Concepts\n\n| Concept | Definition |\n|---|---|\n| ePHI | Electronic protected health information — the Security Rule's scope. |\n| Covered entity | Health plan, clearinghouse, or provider doing electronic transactions. |\n| Business associate | A vendor that handles ePHI for a covered entity; bound by a BAA. |\n| Risk analysis | Required, documented assessment of risks to ePHI (§164.308(a)(1)(ii)(A)). |\n| Required vs addressable | Must-implement vs risk-based-decision implementation specifications. |\n| Administrative \u002F Physical \u002F Technical safeguards | §164.308 \u002F §164.310 \u002F §164.312. |\n| BAA | Business Associate Agreement — contractually binds vendors to safeguard ePHI. |\n| Breach (unsecured PHI) | Triggers notification under §§164.400–414; encryption is a safe harbor. |\n| OCR | HHS Office for Civil Rights — enforces HIPAA. |\n| Six-year retention | Documentation retention requirement (§164.316). |\n\n## Tools & Systems\n\n- **45 CFR Part 164 Subpart C** — the Security Rule text (and Subpart D, Breach Notification).\n- **HHS Security Risk Assessment (SRA) Tool** — free guided risk analysis.\n- **NIST SP 800-66 Rev 2** — implementing the HIPAA Security Rule (NIST guidance, maps to 800-53).\n- **NIST SP 800-30** — risk-assessment methodology to ground the SRA.\n- **GRC \u002F compliance platforms** — to manage policies, the BAA inventory, and evidence.\n- **Encryption \u002F MFA \u002F SIEM \u002F audit-logging tooling** — to satisfy technical safeguards and the proposed mandates.\n\n## Common Scenarios\n\n- **OCR investigation after a breach.** First request is almost always the current, dated **risk analysis** and the **risk-management plan** — have them ready.\n- **New SaaS handling ePHI.** Sign a **BAA** before any ePHI flows; confirm the vendor's safeguards.\n- **Addressable spec you won't implement as written.** Document the risk-based rationale and the **equivalent alternative** you implemented instead.\n- **Preparing for the proposed rule.** Pre-position MFA, at-rest\u002Fin-transit encryption, asset inventory, scanning, and pen-testing so a final rule is a small step, not a scramble.\n- **Lost\u002Fstolen device.** If ePHI was encrypted to NIST standards, the safe harbor applies; if not, run the four-factor breach assessment and notify as required.\n\n## Output Format\n\nProduce a **HIPAA Security Rule Gap Assessment** using `assets\u002Ftemplate.md`, containing:\n\n1. **Role & ePHI scope** — covered entity vs BA; ePHI data map and systems.\n2. **Risk analysis summary** — top risks to ePHI with likelihood\u002Fimpact (feeds risk management).\n3. **Safeguard status** — Administrative \u002F Physical \u002F Technical, each specification marked **Implemented \u002F Partial \u002F Gap** with required-vs-addressable noted.\n4. **BAA inventory** — business associates and BAA status.\n5. **Breach-notification readiness** — detection, four-factor assessment, notification workflow.\n6. **2025 NPRM gap view** — readiness against the proposed mandates (clearly labeled proposed).\n7. **Remediation plan** — prioritized, with owners and dates; required specs and risk-analysis gaps first.\n\nUse `scripts\u002Fprocess.py` to score a safeguard-status JSON across the §164.308\u002F310\u002F312 standards, weight required gaps above addressable ones, and emit the gap table plus a remediation-priority list.\n","# Implementing HIPAA Security Rule Safeguards\n\n## When to Use\n\n- When an organization is a **covered entity** (health plan, clearinghouse, or provider transmitting electronic transactions) or a **business associate** handling **ePHI** on their behalf.\n- When standing up or maturing controls to protect **electronic protected health information**.\n- When performing the mandatory **HIPAA Security Risk Analysis** (§164.308(a)(1)(ii)(A)) — the single most-cited gap in OCR enforcement.\n- When preparing for an **OCR audit\u002Finvestigation** or responding to a suspected **breach**.\n- When drafting, reviewing, or remediating a **Business Associate Agreement (BAA)**.\n- When mapping existing security controls to the HIPAA safeguard standards and implementation specifications.\n\n> Scope note: this skill covers the **Security Rule** (ePHI). The **Privacy Rule** (uses\u002Fdisclosures of all PHI) and the **Breach Notification Rule** are related but distinct; this skill touches breach readiness and BAAs where they intersect security.\n\n## Prerequisites\n\n- A clear determination of the organization's **role** (covered entity vs business associate) and where ePHI lives, flows, and is stored (an ePHI data map).\n- An **asset inventory** of systems that create, receive, maintain, or transmit ePHI.\n- Knowledge of the current rule's structure (45 CFR §§164.302–318) and the **required vs addressable** distinction.\n- Awareness that a **2025 NPRM** proposes significant changes (see Workflow step 7 and `references\u002Fstandards.md`) — track but do not assume them as in force.\n\n## Workflow\n\n### 1. Conduct the Security Risk Analysis (§164.308(a)(1)(ii)(A))\nThis is **required** and foundational. Inventory ePHI and systems, identify threats and vulnerabilities, assess current controls, determine likelihood and impact, and assign risk levels. (Pair with the NIST 800-30 methodology and HHS's SRA Tool.) Output is a documented, dated risk analysis — the artifact OCR asks for first.\n\n### 2. Implement Administrative Safeguards (§164.308)\nThe largest section. Includes the **Security Management Process** (risk analysis, risk management, sanction policy, information-system activity review), assigned **security responsibility** (a named Security Official), **workforce security**, **information access management**, **security awareness and training**, **security incident procedures**, **contingency planning** (data backup, disaster recovery, emergency-mode operation), **evaluation**, and **BAAs** with business associates.\n\n### 3. Implement Physical Safeguards (§164.310)\n**Facility access controls**, **workstation use** and **workstation security**, and **device and media controls** (disposal, media re-use, accountability, data backup and storage).\n\n### 4. Implement Technical Safeguards (§164.312)\n**Access control** (unique user ID, emergency access, automatic logoff, encryption\u002Fdecryption), **audit controls**, **integrity** (mechanisms to authenticate ePHI), **person\u002Fentity authentication**, and **transmission security** (integrity controls + encryption).\n\n### 5. Resolve \"Required\" vs \"Addressable\" specifications\nUnder the current rule, each implementation specification is **Required** (must implement) or **Addressable** (assess whether reasonable and appropriate; if so implement, if not document why and implement an equivalent alternative). **Addressable does not mean optional** — it means make and document a risk-based decision.\n\n### 6. Execute Business Associate Agreements (§164.314 \u002F §164.308(b))\nEvery business associate that touches ePHI needs a BAA binding it to safeguard ePHI, report incidents, and flow requirements to subcontractors. Maintain the BAA inventory.\n\n### 7. Track the 2025 NPRM proposed changes (NOT yet final)\nHHS OCR published an NPRM (Jan 6, 2025) proposing to **remove the required\u002Faddressable distinction** (make nearly all specifications required), and to mandate **MFA**, **encryption of ePHI at rest and in transit**, **asset inventory and network maps**, **vulnerability scans every 6 months**, **annual penetration testing**, **72-hour restoration of certain systems\u002Fdata**, and **annual risk-analysis updates**. **These are proposals** — the current rule remains in force until a final rule is published and effective. Plan toward them, but comply with what is current.\n\n### 8. Stand up breach-notification readiness (45 CFR §§164.400–414)\nDefine how you detect, assess (the four-factor risk assessment), and report breaches of unsecured PHI: to **individuals** and **HHS** (and **media** for breaches affecting 500+ in a state\u002Fjurisdiction), within the required timelines. Encryption to NIST standards renders PHI \"secured\" and is a safe harbor from breach notification.\n\n### 9. Document everything (§164.316)\nMaintain policies, procedures, and records of actions\u002Fdecisions in writing, **retain for six years**, review periodically, and update in response to environmental or operational change.\n\n## Key Concepts\n\n| Concept | Definition |\n|---|---|\n| ePHI | Electronic protected health information — the Security Rule's scope. |\n| Covered entity | Health plan, clearinghouse, or provider doing electronic transactions. |\n| Business associate | A vendor that handles ePHI for a covered entity; bound by a BAA. |\n| Risk analysis | Required, documented assessment of risks to ePHI (§164.308(a)(1)(ii)(A)). |\n| Required vs addressable | Must-implement vs risk-based-decision implementation specifications. |\n| Administrative \u002F Physical \u002F Technical safeguards | §164.308 \u002F §164.310 \u002F §164.312. |\n| BAA | Business Associate Agreement — contractually binds vendors to safeguard ePHI. |\n| Breach (unsecured PHI) | Triggers notification under §§164.400–414; encryption is a safe harbor. |\n| OCR | HHS Office for Civil Rights — enforces HIPAA. |\n| Six-year retention | Documentation retention requirement (§164.316). |\n\n## Tools & Systems\n\n- **45 CFR Part 164 Subpart C** — the Security Rule text (and Subpart D, Breach Notification).\n- **HHS Security Risk Assessment (SRA) Tool** — free guided risk analysis.\n- **NIST SP 800-66 Rev 2** — implementing the HIPAA Security Rule (NIST guidance, maps to 800-53).\n- **NIST SP 800-30** — risk-assessment methodology to ground the SRA.\n- **GRC \u002F compliance platforms** — to manage policies, the BAA inventory, and evidence.\n- **Encryption \u002F MFA \u002F SIEM \u002F audit-logging tooling** — to satisfy technical safeguards and the proposed mandates.\n\n## Common Scenarios\n\n- **OCR investigation after a breach.** First request is almost always the current, dated **risk analysis** and the **risk-management plan** — have them ready.\n- **New SaaS handling ePHI.** Sign a **BAA** before any ePHI flows; confirm the vendor's safeguards.\n- **Addressable spec you won't implement as written.** Document the risk-based rationale and the **equivalent alternative** you implemented instead.\n- **Preparing for the proposed rule.** Pre-position MFA, at-rest\u002Fin-transit encryption, asset inventory, scanning, and pen-testing so a final rule is a small step, not a scramble.\n- **Lost\u002Fstolen device.** If ePHI was encrypted to NIST standards, the safe harbor applies; if not, run the four-factor breach assessment and notify as required.\n\n## Output Format\n\nProduce a **HIPAA Security Rule Gap Assessment** using `assets\u002Ftemplate.md`, containing:\n\n1. **Role & ePHI scope** — covered entity vs BA; ePHI data map and systems.\n2. **Risk analysis summary** — top risks to ePHI with likelihood\u002Fimpact (feeds risk management).\n3. **Safeguard status** — Administrative \u002F Physical \u002F Technical, each specification marked **Implemented \u002F Partial \u002F Gap** with required-vs-addressable noted.\n4. **BAA inventory** — business associates and BAA status.\n5. **Breach-notification readiness** — detection, four-factor assessment, notification workflow.\n6. **2025 NPRM gap view** — readiness against the proposed mandates (clearly labeled proposed).\n7. **Remediation plan** — prioritized, with owners and dates; required specs and risk-analysis gaps first.\n\nUse `scripts\u002Fprocess.py` to score a safeguard-status JSON across the §164.308\u002F310\u002F312 standards, weight required gaps above addressable ones, and emit the gap table plus a remediation-priority list.\n",{"name":5,"tags":25,"author":37,"domain":38,"license":15,"version":39,"nist_csf":40,"subdomain":48,"description":7,"mitre_attack":49},[26,27,28,29,30,31,32,33,34,35,36],"hipaa","hipaa-security-rule","ephi","phi","45-cfr-164","risk-analysis","baa","breach-notification","ocr","compliance","governance","andrewibrah","cybersecurity","1.0",[41,42,43,44,45,46,47],"GV.OC-03","GV.RM-01","ID.RA-01","ID.RA-05","PR.DS-01","PR.AA-01","DE.CM-01","compliance-governance",[50,51,52,53,54],"T1078","T1566","T1486","T1530","T1048","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill implementing-hipaa-security-rule-safeguards",{"tool":69,"command":70},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill implementing-hipaa-security-rule-safeguards",{"tool":72,"command":73},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill implementing-hipaa-security-rule-safeguards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards\u002FSKILL.md",true,[77,83,87,93],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002Ftemplate.md","ASSET","资产文件",4105,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards\u002Fassets\u002Ftemplate.md",{"path":84,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstandards.md","REFERENCE","参考文档",5612,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards\u002Freferences\u002Fstandards.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fprocess.py","SCRIPT","脚本",7836,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fimplementing-hipaa-security-rule-safeguards\u002Fscripts\u002Fprocess.py",[100,108,116,124,132,139],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]