CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawsec-feed

Security advisory feed package for OpenClaw-related threats and vulnerabilities. The upstream feed is updated daily; local automation is handled by clawsec-suite or the operator.

Quality

57%

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-feed/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 delivers strong, security-conscious operational content with real validation feedback loops, but it is bloated and monolithic: repeated fetch/validate blocks, marketing-style installation-option comparisons, and 300+ lines of install machinery inlined where a reference file belongs. Broken pointers to nonexistent wiki/suite paths further undermine navigation.

Suggestions

Extract the ~170-line Step 2 install script into a bundled script (e.g. scripts/install.sh) and the feed schema/state-tracking detail into a reference file, leaving SKILL.md an overview.

Deduplicate the three near-identical feed-fetch/validate bash blocks into one canonical snippet that later sections reuse (e.g. by referencing a shared fetch function).

Fix or remove the dangling links to ../../wiki/exploitability-scoring.md and ../clawsec-suite/SKILL.md, inlining the exploitability-scoring guidance since no such files ship with the bundle.

DimensionReasoningScore

Conciseness

The ~850-line body is noticeably verbose: the same fetch-with-retry/validate feed block is repeated nearly verbatim three times ("Checking the Advisory Feed", "Parsing the Feed", "Cross-Reference Installed Skills"), and padded sections like the Option A/B "Advantages" lists add marketing bulk ("Convenient - no separate download needed"). Not 1 because most of the content is novel operational detail (checksums, signing keys, rate limits) rather than concepts Claude already knows.

2 / 5

Actionability

Extensive copy-paste-ready bash with error handling, retries, explicit exit codes, and security checks. Not 5 because "Filter by exploitability score" defers to paths that do not exist in this bundle ("[`wiki/exploitability-scoring.md`](../../wiki/exploitability-scoring.md)", "[`skills/clawsec-suite/SKILL.md`](../clawsec-suite/SKILL.md)") and Step 1's "# Save this SKILL.md as SKILL.md in the directory above" is vague. Not 3 because the code is genuinely executable, not pseudocode.

4 / 5

Workflow Clarity

Deployment is a clear Step 1-4 sequence with exemplary validation checkpoints — signed release manifest verification before extraction, per-file checksum checks, path-traversal and zip-bomb detection, and a fallback to individual-file download on checksum failure. Not 5 because the document presents two overlapping installation instruction sets (the quick SKILL.md download block that says "Once you have this skill file, proceed to Deploy" versus Deploy Step 2's full re-download), creating ambiguity about which sequence applies. Not 3 since validation is explicit and thorough, not merely present.

4 / 5

Progressive Disclosure

Section headers and tables provide navigable structure, but the entire payload — install scripts, feed JSON schema, state-file operations, rate-limiting guidance, notification templates — is inlined in one monolithic SKILL.md that clearly belongs in separate reference files, and the only external pointers are to files absent from the bundle. Not 4 because essentially nothing is split out; not 2 because headers do give real structure and navigation.

3 / 5

Total

13

/

20

Passed

Description

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

The description identifies a distinct niche but undersells the skill: it states what the package is, not what the skill does, and provides no "use when" trigger guidance. It reads more like package metadata than a skill description that would fire reliably at invocation time.

Suggestions

State the skill's concrete actions in third person, e.g. "Checks the advisory feed for new CVEs and community advisories, cross-references installed skills, and alerts the user".

Add an explicit trigger clause: "Use when the user mentions security advisories, CVEs, malicious or vulnerable skills/plugins, or agent threat intelligence".

Include natural trigger synonyms (CVE, malicious skill, prompt injection, security alert) so the description matches how users actually phrase these requests.

DimensionReasoningScore

Specificity

"Security advisory feed package for OpenClaw-related threats and vulnerabilities" names the domain but gives no concrete actions of the skill itself (no monitoring, parsing, cross-referencing, or alerting verbs); the second sentence describes upstream cadence and delegation to clawsec-suite rather than capabilities.

2 / 5

Completeness

There is a moderately clear "what" (an advisory feed package for OpenClaw threats), but "when to use it" is entirely absent — no "Use when..." clause or equivalent trigger guidance — which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is not even weakly implied.

3 / 5

Trigger Term Quality

"security advisory", "threats", and "vulnerabilities" are relevant keywords, but common natural phrasings users would say ("CVE", "malicious skill", "security alert", "check the feed") are missing. It sits between anchor 3 (some relevant keywords, missing variations) and anchor 4, closer to 3 because most natural variants are absent.

3 / 5

Distinctiveness Conflict Risk

The niche (OpenClaw-related security advisories) is fairly distinct, and explicitly naming "clawsec-suite" as the automation handler reduces collision with that sibling skill. Not 5 because the phrasing could still match broad security-related requests and overlaps minorly with generic security skills.

4 / 5

Total

12

/

20

Passed

Validation

68%

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

Validation — 11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

11

/

16

Passed

Repository

prompt-security/clawsec

Path

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