[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E20TP2XWJ03P0TECTDMEKD":3,"skill-same:01M7E20TP2XWJ03P0TECTDMEKD":97},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M7E20TP2XWJ03P0TECTDMEKD","achieving-cmmc-level-2-compliance",null,"Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when an organization handles Controlled Unclassified Information (CUI) under a DoD contract, when a contract carries DFARS clause 252.204-7012\u002F7019\u002F7020\u002F7021, when preparing for or responding to a CMMC assessment, when computing or improving an SPRS score, when building a System Security Plan or POA&M for 800-171, or when scoping which systems are in the CUI boundary. Keywords: CMMC, CMMC Level 2, NIST 800-171, SP 800-171 Rev 2, CUI, FCI, SPRS, DFARS 7012, C3PAO, POA&M, System Security Plan, DoD Assessment Methodology, 110 controls, defense industrial base, DIB, FedRAMP equivalency.","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\u002Fachieving-cmmc-level-2-compliance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fachieving-cmmc-level-2-compliance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: achieving-cmmc-level-2-compliance\ndescription: >-\n  Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI\n  and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14\n  families, compute the SPRS score with the DoD Assessment Methodology, manage a\n  compliant POA&M, and ready the organization for a C3PAO assessment. Use when an\n  organization handles Controlled Unclassified Information (CUI) under a DoD contract,\n  when a contract carries DFARS clause 252.204-7012\u002F7019\u002F7020\u002F7021, when preparing for\n  or responding to a CMMC assessment, when computing or improving an SPRS score, when\n  building a System Security Plan or POA&M for 800-171, or when scoping which systems\n  are in the CUI boundary. Keywords: CMMC, CMMC Level 2, NIST 800-171, SP 800-171 Rev 2,\n  CUI, FCI, SPRS, DFARS 7012, C3PAO, POA&M, System Security Plan, DoD Assessment\n  Methodology, 110 controls, defense industrial base, DIB, FedRAMP equivalency.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- cmmc\n- nist-800-171\n- cui\n- sprs\n- dfars\n- c3pao\n- poam\n- compliance\n- governance\n- defense-industrial-base\nversion: \"1.0\"\nauthor: andrewibrah\nlicense: Apache-2.0\nnist_csf:\n- GV.OC-03\n- GV.SC-01\n- ID.AM-08\n- ID.RA-05\n- PR.AA-01\n- PR.DS-01\nmitre_attack:\n- T1078\n- T1190\n- T1041\n- T1048\n- T1567\n---\n\n# Achieving CMMC Level 2 Compliance\n\n## When to Use\n\n- When an organization in the **Defense Industrial Base (DIB)** stores, processes, or transmits **Controlled Unclassified Information (CUI)** under a DoD contract.\n- When a contract includes **DFARS 252.204-7012** (safeguarding\u002Fincident reporting), **-7019\u002F-7020** (NIST 800-171 self-assessment + SPRS), or the new **-7021** (CMMC requirement).\n- When preparing for a **C3PAO** third-party assessment or a DoD-led assessment.\n- When you must **compute, post, or improve an SPRS score** based on the NIST SP 800-171 DoD Assessment Methodology.\n- When authoring or remediating a **System Security Plan (SSP)** and **POA&M** for the 110 requirements.\n- When **scoping** which assets fall inside the CUI\u002FFCI boundary (CUI assets, security-protection assets, contractor risk-managed assets, out-of-scope).\n\n## Prerequisites\n\n- Knowledge of **which contracts carry CUI** and the CUI categories involved (check the contract and the DoD CUI Registry).\n- An asset inventory and network diagram so you can define the **CMMC assessment scope** before assessing controls.\n- The **NIST SP 800-171 Rev 2** requirements and the **DoD Assessment Methodology** scoring weights.\n- A documented **SSP** (its absence is itself a failed requirement — 3.12.4).\n- Identification of any **External Service Providers (ESPs)** \u002F cloud services touching CUI, and whether they meet **FedRAMP Moderate (or equivalency)**.\n\n## Workflow\n\n### 1. Determine applicability and CUI categories\nConfirm the contract requires CMMC Level 2 (CUI present, not just FCI). FCI-only contracts are **Level 1** (the 15 FAR 52.204-21 requirements). Identify CUI categories from the contract and the DoD CUI Registry.\n\n### 2. Scope the environment\nClassify every asset into one of the CMMC scoping categories:\n- **CUI Assets** — process\u002Fstore\u002Ftransmit CUI (in scope, assessed against all applicable controls).\n- **Security Protection Assets** — provide security to the CUI environment (in scope).\n- **Contractor Risk Managed Assets** — could but are not intended to handle CUI; managed by policy.\n- **Specialized Assets** (IoT\u002FOT, GFE, test equipment) — documented, limited assessment.\n- **Out-of-Scope** — physically\u002Flogically isolated from CUI.\n\nMinimize scope deliberately — a smaller, well-segmented CUI enclave is far cheaper to certify than a flat network.\n\n### 3. Implement the 110 requirements (NIST SP 800-171 Rev 2)\nWork the **14 families** (3.1–3.14). For each requirement, implement, then write the **how** in the SSP. High-leverage early wins: MFA (3.5.3), FIPS-validated cryptography (3.13.11), audit logging (3.3.x), access control + least privilege (3.1.x), and incident response (3.6.x).\n\n### 4. Score with the DoD Assessment Methodology (SPRS)\nStart at **110** and subtract the weighted value (**1, 3, or 5 points**) of each **unmet** requirement; partial credit applies to a small number of controls (e.g., MFA, FIPS crypto). The result is the **SPRS score** (maximum 110; the methodology floor is −203). Post the score, the SSP date, and the assessment scope to **SPRS** (or eMASS for higher assessments).\n\n### 5. Build a compliant POA&M\nDocument every unmet requirement with owner, remediation, and milestone. **Constraints under the CMMC rule:** a **Conditional** status requires a score of at least **80%** (≥ 88 of 110), only **POA&M-eligible** requirements may be deferred (the highest-weighted security requirements must be fully met — verify eligibility against 32 CFR Part 170), and all POA&M items must be **closed within 180 days** to convert Conditional → **Final**.\n\n### 6. Assess (self or C3PAO)\n- **Level 1** and a subset of Level 2 = annual **self-assessment** with an affirmation in SPRS.\n- **Level 2 (most CUI contracts)** = triennial **C3PAO** certification assessment.\n- **Level 3** = DoD (DIBCAC) assessment on top of Level 2, adding SP 800-172 enhanced requirements.\nAssessors evaluate each objective as **MET \u002F NOT MET \u002F N\u002FA** with evidence (examine\u002Finterview\u002Ftest). A senior official files the **annual affirmation** of continued compliance.\n\n### 7. Maintain certification\nCertification is valid **three years** with **annual affirmations**. Maintain the SSP, re-score on change, keep evidence current, and feed significant changes back into the assessment.\n\n## Key Concepts\n\n| Concept | Definition |\n|---|---|\n| FCI | Federal Contract Information — Level 1 protects it (FAR 52.204-21). |\n| CUI | Controlled Unclassified Information — Level 2 protects it (NIST 800-171). |\n| 110 requirements | The SP 800-171 Rev 2 security requirements across 14 families. |\n| SPRS | Supplier Performance Risk System — where the 800-171 score is posted. |\n| DoD Assessment Methodology | The 1\u002F3\u002F5-point weighting used to compute the score from 110. |\n| C3PAO | CMMC Third-Party Assessment Organization — performs Level 2 certification. |\n| POA&M | Plan of Action & Milestones — limited, must close in 180 days for Final status. |\n| Conditional vs Final | Conditional = open POA&M (score ≥ 80%); Final = all controls met. |\n| ESP | External Service Provider — must meet FedRAMP Moderate \u002F equivalency for CUI. |\n| Scoping categories | CUI \u002F Security Protection \u002F Contractor Risk Managed \u002F Specialized \u002F Out-of-Scope. |\n\n## Tools & Systems\n\n- **NIST SP 800-171 Rev 2** — the 110 requirements (and 800-171A for assessment objectives).\n- **DoD NIST SP 800-171 Assessment Methodology** — the scoring weights.\n- **32 CFR Part 170** (CMMC Program rule) and **48 CFR \u002F DFARS 252.204-7021** (acquisition rule).\n- **SPRS** — score posting; **SAM.gov** for registration.\n- **SP 800-172 \u002F 800-172A** — enhanced requirements for Level 3.\n- **GRC \u002F compliance tooling** — to manage the SSP, POA&M, and evidence (e.g., Xacta, RegScale, FutureFeed-style trackers).\n\n## Common Scenarios\n\n- **Prime flows CUI to a sub.** The sub needs its own Level 2 scope, SSP, SPRS score, and (most likely) C3PAO certification.\n- **Score is below 88.** Prioritize the highest-weighted unmet requirements (5-point, then 3-point) to clear the conditional threshold and shrink the POA&M.\n- **Cloud holds CUI.** Confirm the service is FedRAMP Moderate authorized or meets equivalency; document the responsibility split.\n- **Flat network.** Re-scope into a segmented CUI enclave to cut the assessment surface before spending on controls.\n- **Annual affirmation due.** A senior official affirms continued compliance in SPRS; let it lapse and you risk contract eligibility.\n\n## Output Format\n\nProduce a **CMMC Level 2 Readiness Report** using `assets\u002Ftemplate.md`, containing:\n\n1. **Applicability & CUI categories** — why Level 2 applies.\n2. **Scope** — assets by scoping category and the CUI boundary diagram reference.\n3. **Control status by family** — met \u002F not met \u002F N\u002FA across the 14 families.\n4. **SPRS score** — computed score, deductions, and the gap to 110 and to the 88 threshold.\n5. **POA&M** — unmet requirements, eligibility check, owners, 180-day milestones.\n6. **Assessment path** — self vs C3PAO, target date, affirmation owner.\n7. **Remediation roadmap** — sequenced by point value and effort.\n\nUse `scripts\u002Fprocess.py` to compute the SPRS score from a control-status JSON, flag POA&M-eligibility concerns, and report the gap to the conditional-certification threshold.\n","# Achieving CMMC Level 2 Compliance\n\n## When to Use\n\n- When an organization in the **Defense Industrial Base (DIB)** stores, processes, or transmits **Controlled Unclassified Information (CUI)** under a DoD contract.\n- When a contract includes **DFARS 252.204-7012** (safeguarding\u002Fincident reporting), **-7019\u002F-7020** (NIST 800-171 self-assessment + SPRS), or the new **-7021** (CMMC requirement).\n- When preparing for a **C3PAO** third-party assessment or a DoD-led assessment.\n- When you must **compute, post, or improve an SPRS score** based on the NIST SP 800-171 DoD Assessment Methodology.\n- When authoring or remediating a **System Security Plan (SSP)** and **POA&M** for the 110 requirements.\n- When **scoping** which assets fall inside the CUI\u002FFCI boundary (CUI assets, security-protection assets, contractor risk-managed assets, out-of-scope).\n\n## Prerequisites\n\n- Knowledge of **which contracts carry CUI** and the CUI categories involved (check the contract and the DoD CUI Registry).\n- An asset inventory and network diagram so you can define the **CMMC assessment scope** before assessing controls.\n- The **NIST SP 800-171 Rev 2** requirements and the **DoD Assessment Methodology** scoring weights.\n- A documented **SSP** (its absence is itself a failed requirement — 3.12.4).\n- Identification of any **External Service Providers (ESPs)** \u002F cloud services touching CUI, and whether they meet **FedRAMP Moderate (or equivalency)**.\n\n## Workflow\n\n### 1. Determine applicability and CUI categories\nConfirm the contract requires CMMC Level 2 (CUI present, not just FCI). FCI-only contracts are **Level 1** (the 15 FAR 52.204-21 requirements). Identify CUI categories from the contract and the DoD CUI Registry.\n\n### 2. Scope the environment\nClassify every asset into one of the CMMC scoping categories:\n- **CUI Assets** — process\u002Fstore\u002Ftransmit CUI (in scope, assessed against all applicable controls).\n- **Security Protection Assets** — provide security to the CUI environment (in scope).\n- **Contractor Risk Managed Assets** — could but are not intended to handle CUI; managed by policy.\n- **Specialized Assets** (IoT\u002FOT, GFE, test equipment) — documented, limited assessment.\n- **Out-of-Scope** — physically\u002Flogically isolated from CUI.\n\nMinimize scope deliberately — a smaller, well-segmented CUI enclave is far cheaper to certify than a flat network.\n\n### 3. Implement the 110 requirements (NIST SP 800-171 Rev 2)\nWork the **14 families** (3.1–3.14). For each requirement, implement, then write the **how** in the SSP. High-leverage early wins: MFA (3.5.3), FIPS-validated cryptography (3.13.11), audit logging (3.3.x), access control + least privilege (3.1.x), and incident response (3.6.x).\n\n### 4. Score with the DoD Assessment Methodology (SPRS)\nStart at **110** and subtract the weighted value (**1, 3, or 5 points**) of each **unmet** requirement; partial credit applies to a small number of controls (e.g., MFA, FIPS crypto). The result is the **SPRS score** (maximum 110; the methodology floor is −203). Post the score, the SSP date, and the assessment scope to **SPRS** (or eMASS for higher assessments).\n\n### 5. Build a compliant POA&M\nDocument every unmet requirement with owner, remediation, and milestone. **Constraints under the CMMC rule:** a **Conditional** status requires a score of at least **80%** (≥ 88 of 110), only **POA&M-eligible** requirements may be deferred (the highest-weighted security requirements must be fully met — verify eligibility against 32 CFR Part 170), and all POA&M items must be **closed within 180 days** to convert Conditional → **Final**.\n\n### 6. Assess (self or C3PAO)\n- **Level 1** and a subset of Level 2 = annual **self-assessment** with an affirmation in SPRS.\n- **Level 2 (most CUI contracts)** = triennial **C3PAO** certification assessment.\n- **Level 3** = DoD (DIBCAC) assessment on top of Level 2, adding SP 800-172 enhanced requirements.\nAssessors evaluate each objective as **MET \u002F NOT MET \u002F N\u002FA** with evidence (examine\u002Finterview\u002Ftest). A senior official files the **annual affirmation** of continued compliance.\n\n### 7. Maintain certification\nCertification is valid **three years** with **annual affirmations**. Maintain the SSP, re-score on change, keep evidence current, and feed significant changes back into the assessment.\n\n## Key Concepts\n\n| Concept | Definition |\n|---|---|\n| FCI | Federal Contract Information — Level 1 protects it (FAR 52.204-21). |\n| CUI | Controlled Unclassified Information — Level 2 protects it (NIST 800-171). |\n| 110 requirements | The SP 800-171 Rev 2 security requirements across 14 families. |\n| SPRS | Supplier Performance Risk System — where the 800-171 score is posted. |\n| DoD Assessment Methodology | The 1\u002F3\u002F5-point weighting used to compute the score from 110. |\n| C3PAO | CMMC Third-Party Assessment Organization — performs Level 2 certification. |\n| POA&M | Plan of Action & Milestones — limited, must close in 180 days for Final status. |\n| Conditional vs Final | Conditional = open POA&M (score ≥ 80%); Final = all controls met. |\n| ESP | External Service Provider — must meet FedRAMP Moderate \u002F equivalency for CUI. |\n| Scoping categories | CUI \u002F Security Protection \u002F Contractor Risk Managed \u002F Specialized \u002F Out-of-Scope. |\n\n## Tools & Systems\n\n- **NIST SP 800-171 Rev 2** — the 110 requirements (and 800-171A for assessment objectives).\n- **DoD NIST SP 800-171 Assessment Methodology** — the scoring weights.\n- **32 CFR Part 170** (CMMC Program rule) and **48 CFR \u002F DFARS 252.204-7021** (acquisition rule).\n- **SPRS** — score posting; **SAM.gov** for registration.\n- **SP 800-172 \u002F 800-172A** — enhanced requirements for Level 3.\n- **GRC \u002F compliance tooling** — to manage the SSP, POA&M, and evidence (e.g., Xacta, RegScale, FutureFeed-style trackers).\n\n## Common Scenarios\n\n- **Prime flows CUI to a sub.** The sub needs its own Level 2 scope, SSP, SPRS score, and (most likely) C3PAO certification.\n- **Score is below 88.** Prioritize the highest-weighted unmet requirements (5-point, then 3-point) to clear the conditional threshold and shrink the POA&M.\n- **Cloud holds CUI.** Confirm the service is FedRAMP Moderate authorized or meets equivalency; document the responsibility split.\n- **Flat network.** Re-scope into a segmented CUI enclave to cut the assessment surface before spending on controls.\n- **Annual affirmation due.** A senior official affirms continued compliance in SPRS; let it lapse and you risk contract eligibility.\n\n## Output Format\n\nProduce a **CMMC Level 2 Readiness Report** using `assets\u002Ftemplate.md`, containing:\n\n1. **Applicability & CUI categories** — why Level 2 applies.\n2. **Scope** — assets by scoping category and the CUI boundary diagram reference.\n3. **Control status by family** — met \u002F not met \u002F N\u002FA across the 14 families.\n4. **SPRS score** — computed score, deductions, and the gap to 110 and to the 88 threshold.\n5. **POA&M** — unmet requirements, eligibility check, owners, 180-day milestones.\n6. **Assessment path** — self vs C3PAO, target date, affirmation owner.\n7. **Remediation roadmap** — sequenced by point value and effort.\n\nUse `scripts\u002Fprocess.py` to compute the SPRS score from a control-status JSON, flag POA&M-eligibility concerns, and report the gap to the conditional-certification threshold.\n",{"name":5,"tags":25,"author":36,"domain":37,"license":15,"version":38,"nist_csf":39,"subdomain":46,"description":7,"mitre_attack":47},[26,27,28,29,30,31,32,33,34,35],"cmmc","nist-800-171","cui","sprs","dfars","c3pao","poam","compliance","governance","defense-industrial-base","andrewibrah","cybersecurity","1.0",[40,41,42,43,44,45],"GV.OC-03","GV.SC-01","ID.AM-08","ID.RA-05","PR.AA-01","PR.DS-01","compliance-governance",[48,49,50,51,52],"T1078","T1190","T1041","T1048","T1567","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Fachieving-cmmc-level-2-compliance",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill achieving-cmmc-level-2-compliance",{"tool":67,"command":68},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill achieving-cmmc-level-2-compliance",{"tool":70,"command":71},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill achieving-cmmc-level-2-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fachieving-cmmc-level-2-compliance\u002FSKILL.md",true,[75,81,85,91],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Ftemplate.md","ASSET","资产文件",3801,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fachieving-cmmc-level-2-compliance\u002Fassets\u002Ftemplate.md",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fstandards.md","REFERENCE","参考文档",4882,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fachieving-cmmc-level-2-compliance\u002Freferences\u002Fstandards.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fprocess.py","SCRIPT","脚本",7774,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fachieving-cmmc-level-2-compliance\u002Fscripts\u002Fprocess.py",[98,106,114,122,130,137],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":102,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"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",[],[]]