CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skillshare-code-review

Review a skillshare change before it becomes a pull request, or review an open pull request. Use this skill whenever the user asks to: review a diff, branch, commit range or PR, check a change before opening a PR, run a pre-Codex review, or find what a change missed. It checks correctness, the repository's documented rules, the originating issue or spec, every consumer of a changed concept, and cleanup (reuse, simplification, efficiency, depth of fix), then verifies each finding against the code before reporting it. Read-only unless the user asks for fixes.

Quality

96%

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

100%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 lean, highly actionable single-file workflow: exact commands per target type, concrete per-pass briefs for parallel subagents, a verification step with explicit verdict criteria, and a fixed report format. Structure and length are appropriate for a skill whose every section is used on each run.

DimensionReasoningScore

Conciseness

Every sentence instructs and nothing explains concepts Claude already knows: Step 1 gives per-case diff commands in a table, the Consumers pass packs its checks (i18n locale paths, translated READMEs) into a few dense lines, and Step 4 defines each verdict in a single clause ('CONFIRMED: the scenario happens; you can name the line where it goes wrong'). Fits the lean/every-token-earns-its-place anchor; not anchor 4 because no sentence or parenthetical can be named as trimmable padding.

5 / 5

Actionability

Guidance is executable throughout: 'git diff origin/main...HEAD plus git diff HEAD', 'git worktree add, then gh pr checkout <n> inside it', 'python3 scripts/ai-context.py pull-requests', an exact subagent output contract ('file:line, a one-sentence claim, and a concrete scenario (input or state → wrong result)'), and a literal report template in Step 5. Specific commands and examples cover the common cases; matches the fully-executable anchor.

5 / 5

Workflow Clarity

Five explicitly sequenced steps with validation checkpoints and feedback loops: 'Stop here if the ref does not resolve or the diff is empty', a dedicated Verify step with CONFIRMED/PLAUSIBLE/Dropped decision rules, 'A finding without a scenario is not reported', and a fix loop of 'add a failing test first for each correctness fix, rerun the narrowest check that proves it'. The skill is read-only by default so the destructive-cap rule does not apply, and even the fix path validates before and after.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are needed: all five steps are per-run core workflow that belongs in SKILL.md, sections are clearly headed for navigation, and repo-specific detail is delegated one level deep to the target repo's own topic files via 'python3 scripts/ai-context.py list' rather than inlined. Content is appropriately placed with easy navigation, matching the top anchor; not anchor 4 because no content that clearly belongs in a separate file can be identified.

5 / 5

Total

20

/

20

Passed

Description

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

A strong description: third-person voice, a concrete enumeration of what is checked (all five passes plus per-finding verification), and an explicit 'Use this skill whenever' clause with natural user phrasings. The only soft spot is that its unscoped trigger wording overlaps what a generic code-review skill would claim.

Suggestions

Scope the trigger clause to the repository to cut overlap with generic review skills, e.g. 'Use when the user asks to review a diff, branch, commit range, or PR in the skillshare repo'.

Add one or two distinguishing trigger phrases only this skill would earn (e.g. 'pre-Codex sweep', 'review rounds') so 'review a diff or PR' alone does not also match a general code-review skill.

DimensionReasoningScore

Specificity

Quotes: 'checks correctness, the repository's documented rules, the originating issue or spec, every consumer of a changed concept, and cleanup (reuse, simplification, efficiency, depth of fix)', 'verifies each finding against the code before reporting it', 'Read-only unless the user asks for fixes'. These enumerate multiple concrete actions covering every pass the skill performs, matching the comprehensive-coverage anchor; not anchor 4 because no pass or behavior gap can be named.

5 / 5

Completeness

Explicitly answers both questions: what — 'It checks correctness, the repository's documented rules, ... then verifies each finding against the code before reporting it' — and when — 'Use this skill whenever the user asks to: review a diff, branch, commit range or PR, check a change before opening a PR, run a pre-Codex review, or find what a change missed'. Third person throughout, with concrete trigger phrases; matches the anchor-5 example pattern, and clearly above anchor 4 where 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Quotes: 'review a diff, branch, commit range or PR', 'check a change before opening a PR', 'run a pre-Codex review', 'find what a change missed'. The trigger clause covers the natural synonyms for every target object a user would name (diff, branch, commit range, PR, change) plus several verb phrasings, fitting the comprehensive-synonyms anchor; not anchor 4 because no commonly-said variation of the request is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

Quotes: 'Review a skillshare change before it becomes a pull request' and 'run a pre-Codex review' establish a clear niche, but the trigger phrasing 'review a diff, branch, commit range or PR' is generic enough to also match a general-purpose code-review skill, leaving minor overlap risk. Not anchor 5 (minimal conflict risk) because those unscoped trigger phrases are shared with any generic review skill; not anchor 3 because the skillshare scoping and pre-Codex terminology keep the niche distinct.

4 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

16

Passed

Repository

runkids/skillshare

Path

.skillshare/skills/skillshare-code-review/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.