CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawsec-scanner

Automated vulnerability scanner for agent platforms. Performs dependency scanning (npm audit, pip-audit), multi-database CVE lookup (OSV, NVD, GitHub Advisory), SAST analysis (Semgrep, Bandit), and agent-specific static hook inspection for OpenClaw hooks.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/clawsec-scanner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 is highly actionable with concrete commands, a verified install path, and solid troubleshooting, but it is noticeably verbose with README-style sections and duplicated instructions, and its architecture references point at files missing from the bundle. Structure is present but detail that belongs in reference files is inlined.

Suggestions

Move the ScanReport/Vulnerability schema, Roadmap, Contributing, License, and Resources sections into a references/ file or README, keeping SKILL.md to install, usage, and troubleshooting.

Deduplicate tool-install instructions (prerequisites vs. troubleshooting) and test-running commands (Verification vs. Development) into single authoritative sections.

Reconcile the architecture tree with the actual bundle — either ship the referenced lib/, hooks/, and test/ files or remove those entries so navigation reflects what exists.

DimensionReasoningScore

Conciseness

The ~500-line body inlines README material (Roadmap, Contributing, License, Resources), duplicates tool-install instructions between Prerequisites and Troubleshooting, duplicates test commands between Verification and Development, and offers two parallel install routes. Several unnecessary padded sections match the 2 anchor; not 3 given the volume of duplication.

2 / 5

Actionability

Concrete and mostly executable: exact CLI invocations with flags ('runner.sh --target ./skills/ --output report.json --format json'), env vars, a complete signature-verified install script, and a hook setup command. Minor gaps: 'node test/*.test.mjs' and 'python ../../utils/validate_skill.py' reference paths that are not in this bundle.

4 / 5

Workflow Clarity

Install → verify binaries → scan → hook setup is clearly sequenced, with a Fail-Open Philosophy section, a Troubleshooting section covering failure modes, and a Verification section including '--check' and unit tests for this batch operation. Not 5 because the main scan workflow lacks an explicit 'validate the report' checkpoint after scanning.

4 / 5

Progressive Disclosure

Sections are well organized, but everything is inlined — the 28-line ScanReport/Vulnerability schema, roadmap, and license belong in separate reference files, and the architecture tree references 'lib/', 'hooks/clawsec-scanner-hook/HOOK.md', and 'test/' that do not exist in the actual bundle (only 'scripts/' is present). Some structure with inline content that should be separate and partly misleading references fits the 3 anchor.

3 / 5

Total

13

/

20

Passed

Description

71%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, specific description that names concrete tools for each capability in third-person voice. Its main weakness is the complete absence of a 'when to use' clause, which caps completeness, and slightly thin natural-language trigger synonyms.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when scanning agent skills or dependencies for vulnerabilities, checking for CVEs, or reviewing OpenClaw hooks for security issues.'

Include natural user phrasings and synonyms such as 'security scan', 'audit dependencies', and 'check packages for known vulnerabilities' to broaden trigger coverage.

Clarify what distinguishes it from running npm audit or Semgrep directly (e.g. unified reporting and continuous hook monitoring) to reduce overlap with generic security tooling.

DimensionReasoningScore

Specificity

The description names four concrete capability areas, each with specific tools: 'dependency scanning (npm audit, pip-audit)', 'multi-database CVE lookup (OSV, NVD, GitHub Advisory)', 'SAST analysis (Semgrep, Bandit)', and 'agent-specific static hook inspection for OpenClaw hooks' — comprehensive concrete coverage in third-person voice.

5 / 5

Completeness

The 'what' is clear and concrete across all scan types, but there is no 'Use when...' clause or equivalent trigger guidance anywhere, which caps completeness at 3. Not 2 because the 'what' is explicit and specific rather than vague.

3 / 5

Trigger Term Quality

Natural terms like 'vulnerability scanner', 'CVE', 'npm audit', and 'SAST' are present, but common user phrasings such as 'security scan', 'audit dependencies', or 'check for vulnerabilities' are missing. Good coverage with a few natural terms absent, matching the 4 anchor rather than the 5 anchor's synonym comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

'agent platforms' and 'OpenClaw hooks' carve a distinct niche, but generic terms like 'npm audit' and 'Semgrep' overlap with plain tool-usage requests that a general security skill could also serve. Mostly distinct with minor overlap risk, fitting the 4 anchor; not 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (506 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

prompt-security/clawsec

Path

skills/clawsec-scanner/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.