CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawtributor

Harness-neutral community incident reporting for AI agents. Contribute to collective security by reporting threats.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/clawtributor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 skill body is highly actionable with concrete commands, templates, and a genuinely thorough release-verification script, and the reporting workflow is well sequenced with approval gates. However, duplicated installation sections, an oversized inlined verification script, and a dead reference to a nonexistent reporting.md file hurt both token efficiency and progressive disclosure.

Suggestions

Fix the dead reference: either ship the referenced reporting.md in the bundle or remove/replace the 'See reporting.md' link with the content inline.

Move the ~70-line release verification script into a scripts/verify-release.sh file and invoke it from SKILL.md, keeping the body as a concise overview.

Merge the two Installation sections into one to eliminate the duplicated (and contradictory: '-a openclaw' vs '-a codex') install commands.

DimensionReasoningScore

Conciseness

The body is mostly efficient — concrete lists, no concept tutorials — but the Installation instructions are duplicated in two sections ('Vercel Skills Installation' and a second 'Installation' section with overlapping and even contradictory harness flags), and a ~70-line shell verification script is inlined. This matches 'mostly efficient but could be tightened'; not a 4 given the real duplication.

3 / 5

Actionability

Guidance is fully executable: copy-paste install commands, a complete signed-release verification script with real error handling and exit codes, a concrete report JSON template, an exact user-confirmation prompt, file paths, and chmod 600 permissions. It is not a 4 because the common cases are covered with copy-paste-ready material throughout.

5 / 5

Workflow Clarity

The submission workflow has a clear sequenced flow with an explicit approval checkpoint (prepare locally → show user exactly what will be submitted → manual submission after approval), and the verification script has full feedback loops (mismatch → error → exit 1). Not a 5 because the post-submission state.json update in 'State Tracking' is not sequenced into the submission steps, leaving a minor gap between form submission and tracking.

4 / 5

Progressive Disclosure

The body references '[reporting.md](./reporting.md)' but no references directory or reporting.md file exists in the bundle — a dead reference an agent cannot follow. Additionally, the 70-line verification script is inlined when it clearly belongs in a separate scripts/ file. This matches 'content that clearly belongs in separate files is inlined' plus an unusable reference; not a 3 because the broken link makes navigation actively misleading.

2 / 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 concise and names a clear, distinctive niche, but it lists only one generic action and provides no 'use when' trigger guidance. Adding explicit trigger conditions and enumerating the report types (malicious prompts, vulnerable skills, tampering) would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to report a malicious prompt, a vulnerable skill, or a tampering attempt, or mentions security incidents or advisories.'

Enumerate the concrete capabilities instead of the single generic 'reporting threats' action — e.g. 'Reports malicious prompt attempts, vulnerable skills/plugins, and tampering attempts' — to match the body's actual scope.

Include natural user vocabulary such as 'malicious prompt', 'vulnerability', 'attack pattern', and 'security advisory' so the description triggers on real user phrasing.

DimensionReasoningScore

Specificity

The description names its domain ('Harness-neutral community incident reporting for AI agents') and one concrete action ('reporting threats'), matching the anchor for domain plus 1-2 concrete actions. It is not a 4 because only a single generic action is listed, and not a 2 because an action is explicitly stated alongside a specific domain.

3 / 5

Completeness

The 'what' is reasonably clear (community incident reporting, contributing threat reports), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is above a 2 because the 'what' is not vague.

3 / 5

Trigger Term Quality

Some relevant keywords are present ('incident reporting', 'security', 'threats'), but the natural phrases a user would say — 'malicious prompt', 'vulnerable skill', 'report an attack', 'advisory' — are missing. This sits at 'some relevant keywords but missing common variations', below the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The niche ('community incident reporting for AI agents', 'collective security') is distinct from typical skills and unlikely to trigger for the wrong skill. It is not a 5 because trigger terms like 'security' and 'threats' are broad and could overlap with related security-audit skills.

4 / 5

Total

13

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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: 1 missing

Warning

Total

12

/

16

Passed

Repository

prompt-security/clawsec

Path

skills/clawtributor/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.