CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-karpathy-reviewer

Reviews staged git changes against Karpathy's 4 coding principles. Runs complexity_checker on changed files, diff_surgeon on the diff, and produces a verdict with specific fix recommendations. Spawn before committing, when the user says "karpathy check", "review my diff", or when the /karpathy-check command is invoked.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, actionable review skill body with concrete commands and a clear sequenced workflow. It loses points only on placeholder gaps and the absence of explicit error-recovery feedback loops.

Suggestions

Resolve the '<plugin>' and '<changed-files>' placeholders into concrete, copy-pasteable invocations (or document how they are substituted) to push actionability to 5.

Add an explicit validation/feedback step after running the tools (e.g., 'If complexity_checker exits non-zero or returns no findings, note it in the report and adjust manual review depth') to add an error-recovery loop.

Signal the dependency on the karpathy-coder scripts more explicitly — name the referenced scripts and their location up front so the cross-skill reference is unambiguous.

DimensionReasoningScore

Conciseness

Lean and efficient: states the role, gives exact commands, per-principle checks, and a report template without explaining concepts Claude already knows. Every section earns its place.

5 / 5

Actionability

Provides concrete executable commands (git diff, complexity_checker, diff_surgeon) and a full report template, but relies on placeholders like '<plugin>' and '<changed-files>' that leave minor gaps.

4 / 5

Workflow Clarity

Clear 4-step sequence (diff, tools, manual review, report) with a fallback checkpoint in step 1, but lacks explicit error-recovery feedback loops between tool runs and the report.

4 / 5

Progressive Disclosure

Well-organized into Role/Workflow/Rules sections with no nested references, but the ~80-line body references plugin scripts via an implicit '<plugin>' placeholder rather than clearly signaled one-level-deep references.

4 / 5

Total

17

/

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 invoke it, with natural trigger phrases and a distinct niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Reviews staged git changes', 'Runs complexity_checker on changed files', 'diff_surgeon on the diff', 'produces a verdict with specific fix recommendations' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (reviews changes against 4 principles, runs tools, produces verdict) and when ('Spawn before committing, when the user says...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'karpathy check', 'review my diff', and the '/karpathy-check' command — giving comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

The 'Karpathy's 4 coding principles' niche and 'karpathy check' / '/karpathy-check' triggers form a clear, distinct niche with minimal conflict risk.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.