CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Review pull requests in the Trackdub public core (trackdubllc/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.

76

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

90%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 dense, well-structured review playbook with concrete file paths, class references, and falsifiable comment templates, assuming Claude's competence throughout. The main gap is the absence of an explicit feedback loop in the review workflow.

Suggestions

Add an explicit validate→fix→retry style feedback loop (e.g., 'After posting request-changes, re-check the corrected diff against the same rule before approving') to push workflow_clarity to 5.

Consider moving the per-area Checklist focus into a referenced file (e.g., CHECKLIST.md) to keep SKILL.md as a tighter overview and improve progressive_disclosure.

DimensionReasoningScore

Conciseness

Lean and dense with no padding — it never explains concepts Claude already knows (what a PR is, basic programming) and every line states a specific review rule or reference; each token earns its place.

5 / 5

Actionability

Highly actionable instruction-only guidance: exact file paths (Directory.Packages.props, bundled-models.manifest.json, THIRD_PARTY_NOTICES.md), concrete class/method references (StageRunRecord.Start(...), StageNames.*), and copy-paste-ready falsifiable comment examples.

5 / 5

Workflow Clarity

Clear sequenced workflow (Required context → ordered Review priorities 1-7 → Automatic stops → Checklist → Comment style → Merge bar) with a final merge gate, but lacks an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and clearly-signaled one-level-deep references to repo context files (REVIEW.md, AGENTS.md, PR template); the single-file body is appropriate for review guidance, though it is fairly long.

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.

A strong, specific description that clearly states what the skill does and when to use it, with natural trigger terms and a distinct niche tied to a single repository. Third-person imperative voice is used throughout with no first/second-person drift.

DimensionReasoningScore

Specificity

Lists many concrete review actions and domains ('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.

5 / 5

Completeness

Explicitly states both the what ('Review pull requests in the Trackdub public core...') and the when ('Use for...', 'Prefer this skill whenever reviewing diffs, pull requests, or suggesting review comments'), satisfying both halves with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural synonyms a user would actually say — 'code review', 'PR review', 'pull requests', 'reviewing diffs', 'suggesting review comments' — with strong overlap of common phrasings; the technical terms are additions rather than the only triggers.

5 / 5

Distinctiveness Conflict Risk

Scoped to a specific repository (trackdubllc/Trackdub public core) with distinct review triggers, making overlap with other skills minimal.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
trackdubllc/Trackdub
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.