CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawsec-nanoclaw

Use when checking for security vulnerabilities in NanoClaw skills, before installing new skills, or when asked about security advisories affecting the bot

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

63%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 dense, well-sectioned body that is strong on executable tool-call examples and includes a rigorous signed-release verification procedure, but it is held back by duplicated 'Common Mistakes' entries, marketing claims, an oversized inlined bash script, and dangling INSTALL.md/docs/ references that don't exist in the bundle. Trimming the duplication and moving the verification script to a bundled script or reference file would improve both conciseness and progressive disclosure.

Suggestions

Merge the near-duplicate 'Ignoring exploitability context' and 'Skipping critical severity' Common Mistakes entries into one, and consider dropping the Quick Reference rows that merely repeat the preceding tool sections.

Move the ~70-line release verification script into a bundled scripts/ or references/ file and reference it with a one-line pointer, keeping SKILL.md as the overview.

Ensure ./INSTALL.md and ./docs/ actually ship in the bundle (they are absent here), or remove the links so navigation doesn't dead-end.

Add a short remediation step to the audit workflows (what to do after 'Urgent advisories found!') to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly tight, executable code, but 'Common Mistakes' #2 ('Ignoring exploitability context') and #3 ('Skipping critical severity') are near-duplicates with identical DO-blocks, the Quick Reference table repeats the preceding tool sections, and claims like 'Zero false positives (curated feed only)' add marketing padding — matching 'mostly efficient but includes some unnecessary explanation or could be tightened'. It is above anchor 2 because there is no explanation of concepts Claude already knows; the hardcoded VERSION="0.0.10" is time-sensitive and not in a deprecated/old-patterns section, which also costs it anchor 4.

3 / 5

Actionability

Concrete TypeScript tool calls with real parameter names (skillName, installRoot, severity, exploitabilityScore), a Quick Reference parameter table, and a fully copy-paste-ready bash verification script with checksums and signature checks satisfy 'mostly executable guidance; concrete code or commands with minor gaps'. It falls short of anchor 5 because the pattern examples depend on undefined helper functions (installSkill, showSecurityWarning, getUserConfirmation, notifyNow) that don't exist anywhere in the bundle, so those patterns cannot run as written.

4 / 5

Workflow Clarity

Pattern 1 gives an explicit check-then-act sequence with a user-confirmation branch, and the release-artifact verification section has explicit validation checkpoints with error exits ('if [ "$ACTUAL_PUBKEY_SHA256" != ... ] exit 1') and the closing rule 'Only install or extract the archive after this verification succeeds' — clear sequence with most checkpoints present. It is not anchor 5 because the audit workflows lack remediation loops: what to do after 'Urgent advisories found!' or a critical match is never sequenced beyond alerting.

4 / 5

Progressive Disclosure

Section structure is good, but scored against the actual bundle (no references/, scripts/, or assets/ directories exist): the ~70-line release-verification bash script is inlined content that clearly belongs in a separate script or reference file, and the only external pointers — [INSTALL.md](./INSTALL.md) and [docs/](./docs/) — reference files not present in the bundle. This matches 'some structure but could be better organized; content that should be separate is inline' with references that are not usable as-is.

3 / 5

Total

14

/

20

Passed

Description

70%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 competent, trigger-heavy description with an explicit 'Use when...' clause and natural keywords, but it is entirely 'when' and never separately states what the skill does, so its capability surface (audits, feed monitoring, pre-install gating, alerts) goes unlisted. Adding a third-person capability sentence before the trigger clause would raise both specificity and completeness.

Suggestions

Lead with a third-person capability sentence listing the concrete actions (e.g., 'Checks installed NanoClaw skills against a signed feed of security advisories, gates new skill installs, and audits existing skills'), then keep the existing 'Use when...' clause.

Add common trigger synonyms users would say — 'security audit', 'CVE', 'supply chain attack', 'malicious skill' — to broaden natural-term coverage.

Clarify the monitored object in the trigger (skills vs. dependencies) so 'security vulnerabilities' requests about general code don't collide with this skill.

DimensionReasoningScore

Specificity

The phrase "checking for security vulnerabilities in NanoClaw skills" names the domain plus one concrete action, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list the skill's several capabilities (pre-install checks, audits, advisory feed monitoring, alerts), so it is below anchor 4, while the named action is concrete rather than generic, keeping it above anchor 2.

3 / 5

Completeness

Both elements are present: the 'what' is embedded in the opening clause ("checking for security vulnerabilities in NanoClaw skills") and the 'when' is explicit and triple-stated ("before installing new skills, or when asked about security advisories affecting the bot"), matching anchor 4. It is not anchor 5 because the 'what' is never stated as a standalone capability sentence (e.g., 'Checks installed skills against a curated advisory feed and blocks vulnerable installs'), leaving the skill's actual function implied rather than explicit.

4 / 5

Trigger Term Quality

Natural phrases like "security vulnerabilities", "installing new skills", and "security advisories" are terms a user would plausibly say, matching 'good keyword coverage; a few natural terms missing'. It falls short of anchor 5 because common synonyms such as CVE, supply chain, malicious skills, or security audit are absent.

4 / 5

Distinctiveness Conflict Risk

The scoping to "NanoClaw skills" and "advisories affecting the bot" carves a clear niche with minimal conflict risk, matching 'mostly distinct; minor overlap risk'. It is not anchor 5 because "checking for security vulnerabilities" could also plausibly fire for general code-security or security-review requests, a closely related skill family.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

prompt-security/clawsec

Path

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