CC nist-csf-specialist
NIST Cybersecurity Framework 2.0 implementation, assessment, and compliance management. Use for CSF 2.0 gap analysis, cybersecurity risk management, maturity assessment, CSF profiles, and cross-framework compliance mapping.
NIST Cybersecurity Framework 2.0 implementation, assessment, and compliance management. Use for CSF 2.0 gap analysis, cybersecurity risk management, maturity…
As a process C 50/100 · Has gaps — References files that are not bundled: ../soc2-compliance-expert/, ../information-security-manager-iso27001/, ../infrastructure-compliance-auditor/
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 6
✓ No critical or high findings
Medium and low: 6
-
low Risky intent
intent-offensive-securityreferences/assessment-and-roadmap.md:57Offensive-security / dual-use content (legitimate for authorised testing; review intended use)4. **Review Prior Assessments** — Analyze previous CSF assessments, audit findings, penetration test results
-
low Risky intent
intent-offensive-securityreferences/csf-functions-guide.md:181Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Supplier security assessments (questionnaires, SOC 2 reports, penetration test results)
-
low Risky intent
intent-offensive-securityreferences/csf-functions-guide.md:252Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Penetration test results
-
low Risky intent
intent-offensive-securityreferences/csf-functions-guide.md:478Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Containment playbooks per incident type (ransomware, breach, insider, DDoS)
-
low Risky intent
intent-offensive-securityreferences/framework-reference.md:416Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Maintain containment playbooks for ransomware, data breach, insider threat, DDoS
-
low Risky intent
intent-offensive-securitySKILL.md:78Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Technical security testing, vulnerability scanning, or penetration testing (use infrastructure-compliance-auditor)
detector
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../soc2-compliance-expert/ - warning
missing-refreference to a missing file: ../information-security-manager-iso27001/ - warning
missing-refreference to a missing file: ../infrastructure-compliance-auditor/ - warning
missing-refreference to a missing file: ../pci-dss-specialist/ - warning
missing-refreference to a missing file: ../nis2-directive-specialist/ - warning
missing-refreference to a missing file: ../dora-compliance-expert/
Process rating: all ten parameters 50/100
- 0Tools and files. 6 referenced file(s) missing: ../soc2-compliance-expert/, ../information-security-manager-iso27001/, ../infrastructure-compliance-auditor/
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1609 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 223: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.