clawsweeper

Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/clawsweeper/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete commands, clear sequenced workflows, and explicit validation feedback loops, but it is a verbose monolithic document with repeated command surfacing and inline time-sensitive version info, leaving conciseness and progressive disclosure at the middle level.

Suggestions

Move time-sensitive values (baseline version 0.4.3, unreleased 0.4.4 changelog, issue counts) into a dedicated 'Baselines / old patterns' section so they do not penalize conciseness.

Deduplicate the repeated gitcrawl command shapes by consolidating the CLI surface into one reference block and referring back to it.

Split large reference material (e.g., the full CLI shape catalog, claim-level definitions, dossier template) into bundle files under references/ and link to them one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids teaching basics Claude already knows, but repeats similar gitcrawl command shapes across sections and places time-sensitive values inline ('Current stable release baseline: 0.4.3', 'unreleased 0.4.4', '682-issue', '630 live issues') rather than in a deprecated/old-patterns section, so it could be tightened.	2 / 3
Actionability	It is packed with executable, copy-paste-ready bash commands with exact flags and JSON field lists, plus concrete output templates (the fork-issue-dossier markdown shape and the single-issue/batch output shapes), matching the fully-executable anchor.	3 / 3
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops — the 8-step Small-Fix Sweep Loop gates classification before patching, Verification Discipline gives a reproduce→fix→rerun→broaden loop, and the <update> mode ends with an explicit sync-verification step and Hard Stops.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the skill is a single large monolithic body with clear headers but no content split into one-level-deep referenced files; external docs it cites are project source-of-truth ledgers, not skill bundles, so structure is present but content that could be separate stays inline.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive, listing concrete capabilities in a clear niche, but relies on internal jargon rather than natural user trigger terms and omits an explicit 'Use when...' clause, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when triaging Slate issues, finding duplicates, or syncing the issue ledger') to raise completeness.

Soften internal jargon like 'OpenClaw-style sweep discipline' and 'gitcrawl API refreshes' toward phrasing users would actually say.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — 'archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes' — matching the top anchor for listing several specific concrete actions rather than naming only a domain.	3 / 3
Completeness	It clearly answers 'what' (triage and process the ledger with named disciplines) but provides no explicit 'Use when...' trigger clause in the description itself, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant keywords exist ('issue ledger', 'duplicate proof') but the phrasing leans on internal jargon ('OpenClaw-style sweep discipline', 'gitcrawl API refreshes') that a user would not naturally say, so it has some relevant keywords but misses common natural variations.	2 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to 'Slate v2 issue ledger' triage with gitcrawl/OpenClaw-specific discipline, giving it distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (635 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

	Total	12 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/clawsweeper/SKILL.md
Commit: 45116fd

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

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.