[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EC8T1DN0H28C0R64S02MS6":3,"skill-same:01M7EC8T1DN0H28C0R64S02MS6":80},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M7EC8T1DN0H28C0R64S02MS6","executing-nist-rmf-authorization-to-operate",null,"Drive a federal system through the NIST Risk Management Framework (SP 800-37 Rev 2) to an Authorization to Operate (ATO): Prepare, Categorize (FIPS 199), Select a control baseline (FIPS 200 \u002F SP 800-53 Rev 5), Implement, Assess (SP 800-53A), Authorize, and Monitor continuously. Use when a system needs an ATO or a renewal, when working a FISMA\u002FFedRAMP authorization package, when building or reviewing an SSP, SAR, or POA&M, when categorizing a system as Low\u002FModerate\u002FHigh impact, when selecting or tailoring a control baseline, or when standing up continuous monitoring (ConMon) after authorization. Covers ATO, conditional ATO (cATO), and the artifacts assessors expect. Keywords: NIST RMF, 800-37, ATO, authorization to operate, FISMA, FedRAMP, SSP, SAR, POA&M, FIPS 199, FIPS 200, 800-53, 800-53A, control baseline, security categorization, continuous monitoring, authorizing official, system boundary, ongoing authorization.","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\u002F03-逆向工程\u002Fexecuting-nist-rmf-authorization-to-operate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: executing-nist-rmf-authorization-to-operate\ndescription: >-\n  Drive a federal system through the NIST Risk Management Framework (SP 800-37 Rev 2)\n  to an Authorization to Operate (ATO): Prepare, Categorize (FIPS 199), Select a control\n  baseline (FIPS 200 \u002F SP 800-53 Rev 5), Implement, Assess (SP 800-53A), Authorize, and\n  Monitor continuously. Use when a system needs an ATO or a renewal, when working a\n  FISMA\u002FFedRAMP authorization package, when building or reviewing an SSP, SAR, or POA&M,\n  when categorizing a system as Low\u002FModerate\u002FHigh impact, when selecting or tailoring a\n  control baseline, or when standing up continuous monitoring (ConMon) after authorization.\n  Covers ATO, conditional ATO (cATO), and the artifacts assessors expect. Keywords: NIST\n  RMF, 800-37, ATO, authorization to operate, FISMA, FedRAMP, SSP, SAR, POA&M, FIPS 199,\n  FIPS 200, 800-53, 800-53A, control baseline, security categorization, continuous\n  monitoring, authorizing official, system boundary, ongoing authorization.\ndomain: cybersecurity\nsubdomain: compliance-governance\ntags:\n- nist-rmf\n- nist-800-37\n- ato\n- fisma\n- fedramp\n- nist-800-53\n- fips-199\n- ssp\n- poam\n- continuous-monitoring\n- governance\nversion: \"1.0\"\nauthor: andrewibrah\nlicense: Apache-2.0\nnist_csf:\n- GV.OC-03\n- GV.RM-01\n- ID.AM-08\n- ID.RA-05\n- PR.IR-01\nmitre_attack:\n- T1078\n- T1190\n- T1068\n- T1210\n- T1486\n---\n\n# Executing the NIST RMF to an Authorization to Operate (ATO)\n\n## When to Use\n\n- When a federal or federally-aligned system (or a FedRAMP cloud service) needs an **Authorization to Operate**, a re-authorization, or has fallen out of authorization.\n- When you must produce or review the core authorization artifacts: **System Security Plan (SSP)**, **Security Assessment Report (SAR)**, and **Plan of Action & Milestones (POA&M)**.\n- When categorizing a system's impact level (Low \u002F Moderate \u002F High) under **FIPS 199**.\n- When selecting, tailoring, or implementing a **NIST SP 800-53 Rev 5** control baseline.\n- When standing up **continuous monitoring (ConMon)** or pursuing **ongoing authorization \u002F cATO** after an initial ATO.\n\n## Prerequisites\n\n- A defined **system** and **authorization boundary** (what's in, what's inherited, what's a leveraged service).\n- An identified **Authorizing Official (AO)**, **System Owner**, and **ISSO**.\n- The information types the system handles (use **SP 800-60** to map them to impact levels).\n- For cloud: the provider's **Customer Responsibility Matrix (CRM)** and any inherited\u002Fleveraged ATO.\n- Access to assessment evidence sources (config, scans, policies) for the Assess step.\n\n## Workflow\n\nNIST SP 800-37 Rev 2 defines **seven steps**. Prepare is the foundation; the rest run in order and then loop through Monitor.\n\n### 0\u002F1. Prepare (organization and system level)\nEstablish context: roles (AO, SO, ISSO, assessor), risk-management strategy and tolerance (ties to SP 800-39), a control baseline strategy, common controls available for inheritance, and the system's mission\u002Fbusiness context. Define the **authorization boundary** precisely — scope creep here inflates the whole package.\n\n### 2. Categorize (FIPS 199 + SP 800-60)\nDetermine the impact level for **confidentiality, integrity, and availability** for each information type, then take the **high-water mark** across the three to set the overall system categorization: **Low**, **Moderate**, or **High**. Document in the SSP. This single decision drives the entire control baseline.\n\n### 3. Select (FIPS 200 + SP 800-53 Rev 5 + SP 800-53B)\nStart from the SP 800-53B baseline matching the categorization (Low\u002FModerate\u002FHigh). Then **tailor**: apply scoping guidance, select compensating controls where needed, and assign values to organization-defined parameters. Add overlays (e.g., privacy, FedRAMP). Record the tailored set and the rationale in the SSP. Identify which controls are **common (inherited)**, **system-specific**, or **hybrid**.\n\n### 4. Implement\nDeploy the selected controls and **document how each is implemented** in the SSP — the implementation statement, not just \"yes.\" This is the artifact assessors read first; vague statements generate findings.\n\n### 5. Assess (SP 800-53A Rev 5)\nAn independent assessor evaluates controls using the **examine \u002F interview \u002F test** methods against assessment objectives. Findings of \"other than satisfied\" become weaknesses. Output is the **Security Assessment Report (SAR)**. Remediate what you can before authorization; the rest flows to the POA&M.\n\n### 6. Authorize\nAssemble the **authorization package**: SSP + SAR + POA&M (plus supporting artifacts). The AO reviews **residual risk** and renders a decision:\n- **ATO** — authorized, typically with a defined term and a ConMon expectation.\n- **Conditional \u002F cATO** — authorized subject to conditions or operating under an approved ongoing-authorization model.\n- **Denial \u002F DATO** — risk too high; system may not operate.\n\nThe decision and its rationale are captured in the **authorization decision document**.\n\n### 7. Monitor (continuous monitoring)\nAuthorization is not a one-time gate. Maintain an ongoing posture: track control effectiveness, ingest scan\u002Fconfig drift, update the SSP on change, work the POA&M to closure, report per the ConMon plan, and feed significant changes back into reassessment. Mature programs move from periodic re-ATO to **ongoing authorization**.\n\n## Key Concepts\n\n| Concept | Definition |\n|---|---|\n| Authorization boundary | The set of components, data flows, and inherited services covered by the authorization. |\n| FIPS 199 categorization | Low\u002FModerate\u002FHigh per C\u002FI\u002FA; overall = high-water mark across the three. |\n| Control baseline | The SP 800-53B starting control set for the categorization, before tailoring. |\n| Tailoring | Adjusting the baseline via scoping, compensating controls, and parameter values. |\n| Common \u002F inherited control | A control provided by another entity (e.g., the platform) and inherited by the system. |\n| SSP | System Security Plan — describes the system, boundary, and how each control is implemented. |\n| SAR | Security Assessment Report — the assessor's findings on control effectiveness. |\n| POA&M | Plan of Action & Milestones — tracked weaknesses with owners and remediation dates. |\n| ATO \u002F cATO \u002F DATO | Authorize \u002F conditional (ongoing) \u002F denial of authorization to operate. |\n| Authorizing Official (AO) | The senior official who accepts residual risk and signs the authorization. |\n| ConMon | Continuous monitoring — ongoing control-effectiveness and risk tracking post-ATO. |\n\n## Tools & Systems\n\n- **NIST SP 800-37 Rev 2** — the RMF process (7 steps).\n- **FIPS 199 \u002F FIPS 200 \u002F SP 800-60** — categorization and minimum requirements.\n- **NIST SP 800-53 Rev 5 \u002F 800-53B** — control catalog and baselines.\n- **NIST SP 800-53A Rev 5** — assessment procedures (examine\u002Finterview\u002Ftest).\n- **OSCAL** — machine-readable SSP\u002FSAR\u002FPOA&M (NIST's authorization-document format).\n- **eMASS** (DoD) \u002F **FedRAMP** templates — package management and submission.\n- **GRC platforms** — Xacta, ServiceNow, RegScale, etc., to manage the package and ConMon.\n- **NIST CSF 2.0** — cross-walks to communicate RMF posture in framework terms.\n\n## Common Scenarios\n\n- **New system pre-launch.** Run Categorize → Authorize before go-live; ATO is the gate to production.\n- **Cloud service (FedRAMP).** Inherit the platform's controls, document the CRM split, and authorize the customer-responsible delta.\n- **Re-authorization.** Triggered by term expiry or significant change; refresh SSP\u002FSAR\u002FPOA&M and re-decide.\n- **cATO \u002F ongoing authorization.** Replace periodic re-ATO with continuous evidence and an approved ConMon model.\n- **POA&M review.** Triage open weaknesses by risk, assign owners and dates, and report closure trend to the AO.\n\n## Output Format\n\nProduce an **Authorization Package summary** using `assets\u002Ftemplate.md`, containing:\n\n1. **System & boundary** — description, components, data flows, inherited services.\n2. **Categorization** — FIPS 199 C\u002FI\u002FA and overall impact, with information-type rationale.\n3. **Control baseline & tailoring** — baseline selected, tailoring decisions, common vs system-specific.\n4. **Implementation status** — per-family implementation summary (from the SSP).\n5. **Assessment results (SAR)** — findings by severity; what's satisfied vs other-than-satisfied.\n6. **POA&M** — open weaknesses, risk, owner, milestone dates.\n7. **Authorization decision** — ATO\u002FcATO\u002FDATO, term, conditions, residual-risk statement, AO.\n8. **ConMon plan** — what's monitored, how often, reporting cadence, reassessment triggers.\n\nUse `scripts\u002Fprocess.py` to select the right SP 800-53B baseline from a FIPS 199 categorization, summarize control-implementation status, and generate a POA&M table from a findings JSON.\n","# Executing the NIST RMF to an Authorization to Operate (ATO)\n\n## When to Use\n\n- When a federal or federally-aligned system (or a FedRAMP cloud service) needs an **Authorization to Operate**, a re-authorization, or has fallen out of authorization.\n- When you must produce or review the core authorization artifacts: **System Security Plan (SSP)**, **Security Assessment Report (SAR)**, and **Plan of Action & Milestones (POA&M)**.\n- When categorizing a system's impact level (Low \u002F Moderate \u002F High) under **FIPS 199**.\n- When selecting, tailoring, or implementing a **NIST SP 800-53 Rev 5** control baseline.\n- When standing up **continuous monitoring (ConMon)** or pursuing **ongoing authorization \u002F cATO** after an initial ATO.\n\n## Prerequisites\n\n- A defined **system** and **authorization boundary** (what's in, what's inherited, what's a leveraged service).\n- An identified **Authorizing Official (AO)**, **System Owner**, and **ISSO**.\n- The information types the system handles (use **SP 800-60** to map them to impact levels).\n- For cloud: the provider's **Customer Responsibility Matrix (CRM)** and any inherited\u002Fleveraged ATO.\n- Access to assessment evidence sources (config, scans, policies) for the Assess step.\n\n## Workflow\n\nNIST SP 800-37 Rev 2 defines **seven steps**. Prepare is the foundation; the rest run in order and then loop through Monitor.\n\n### 0\u002F1. Prepare (organization and system level)\nEstablish context: roles (AO, SO, ISSO, assessor), risk-management strategy and tolerance (ties to SP 800-39), a control baseline strategy, common controls available for inheritance, and the system's mission\u002Fbusiness context. Define the **authorization boundary** precisely — scope creep here inflates the whole package.\n\n### 2. Categorize (FIPS 199 + SP 800-60)\nDetermine the impact level for **confidentiality, integrity, and availability** for each information type, then take the **high-water mark** across the three to set the overall system categorization: **Low**, **Moderate**, or **High**. Document in the SSP. This single decision drives the entire control baseline.\n\n### 3. Select (FIPS 200 + SP 800-53 Rev 5 + SP 800-53B)\nStart from the SP 800-53B baseline matching the categorization (Low\u002FModerate\u002FHigh). Then **tailor**: apply scoping guidance, select compensating controls where needed, and assign values to organization-defined parameters. Add overlays (e.g., privacy, FedRAMP). Record the tailored set and the rationale in the SSP. Identify which controls are **common (inherited)**, **system-specific**, or **hybrid**.\n\n### 4. Implement\nDeploy the selected controls and **document how each is implemented** in the SSP — the implementation statement, not just \"yes.\" This is the artifact assessors read first; vague statements generate findings.\n\n### 5. Assess (SP 800-53A Rev 5)\nAn independent assessor evaluates controls using the **examine \u002F interview \u002F test** methods against assessment objectives. Findings of \"other than satisfied\" become weaknesses. Output is the **Security Assessment Report (SAR)**. Remediate what you can before authorization; the rest flows to the POA&M.\n\n### 6. Authorize\nAssemble the **authorization package**: SSP + SAR + POA&M (plus supporting artifacts). The AO reviews **residual risk** and renders a decision:\n- **ATO** — authorized, typically with a defined term and a ConMon expectation.\n- **Conditional \u002F cATO** — authorized subject to conditions or operating under an approved ongoing-authorization model.\n- **Denial \u002F DATO** — risk too high; system may not operate.\n\nThe decision and its rationale are captured in the **authorization decision document**.\n\n### 7. Monitor (continuous monitoring)\nAuthorization is not a one-time gate. Maintain an ongoing posture: track control effectiveness, ingest scan\u002Fconfig drift, update the SSP on change, work the POA&M to closure, report per the ConMon plan, and feed significant changes back into reassessment. Mature programs move from periodic re-ATO to **ongoing authorization**.\n\n## Key Concepts\n\n| Concept | Definition |\n|---|---|\n| Authorization boundary | The set of components, data flows, and inherited services covered by the authorization. |\n| FIPS 199 categorization | Low\u002FModerate\u002FHigh per C\u002FI\u002FA; overall = high-water mark across the three. |\n| Control baseline | The SP 800-53B starting control set for the categorization, before tailoring. |\n| Tailoring | Adjusting the baseline via scoping, compensating controls, and parameter values. |\n| Common \u002F inherited control | A control provided by another entity (e.g., the platform) and inherited by the system. |\n| SSP | System Security Plan — describes the system, boundary, and how each control is implemented. |\n| SAR | Security Assessment Report — the assessor's findings on control effectiveness. |\n| POA&M | Plan of Action & Milestones — tracked weaknesses with owners and remediation dates. |\n| ATO \u002F cATO \u002F DATO | Authorize \u002F conditional (ongoing) \u002F denial of authorization to operate. |\n| Authorizing Official (AO) | The senior official who accepts residual risk and signs the authorization. |\n| ConMon | Continuous monitoring — ongoing control-effectiveness and risk tracking post-ATO. |\n\n## Tools & Systems\n\n- **NIST SP 800-37 Rev 2** — the RMF process (7 steps).\n- **FIPS 199 \u002F FIPS 200 \u002F SP 800-60** — categorization and minimum requirements.\n- **NIST SP 800-53 Rev 5 \u002F 800-53B** — control catalog and baselines.\n- **NIST SP 800-53A Rev 5** — assessment procedures (examine\u002Finterview\u002Ftest).\n- **OSCAL** — machine-readable SSP\u002FSAR\u002FPOA&M (NIST's authorization-document format).\n- **eMASS** (DoD) \u002F **FedRAMP** templates — package management and submission.\n- **GRC platforms** — Xacta, ServiceNow, RegScale, etc., to manage the package and ConMon.\n- **NIST CSF 2.0** — cross-walks to communicate RMF posture in framework terms.\n\n## Common Scenarios\n\n- **New system pre-launch.** Run Categorize → Authorize before go-live; ATO is the gate to production.\n- **Cloud service (FedRAMP).** Inherit the platform's controls, document the CRM split, and authorize the customer-responsible delta.\n- **Re-authorization.** Triggered by term expiry or significant change; refresh SSP\u002FSAR\u002FPOA&M and re-decide.\n- **cATO \u002F ongoing authorization.** Replace periodic re-ATO with continuous evidence and an approved ConMon model.\n- **POA&M review.** Triage open weaknesses by risk, assign owners and dates, and report closure trend to the AO.\n\n## Output Format\n\nProduce an **Authorization Package summary** using `assets\u002Ftemplate.md`, containing:\n\n1. **System & boundary** — description, components, data flows, inherited services.\n2. **Categorization** — FIPS 199 C\u002FI\u002FA and overall impact, with information-type rationale.\n3. **Control baseline & tailoring** — baseline selected, tailoring decisions, common vs system-specific.\n4. **Implementation status** — per-family implementation summary (from the SSP).\n5. **Assessment results (SAR)** — findings by severity; what's satisfied vs other-than-satisfied.\n6. **POA&M** — open weaknesses, risk, owner, milestone dates.\n7. **Authorization decision** — ATO\u002FcATO\u002FDATO, term, conditions, residual-risk statement, AO.\n8. **ConMon plan** — what's monitored, how often, reporting cadence, reassessment triggers.\n\nUse `scripts\u002Fprocess.py` to select the right SP 800-53B baseline from a FIPS 199 categorization, summarize control-implementation status, and generate a POA&M table from a findings JSON.\n",{"name":5,"tags":24,"author":36,"domain":37,"license":15,"version":38,"nist_csf":39,"subdomain":45,"description":7,"mitre_attack":46},[25,26,27,28,29,30,31,32,33,34,35],"nist-rmf","nist-800-37","ato","fisma","fedramp","nist-800-53","fips-199","ssp","poam","continuous-monitoring","governance","andrewibrah","cybersecurity","1.0",[40,41,42,43,44],"GV.OC-03","GV.RM-01","ID.AM-08","ID.RA-05","PR.IR-01","compliance-governance",[47,48,49,50,51],"T1078","T1190","T1068","T1210","T1486","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","03-逆向工程\u002Fexecuting-nist-rmf-authorization-to-operate",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill executing-nist-rmf-authorization-to-operate",{"tool":66,"command":67},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill executing-nist-rmf-authorization-to-operate",{"tool":69,"command":70},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill executing-nist-rmf-authorization-to-operate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fexecuting-nist-rmf-authorization-to-operate\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstandards.md","REFERENCE","参考文档",4750,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fexecuting-nist-rmf-authorization-to-operate\u002Freferences\u002Fstandards.md",[81,90,95,102,109,116],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":89},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":89},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":89},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":89},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":89},"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",[],[]]