CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

picoclaw-security-guardian

Picoclaw security posture skill with advisory awareness, configuration drift detection, and supply-chain verification guidance.

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/picoclaw-security-guardian/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 executable, fail-closed commands for every capability and real bundled scripts, and workflows carry explicit verification checkpoints. Its weaknesses are moderate verbosity (a redundant one-row support matrix, stale v0.0.1 version notes, and a large inline shell script) and mixed reference hygiene — several cited paths do not resolve within the bundle.

Suggestions

Move the ~70-line release-verification shell block into a bundled script (alongside the other four scripts/) and keep a short invocation plus the key fingerprint in SKILL.md.

Drop or compress the single-row support-matrix table and update or relocate the stale 'v0.0.1' references (current version is 0.0.6) into a dedicated version-history/deprecation note.

Fix reference hygiene: either bundle the cited 'wiki/modules/...', 'utils/validate_skill.py', and 'test/*' paths or clearly mark them as source-repo-only, and consider a references/ file for the detailed operator-review guidance.

DimensionReasoningScore

Conciseness

Most sections are tight and command-driven, but there is tightening available: the single-row support-matrix table restates what the frontmatter already says, version-specific statements ('No scheduler creation in v0.0.1', 'Before publishing v0.0.1 release artifacts') are stale relative to the declared version 0.0.6 and sit outside any deprecation section, and the ~70-line inline release-verification shell block is content that could live in a script. This matches anchor 3 ('mostly efficient but could be tightened'), below 4 where only minor trims would be needed.

3 / 5

Actionability

Every capability is backed by copy-paste-ready, complete commands: a fully executable release-verification bash script with error handling and exit codes, and exact script invocations with all required flags (e.g., '--feed ... --state ...', '--baseline ... --current ... --fail-on critical', '--artifact/--checksums/--signature/--public-key'), and the referenced scripts (check_advisories.mjs, check_drift.mjs, generate_profile.mjs, verify_supply_chain.mjs) exist in the bundle. This matches the anchor-5 example of fully executable, common-case-covering commands.

5 / 5

Workflow Clarity

Sequences are clear and checkpoints are largely present: the release flow fails closed ('Only install or extract the archive after this verification succeeds') with explicit ERROR/exit-1 paths, the drift flow is generate-profile then compare with '--fail-on critical', and a Validation section plus a pre-release regression lane are specified. It is not a 5 because there are no explicit error-recovery/feedback loops (e.g., what to do when drift or an advisory hit is found) and the multi-workflow ordering is implied by section order rather than an explicit overall sequence.

4 / 5

Progressive Disclosure

Structure is decent: well-labeled sections, and the four referenced scripts are real bundle files. However, the body also points to paths that do not exist in the bundle ('wiki/modules/picoclaw-security-guardian.md', 'utils/validate_skill.py', 'skills/picoclaw-security-guardian/test/*') without clear signaling, and the long inline release-verification shell block plus drift/advisory detail is content that belongs in the existing scripts/ or a references/ layer. This matches anchor 3 ('some structure; references present but not clearly signaled; content that should be separate is inline'), short of anchor 4's well-signaled one-level-deep references.

3 / 5

Total

15

/

20

Passed

Description

53%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 clearly scopes the skill to Picoclaw and enumerates its three capability areas, but it is written as a feature list rather than an action-plus-trigger statement. It lacks any 'Use when...' guidance and natural trigger variations, capping both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when reviewing or hardening Picoclaw deployments, checking security advisories/CVEs for the gateway, or verifying release artifacts before install.'

Rewrite capability nouns as concrete third-person actions: 'Checks security advisories against a verified feed, detects configuration drift against an approved baseline, and verifies signed release artifacts.'

Include natural synonyms users would say, such as CVE/vulnerability alerts, config baseline, signed releases, provenance, and supply-chain checks.

DimensionReasoningScore

Specificity

The description names the domain ('Picoclaw security posture skill') and three capability areas ('advisory awareness, configuration drift detection, and supply-chain verification guidance'), which is more than 1-2 items, but they are hedged noun phrases rather than concrete actions ('awareness', 'guidance'), not the verb-stated capabilities of the anchor-4 example. It fits anchor 3: clear domain with named but non-comprehensive, non-action-oriented capabilities.

3 / 5

Completeness

The 'what' is stated (advisory awareness, drift detection, supply-chain verification), but there is no 'Use when...' clause or any trigger guidance, which per the guidelines caps completeness at 3. It is not a 2 because the 'what' is clear and multi-part, not vague.

3 / 5

Trigger Term Quality

Phrases like 'security posture', 'advisory', 'configuration drift', and 'supply-chain verification' are keywords a security-minded user might say, but there are no natural variations or synonyms (e.g., CVE, vulnerability feed, provenance, signed releases). This matches anchor 3: some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

Scoping to 'Picoclaw' gives a clear niche with minimal generic conflict. It is not a 5 because the description contains no distinct trigger phrases and could overlap with sibling platform-security modules implied by the support-matrix family (e.g., other ClawSec platform guardians), matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills').

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

prompt-security/clawsec

Path

skills/picoclaw-security-guardian/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.