CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

community-sweep

Land community pull requests as the contributor and answer community issues on thedotmack/claude-mem. Takes stock of every open PR (the owner's own included, except the ones the owner marked experimental) and community issue, triages each against the owner's merge philosophy and the cmem.ai hosted-service boundary, finishes somewhat-aligned PRs on the contributor's own branch, squash-merges so the contributor stays the commit author on main, thanks them by name, closes fixed issues with credit to reporter and fixer, keeps the private ledger and contributor roster current, and reports what it decided. Use when asked to "go through the PRs", "merge contributor PRs", "help contributors with their PRs", "land the new community PRs", "triage new issues and PRs", "run the community sweep", "keep the momentum", or "grow the community".

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A rigorous, highly executable operational protocol: every phase carries exact commands, decision tables, and validation/feedback loops, and it never explains things Claude already knows. The only meaningful room for improvement is moving some inline reference material (generated-bundle inventory, boundary rules, historical precedent notes) into a bundled reference file to cut token load.

Suggestions

Move the generated-bundle inventory in step 3 (the list of plugin/scripts, sqlite, and ui paths) into a references/bundles.md file and keep only the rule plus a pointer in SKILL.md, refreshing the pointer as noted.

Extract the seven hosted-service boundary rules into a references/boundary.md (or point at the existing docs/merge-rubric.md-style file) and summarize the decision rule in one line inline, reducing body token load.

Fold the inline dated precedent notes (e.g., the 2026-11-07 #5455 and #5383/#5347 incidents) into a short 'past incidents' reference or the run report template, keeping only the rule they justify in the body.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no space is spent explaining what PRs, merges, or CI are — but inline historical anecdotes ("On 2026-11-07 the owner was wrongly asked about #5455, which fixed Pro sign-in returning 500") and the long generated-bundle enumeration could be trimmed or moved to a reference file. This fits the 4 anchor (efficient with minor over-explanation that could be trimmed) rather than 5, where every token would earn its place.

4 / 5

Actionability

Guidance is fully executable throughout: exact gh/git commands for triage, checkout, push-remote resolution, squash-merge, CI approval by head SHA, the ledger printf one-liner, and the merge.lock loop, plus verdict tables that specify exactly what happens per case. Copy-paste ready and covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The seven numbered steps are clearly sequenced with explicit validation checkpoints (test baseline before landing anything, verify on the exact merge head, post-run gate in a fresh worktree) and genuine feedback loops for error recovery (incomplete baseline → stop and fix; non-baseline test failure → rerun alone, then fix; rejected push → pull, re-verify, push again; wrong author on main → record incident). This batch-merge workflow matches the 5 anchor.

5 / 5

Progressive Disclosure

The body is well-sectioned with clearly signaled, one-level-deep references to stable repo docs ("AGENTS.md and docs/architecture/observer-lifecycle.md on main hold the full contract") and named skills (claude-mem:release, oh-my-issues). It fits the 4 anchor (good structure, references mostly clear, minor organization gaps) rather than 5 because sizable inline material — the generated-bundle list and the hosted-service boundary enumeration — could live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: third person, packed with concrete capabilities, and ending in an explicit, multi-variant trigger clause. It would be discoverable from almost any natural user phrasing about handling community PRs or issues for this repo.

DimensionReasoningScore

Specificity

The description lists many concrete actions — "takes stock of every open PR", "triages each against the owner's merge philosophy", "finishes somewhat-aligned PRs on the contributor's own branch, squash-merges", "closes fixed issues with credit to reporter and fixer", "keeps the private ledger and contributor roster current" — giving comprehensive, specific coverage of what the skill does. It matches the 5 anchor (multiple specific concrete actions, comprehensive) rather than 4, since no meaningful capability is left out.

5 / 5

Completeness

Both halves are explicit: the first sentences answer "what" with concrete actions, and the closing clause answers "when" with quoted trigger phrases. It clearly matches the 5 anchor (explicit what AND when with concrete trigger phrases), not 4, because the when-guidance is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

The "Use when asked to" clause lists eight natural phrasings users would actually say: "go through the PRs", "merge contributor PRs", "help contributors with their PRs", "land the new community PRs", "triage new issues and PRs", "run the community sweep", "keep the momentum", "grow the community". Coverage includes synonyms and idiom variants, matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

The description is anchored to a specific repo and role — community PR/issue handling on thedotmack/claude-mem — with distinct triggers like "run the community sweep", so it occupies a clear niche with minimal risk of triggering for an unrelated skill.

5 / 5

Total

20

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

thedotmack/claude-mem

Path

.claude/skills/community-sweep/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.