plankton-code-quality

Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks. Use when setting up write-time formatting, linting, or auto-fix hooks on file edits.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/plankton-code-quality/SKILL.md

Quality

Content

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

The content is well-structured with strong workflow sequencing and actionable setup guidance, but it is verbose and inlines reference material that would be better split into bundled files. Splitting the config reference and ECC comparison into separate reference files would improve token efficiency and navigation.

Suggestions

Move the 'Configuration Reference' JSON block and 'Environment Overrides' table into a bundled reference file and link to it from the body to reduce inline token load.

Trim the 'ECC v1.8 Additions' and ECC pairing sections to only the resolution guidance, removing restated concepts Claude already knows, to improve conciseness.

Add a clearly signaled one-level-deep 'See X.md' pointer for the Plankton REFERENCE.md and SETUP.md docs so navigation is explicit rather than just listed in References.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear structure, but the ECC pairing section, 'ECC v1.8 Additions', and repeated config-protection material include unnecessary over-explanation that could be tightened, matching anchor 3 rather than 4.	3 / 5
Actionability	Provides concrete executable commands ('brew install jaq ruff uv', 'uv sync --all-extras'), a config JSON block, and env-override tables with only minor gaps in the per-project integration steps, matching anchor 4.	4 / 5
Workflow Clarity	The three-phase architecture is clearly sequenced with an explicit validation loop ('Re-runs Phase 1+2 to verify fixes', 'Exit 0 if clean, Exit 2 if violations remain') and a layered config-protection workflow, matching anchor 5.	5 / 5
Progressive Disclosure	No bundle files exist and the body inlines extensive config reference, environment overrides, and ECC comparison tables that belong in separate reference files, while referenced docs (REFERENCE.md, SETUP.md) are external and not clearly signaled as navigable, matching anchor 3.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is strong, clearly answering both what the skill does and when to use it in a distinctive third-person voice. It could be slightly improved with broader synonym coverage for trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('auto-formatting, linting, and Claude-powered fixes on every file edit via hooks'), with only minor coverage gaps, matching anchor 4 rather than 5 which requires more comprehensive coverage.	4 / 5
Completeness	Clearly states what the skill does ('write-time code quality enforcement... auto-formatting, linting, and Claude-powered fixes') and an explicit 'Use when setting up write-time formatting, linting, or auto-fix hooks' clause with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('formatting, linting, or auto-fix hooks on file edits') a user would say, but misses common synonyms like 'code quality', 'linters', or 'formatters', so it falls at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'write-time' enforcement niche via Plankton hooks with config protection and model-tier routing is a clear, distinct trigger set with minimal overlap with other skills, matching anchor 5.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/plankton-code-quality/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.