CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Review pull requests in the Trackdub public core (Mesililm-LLC/Trackdub). Use for Copilot code review, PR review, architecture checks, dependency-direction violations, model/license safety, fake readiness, runtime planner routing, and honest test evidence. Prefer this skill whenever reviewing diffs, pull requests, or suggesting review comments in this repository.

Quality

95%

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

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

An exemplary instruction-only skill body: lean, entirely repo-specific, with concrete seams, an ordered review workflow, explicit stop conditions, a merge bar, and example comments. The only notable gap is that the inline checklist duplicates content delegated to the authoritative REVIEW.md, which slightly muddies what lives where.

Suggestions

Clarify the division of labor with REVIEW.md: either state that the inline 'Checklist focus' is a summary and REVIEW.md holds the authoritative version, or trim the inline checklist to only the highest-frequency checks to reduce duplication.

Add one or two exact verification commands (e.g., how to run the layer-appropriate test suites or guard tests) so reviewers can validate PR claims like 'tests pass' directly instead of only judging the listed evidence.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific rules Claude cannot know (dependency boundaries, StageNames guards, manifest paths) and contains no padding or explanation of already-known concepts — every token earns its place, matching the lean top anchor rather than the 'minor instances of over-explanation' of 4.

5 / 5

Actionability

Guidance is fully concrete: exact file paths and seams ('Trackdub.Domain', 'IRuntimePlanner', 'StageNames.*', 'bundled-models.manifest.json', 'tests/Trackdub.TestDoubles/') plus five copy-paste-ready example review comments covering common cases. Per the rubric's instruction-only note, absence of code is not penalized when guidance is this actionable, so it exceeds 4's 'minor gaps'.

5 / 5

Workflow Clarity

The workflow is clearly sequenced — required reading (1-3), issue-context loading with explicit fallback branches, then review priorities in order 1-7 — with explicit validation gates ('Automatic review stops', 'Merge bar') and checklists ('Checklist focus'), matching the top anchor's checkpoints and error recovery; 4's 'minor validation gaps' does not apply.

5 / 5

Progressive Disclosure

Sections are well organized and references are clearly signaled and one level deep ('Root REVIEW.md (authoritative reviewer checklist)', 'AGENTS.md', '.github/pull_request_template.md'), with no nested references. However, the inlined 'Checklist focus' partially duplicates the external file the skill itself calls authoritative (REVIEW.md), leaving a minor organization gap versus the 5 anchor's 'content appropriately split'.

4 / 5

Total

19

/

20

Passed

Description

92%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, repo-scoped description that explicitly covers both what the skill does and when to use it, with concrete enumerated capabilities and good natural trigger terms. The only weakness is that a few common trigger phrasings (e.g., plain 'code review') are absent or embedded in unusual compounds.

DimensionReasoningScore

Specificity

The description lists multiple concrete review actions — 'Copilot code review, PR review, architecture checks, dependency-direction violations, model/license safety, fake readiness, runtime planner routing, and honest test evidence' — giving comprehensive coverage of what the skill does, which matches the top anchor rather than the 'minor gaps' of 4.

5 / 5

Completeness

It explicitly answers both 'what' ('Review pull requests in the Trackdub public core' with enumerated check areas) and 'when' ('Use for...', 'Prefer this skill whenever reviewing diffs, pull requests, or suggesting review comments in this repository') with concrete trigger phrases, matching the top anchor; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Natural phrases like 'PR review', 'pull requests', 'reviewing diffs', and 'review comments' are present, but 'code review' only appears in the unusual compound 'Copilot code review' and a few common variations are missing, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a named repository ('Trackdub public core', 'Mesililm-LLC/Trackdub', 'in this repository') with distinct triggers, giving a clear niche with minimal conflict risk rather than merely 'mostly distinct' as at 4.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MesilimLLC/Trackdub

Path

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