CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

picoclaw-self-pen-testing

Picoclaw-only local posture-review skill focused on read-only findings and safe operator remediation guidance.

Quality

66%

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-self-pen-testing/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.

The body delivers fully executable, security-conscious guidance with a proper verify-before-install gate, which is its core strength. Its weaknesses are structural: a large inline script that belongs in a separate file, and no guidance on interpreting or acting on the findings the tool produces.

Suggestions

Move the ~70-line release-verification script into scripts/ (e.g. scripts/verify_release.sh) and keep a one-line invocation with the pinned pubkey fingerprint inline.

Add a short section explaining the tool's output format and what remediation guidance to give per flagged finding, since the description promises remediation guidance the body never delivers.

Make validation paths relative to the skill bundle or note they are repo-root paths, and ensure the referenced test file ships with the skill.

DimensionReasoningScore

Conciseness

The prose is lean and does not re-teach concepts Claude already knows, but roughly 60% of the body is a ~70-line inline release-verification script that would be tighter as a separate script or reference file invoked by one command. This is 'Mostly efficient but includes some... could be tightened' rather than 4, whose minor-trim bar is exceeded by the large inline block.

3 / 5

Actionability

The install command, usage command, and full bash verification script are concrete and copy-paste ready. It is not 5 because there is no guidance on interpreting the tool's output or acting on the flagged findings, despite the description promising remediation guidance, and the Validation section references paths (utils/validate_skill.py, test/self_pen_test.test.mjs) not present in this bundle.

4 / 5

Workflow Clarity

The install → verify release → run → validate sequence is clearly ordered, and the verification step has explicit failure checkpoints (checksum mismatches exit 1) plus an explicit gate ('Only install or extract the archive after this verification succeeds'). It is not 5 because the post-run workflow (what to do with findings and how to remediate) is left implicit.

4 / 5

Progressive Disclosure

Sections are clean and the referenced scripts/self_pen_test.mjs genuinely exists in the bundle, but the large verification script is inlined rather than split out, and the run/validate steps reference files outside the bundle without signaling. This matches 'Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline' rather than 4.

3 / 5

Total

14

/

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 is honest and reasonably scoped, clearly naming its domain and the nature of its output, but it is incomplete and under-specified. It lacks any 'when to use' trigger guidance and omits the concrete check categories that would make it more specific and discoverable.

Suggestions

Add a trigger clause, e.g. 'Use when the operator asks to review, audit, or pen-test their Picoclaw posture profile or mentions Picoclaw security settings.'

Enumerate the key finding categories (public Web UI exposure, disabled UI auth, plaintext secret markers, MCP trust boundaries) in the description so users searching those terms can find the skill.

Include natural synonyms such as 'security audit', 'review', or 'pen test' alongside the technical 'posture-review' term.

DimensionReasoningScore

Specificity

The description names the domain ("Picoclaw-only local posture-review") and two actions ("read-only findings and safe operator remediation guidance"), but these actions are generic and the concrete checks enumerated in the body (Web UI exposure, disabled UI auth, plaintext secrets, etc.) are absent. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several specific listed actions.

3 / 5

Completeness

The 'what' is clear (read-only posture findings plus remediation guidance), but there is no 'when' clause or equivalent trigger guidance anywhere in the description, capping completeness at 3 per the judging guidelines. It is not 2 because the 'what' is specific, and not 4 because 'when' is entirely missing rather than merely weak.

3 / 5

Trigger Term Quality

It contains relevant keywords ("Picoclaw", "posture-review", "remediation") but misses the natural phrases a user would say, such as "security audit", "pen test", or "review my setup". This is 'Some relevant keywords but missing common variations or synonyms', not 4, since several natural trigger terms are absent.

3 / 5

Distinctiveness Conflict Risk

"Picoclaw-only local posture-review" carves out a clear niche with minimal conflict risk against unrelated skills. It is not 5 because the body notes this was split from a broader 'guardian package', so minor overlap risk with closely related sibling security skills remains.

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-self-pen-testing/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.