[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMF424T2AF7HMCGZKFT3T5":3,"skill-same:01M7EMF424T2AF7HMCGZKFT3T5":82},{"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":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M7EMF424T2AF7HMCGZKFT3T5","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\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":24,"author":36,"domain":37,"license":15,"version":38,"nist_csf":39,"subdomain":47,"description":7,"mitre_attack":48},[25,26,27,28,29,30,31,32,33,34,35],"hipaa","hipaa-security-rule","ephi","phi","45-cfr-164","risk-analysis","baa","breach-notification","ocr","compliance","governance","andrewibrah","cybersecurity","1.0",[40,41,42,43,44,45,46],"GV.OC-03","GV.RM-01","ID.RA-01","ID.RA-05","PR.DS-01","PR.AA-01","DE.CM-01","compliance-governance",[49,50,51,52,53],"T1078","T1566","T1486","T1530","T1048","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fimplementing-hipaa-security-rule-safeguards",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-hipaa-security-rule-safeguards",{"tool":68,"command":69},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-hipaa-security-rule-safeguards",{"tool":71,"command":72},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-hipaa-security-rule-safeguards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-hipaa-security-rule-safeguards\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fstandards.md","REFERENCE","参考文档",5612,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-hipaa-security-rule-safeguards\u002Freferences\u002Fstandards.md",[83,92,97,104,111,118],{"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":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":93,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":91},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":91},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":91},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":91},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":91},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]