CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-iso27001-kmo-pack

Builds an ISO 27001 documentation set for a Belgian SME: scope, risk assessment, Statement of Applicability and the core Annex A policies. Use when: Generate a complete ISMS scope statement for a Belgian legal entity; Conduct a NIS2 readiness quickcheck for Belgian organizations; Create a risk register with pre-defined SME impact/likelihood defaults.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-compliance/skills/nex-iso27001-kmo-pack/SKILL.md

The canonical home for this skill is nex-iso27001-kmo-pack in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

40%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 body reads as a product landing page rather than a skill: it markets capabilities and includes a sample chat, but provides no executable guidance — no templates, no document structures, no ordered workflow — and explicitly admits the scripts and templates from the original package are missing. Structure and brevity are reasonable, but actionability and workflow clarity are weak.

Suggestions

Add concrete output structures: a risk register table template (columns for asset, threat, likelihood, impact, owner, treatment), a Statement of Applicability template with per-control justification fields, and section outlines for each core policy (access control, supplier security, incident response, business continuity, secure development).

Define an ordered workflow (e.g., 1. NIS2 quickcheck questions, 2. scope statement with interested parties and boundaries, 3. risk assessment and treatment plan, 4. SoA, 5. policies) with validation checkpoints such as confirming scope boundaries with the user before generating the full document set.

Remove the redundant FAQ (which repeats Known limitations) and the promotional footer, and either bundle the referenced templates/scripts or drop claims to capabilities the folder cannot deliver.

DimensionReasoningScore

Conciseness

The body is short and sectioned without explaining concepts Claude already knows, but it contains redundant and off-task content: the FAQ ("Does this skill provide official ISO 27001 certification?... You still need an accredited auditor") repeats the Known limitations section, and the closing footer ("More skills, including the paid catalog: https://...") is pure promotion that earns no tokens.

3 / 5

Actionability

The skill only describes outcomes ("Runs the risk assessment and treatment plan with a likelihood-times-impact matrix and an owner per risk", "Generates the Statement of Applicability across the Annex A controls, with justification for every inclusion and exclusion") without any templates, document structures, control lists, or step-level guidance; it even states "Scripts, extension source, and templates from the original package are not in this folder", so the concrete material needed to execute is absent. It rises above anchor 1 only because a few concrete hints exist (matrix dimensions, per-control justification, the NIS2 quickcheck questions in the example).

2 / 5

Workflow Clarity

No ordered process for producing the documentation set is given; the only implied sequence (NIS2 quickcheck then scope statement) appears inside the example dialog rather than as instructions, and the "What it does" bullets are capabilities, not steps. It is a rough, gapped sequence rather than a fully incoherent one.

2 / 5

Progressive Disclosure

The body is well-organized with clear sections (What it does, Use cases, Known limitations, Example, Questions) and no wall of text or buried references, but this skill inherently needs bundled reference files (Annex A control list, policy templates, risk matrix) and none exist — the only pointer is an external marketing URL, which keeps it below anchor 5.

4 / 5

Total

11

/

20

Passed

Description

87%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: third-person, concrete about deliverables, with an explicit 'Use when:' clause containing specific trigger phrases that a target user would naturally say. The only weaknesses are un-enumerated policy names and a few missing natural synonyms.

DimensionReasoningScore

Specificity

"Builds an ISO 27001 documentation set for a Belgian SME: scope, risk assessment, Statement of Applicability and the core Annex A policies" lists several concrete deliverables, but the policy set is only referenced generically ("core Annex A policies") rather than enumerated, leaving minor gaps in coverage.

4 / 5

Completeness

It explicitly answers both questions: the "what" ("Builds an ISO 27001 documentation set for a Belgian SME: scope, risk assessment, Statement of Applicability and the core Annex A policies") and the "when" via an explicit "Use when:" clause with three concrete trigger phrases ("Generate a complete ISMS scope statement for a Belgian legal entity; Conduct a NIS2 readiness quickcheck for Belgian organizations; Create a risk register with pre-defined SME impact/likelihood defaults").

5 / 5

Trigger Term Quality

Natural phrases a user would say are present ("ISO 27001", "ISMS scope statement", "NIS2 readiness quickcheck", "risk register"), but common variations like "certification", "audit preparation", or "ISO27001" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific — ISO 27001 documentation for Belgian/EU SMEs with NIS2 framing — so triggers like "ISMS scope statement for a Belgian legal entity" are unlikely to fire for any other skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-compliance/skills/nex-iso27001-kmo-pack/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.