CtrlK
BlogDocsLog inGet started
Tessl Logo

achieving-cmmc-level-2-compliance

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/7019/7020/7021, 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.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, actionable, and appropriately split across real bundle files with a strong sequenced workflow and explicit validation gates. The only meaningful weakness is slight re-statment between the Key Concepts table and the Workflow, and no inline executable example in the body.

Suggestions

Trim the Key Concepts table to only terms not already defined inline in the Workflow to reduce token overlap and lift conciseness toward 5.

Add a short inline runnable example of the SPRS calculator invocation (e.g. a minimal `python scripts/process.py --input controls.json --require-conditional` snippet) so a key action is copy-paste ready without opening the script.

In Workflow step 3, link the per-requirement weights to `references/standards.md` explicitly so the reader knows where the authoritative 1/3/5 assignments live.

DimensionReasoningScore

Conciseness

The body is dense, uses tables and terse bullets, and assumes domain knowledge without padding; the Key Concepts table re-states some Workflow content, keeping it just short of the fully lean anchor.

4 / 5

Actionability

Concrete control IDs (3.5.3, 3.13.11), exact point values (1/3/5, floor −203, threshold 88), named clauses (32 CFR Part 170, DFARS 7012/7019/7020/7021), and an executable `scripts/process.py` with documented flags; minor gap is the absence of any inline runnable snippet in the body itself.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints — the 88-point conditional threshold, POA&M-eligibility check against 32 CFR Part 170, 180-day closeout gate, and the script's `--require-conditional` exit-1 feedback loop.

5 / 5

Progressive Disclosure

SKILL.md is a clean overview with well-signaled, one-level-deep references to real bundle files — `references/standards.md`, `assets/template.md`, and `scripts/process.py` — each with a clear purpose.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states concrete capabilities, provides multiple explicit 'Use when' triggers, lists a comprehensive keyword set, and occupies a clearly distinct compliance niche. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Names multiple concrete actions — scope CUI/FCI, implement the 110 800-171 requirements across 14 families, compute the SPRS score, manage a POA&M, ready for a C3PAO assessment — giving comprehensive coverage with no real gaps.

5 / 5

Completeness

Clearly answers both 'what' (prepare an environment for CMMC Level 2 certification across scoping, controls, scoring, POA&M, and assessment) and 'when' with several concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes explicit 'Use when...' triggers (CUI under a DoD contract, DFARS 252.204-7012/7019/7020/7021, CMMC assessment, SPRS score, SSP/POA&M) plus a broad keyword list with synonyms (CMMC, 800-171, CUI, FCI, SPRS, C3PAO, DIB).

5 / 5

Distinctiveness Conflict Risk

CMMC Level 2 / 800-171 / SPRS / C3PAO is a tightly defined compliance niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
mukul975/Anthropic-Cybersecurity-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.