CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

csf-mapping

Map your security posture against the NIST Cybersecurity Framework 2.0 (Govern, Identify, Protect, Detect, Respond, Recover). Produce a gap analysis, current/target tier assessment, and roadmap in the governance language that boards, auditors, and CISOs actually use. Use when the user mentions 'NIST CSF,' 'CSF 2.0,' 'cybersecurity framework,' 'security posture,' 'governance mapping,' 'CSF gap analysis,' 'CSF tiers,' 'cybersecurity maturity,' 'security roadmap,' 'CISO report,' 'board reporting,' 'security program,' or needs to translate technical findings into governance language.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, genuinely actionable instruction-only skill: the methodology, per-Subcategory field table, tier definitions, and output template give Claude exactly what to produce, and boundaries (no probing, no tier inflation, handoff to incident-triage) are explicit. The main cost is token efficiency — CSF 2.0 background, the six-function table, and annotated external references re-explain what Claude already knows, and version-dated framing sits outside any deprecated section — and the crosswalk/common-gaps tables are candidates for offloaded reference files.

Suggestions

Trim the CSF 2.0 background (the 2024/CSF-1.1 history and the six-function table) to a one-line version pointer and keep only the function/subcategory naming the skill actually uses; if version-dated framing is needed, put it in a short 'deprecated frameworks' note rather than the intro.

Move the annotated external-framework References list (SP 800-53, ISO 27001, CIS v8, CMMC, book citation) to a one-level-deep reference file, keeping only NIST CSF 2.0 itself and the Community Profiles pointer inline.

Consider moving the 15-row Subcategory-to-skill crosswalk and the high-impact-gaps list into a references/ file (e.g., crosswalk.md), keeping a 3-4 line summary in SKILL.md with a clearly signaled link, to cut the always-loaded context roughly in half.

DimensionReasoningScore

Conciseness

Mostly efficient — the methodology, tables, and output template earn their tokens — but it explains material Claude already knows: CSF 2.0 history ('as of 2024, replaced CSF 1.1. It added a sixth function — Govern'), the full six-function table, and annotated external references (ISO 27001, CIS Controls v8, CMMC). The 'as of 2024' version framing is also time-sensitive information not placed in a deprecated/old-patterns section, which the guidelines penalize.

3 / 5

Actionability

Concrete, executable guidance throughout: a 5-step methodology, a 10-field per-Subcategory recording table, tier definitions with characteristics, a 'Risk × Cost-to-close' prioritization rule, a 30/90/365-day roadmap structure, and a copy-paste-ready markdown output template. Minor gaps: how to enumerate the full Subcategory list in scope is left to general knowledge, and evidence-gathering specifics are delegated to other skills via the crosswalk. Anchor 5's 'specific examples cover the common cases' is nearly met but the evidence-verification mechanics are thin.

4 / 5

Workflow Clarity

Five clearly sequenced, well-named steps (scope → profile → assess → prioritize → roadmap) with an explicit scope-drift checkpoint ('Write down what's in and what's out. Most CSF assessments fail at scope drift') and an evidence standard ('Current state — evidence, not aspiration'). Not anchor 5 because there is no explicit verify/re-check loop for the assessment itself — the tier-inflation check lives in the Boundaries section as an instruction ('Refuse to inflate tier ratings without evidence') rather than a validation step in the workflow. Not anchor 3 since checkpoints are present and explicit for the risky parts (scope, evidence, tier claims).

4 / 5

Progressive Disclosure

Good single-file structure: clear section headers, well-formed tables, and a distinct References section, with no nested/dead-end references. As there is no bundle at all (no references/, scripts/, or assets/ files), the skill functions as a self-contained document and navigation is easy. Kept from anchor 5 because ~210 lines of reference-style material — the 15-row subcategory crosswalk, the 9-item common-gaps list, and the annotated external-framework references — is inlined in SKILL.md where one-level-deep reference files would keep the overview leaner.

4 / 5

Total

15

/

20

Passed

Description

96%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.

A strong description that clearly states concrete capabilities, output artifacts, and an explicit, comprehensive trigger list in third-person voice. The only weakness is that a few broad trigger phrases ('security posture,' 'security program,' 'cybersecurity framework') create minor overlap risk with adjacent security-audit skills in the same repo.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — 'Produce a gap analysis, current/target tier assessment, and roadmap' plus 'Map your security posture against the NIST Cybersecurity Framework 2.0' — which comprehensively covers the skill's output set. Anchor 4 ('several specific actions; minor gaps in coverage') fits worse since every major CSF-assessment deliverable is named.

5 / 5

Completeness

Explicitly answers both what ('Map your security posture... Produce a gap analysis, current/target tier assessment, and roadmap in the governance language that boards, auditors, and CISOs actually use') and when ('Use when the user mentions... or needs to translate technical findings into governance language') with concrete trigger phrases, matching the anchor-5 example pattern. Anchor 4 would require a less explicit 'when,' which is not the case here.

5 / 5

Trigger Term Quality

The 'Use when' clause enumerates 13 natural trigger phrases with synonyms — 'NIST CSF,' 'CSF 2.0,' 'CSF gap analysis,' 'CSF tiers,' 'cybersecurity maturity,' 'CISO report,' 'board reporting,' 'security roadmap' — matching the rubric's 'comprehensive coverage including synonyms' anchor. A couple of plausible variants (e.g., 'framework assessment,' 'NIST 800-53 mapping') are absent, but coverage is far above anchor 4.

5 / 5

Distinctiveness Conflict Risk

The NIST CSF 2.0 niche is clear and most triggers ('CSF tiers,' 'CSF gap analysis,' 'governance mapping') are unambiguous, but broader phrases like 'security posture,' 'security program,' and 'cybersecurity framework' overlap with related audit/framework skills referenced in the repo (e.g., control-audit for SOC 2/ISO readiness). Anchor 5 ('minimal conflict risk') is not fully earned; anchor 3 ('could still overlap with similar skills') understates the distinctness.

4 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/csf-mapping/SKILL.md

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.