CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-audit

Find recurring Epicenter code smells and scope the cleanup they require. Use for periodic audits, cleanup PRs, post-refactor reviews, or reviews of a primitive’s consumers.

Quality

81%

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

76%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 highly actionable, codebase-validated audit catalog whose grep recipes, triage rules, and real examples make it directly executable. The main gaps are the missing post-fix validation loop in the workflow for batch refactoring and some inline bulk plus unverifiable cross-skill references that a leaner overview-plus-references split would address.

Suggestions

Add an explicit validation step to the Workflow section: after fixes, re-run the greps to confirm expected hits are gone and run `bun run check` plus tests before opening the cleanup PR.

Consolidate categories 5 and 6, which share the same Pick/boundary-leak analysis and duplicate the same rg pattern, into a single category with sub-cases.

Move the long Whispering evasion narrative in category 3 into a reference file (or trim it to the two grep patterns plus one sentence of why), keeping SKILL.md as a leaner catalog.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific validated patterns and assumes Claude's competence (no generic explanations of typing or promises), but the Whispering evasion narrative in category 3 and the substantial overlap between categories 5 and 6 (both re-explain Pick and boundary leaks) could be trimmed, so it is efficient with minor over-explanation rather than lean throughout.

4 / 5

Actionability

Every category provides a copy-paste-ready grep/rg command, a concrete triage recipe with line-count guidance, a real repo example fix (e.g., the UnixSocketRequestHandler replacement), and explicit false-positive rules, fully covering the common audit cases.

5 / 5

Workflow Clarity

The Workflow section gives a clear 4-step sequence (run greps, triage each hit, group by category, fix in one PR), but a batch refactoring workflow has no explicit validation or verification step (no run of bun run check/tests, no re-grep to confirm hits are resolved before the PR), and the rubric caps batch-operation workflows without validation at 3.

3 / 5

Progressive Disclosure

Sections are well-organized per category with clearly signaled one-level-deep cross-references (e.g., error-handling's error-variants reference in category 7), but the skill ships no bundle files, the external ../collapse-pass and ../error-handling reference paths cannot be verified within this bundle, and the full ~190-line catalog is inlined in SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

78%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 tight, well-structured description that explicitly states both capability and usage triggers with natural phrasing. Its only weaknesses are modest action specificity in the "what" half and slight trigger overlap with sibling review skills.

Suggestions

Name one or two concrete detection actions in the description (e.g., "run grep-based sweeps for seven validated smell categories") to lift the what-half from two actions to several.

Consider narrowing "post-refactor reviews" or "reviews of a primitive's consumers" so the description cannot fire for the sibling post-implementation-review skill's second-read ritual.

DimensionReasoningScore

Specificity

"Find recurring Epicenter code smells and scope the cleanup they require" names the domain plus two concrete actions (detect smells, scope cleanup), but does not list several specific actions like the actual detection greps or smell categories, so it stops at the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

It clearly answers "what" (find recurring code smells and scope the required cleanup) and "when" with an explicit "Use for" clause enumerating four concrete trigger scenarios, matching the anchor-5 pattern of both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"periodic audits, cleanup PRs, post-refactor reviews, reviews of a primitive's consumers" are natural phrases a user of this codebase would say, giving good keyword coverage, though common variations like "code smell sweep" or "cleanup pass" are missing, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Epicenter code smells" carves out a clear niche with distinct audit/cleanup triggers, but "post-refactor reviews" and "reviews of a primitive's consumers" overlap with the closely related post-implementation-review skill referenced in the body, keeping it at minor-overlap rather than minimal-conflict.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/code-audit/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.