Plankton Write-Time Code Quality
Enforce code quality on every file edit: silent auto-formatting, 20+ linters, Claude-powered fixes with tiered model routing, plus config tamper protection.
- What
- Enforce code quality on every file edit: silent auto-formatting, 20+ linters, Claude-powered fixes with tiered model routing, plus config tamper protection.
- Cost
- Free
- Needs
- None. No account, no API key, no payment: this skill is a single instruction file for the agent.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an integration reference for Plankton (by @alxfazio), a write-time code quality enforcement system for Claude Code. Every file edit triggers a three-phase PostToolUse hook: silent auto-formatting (ruff format, biome, shfmt and friends fix 40 to 50 percent of issues invisibly), violation collection as structured JSON, then delegation to a claude subprocess that fixes what the agent missed, routing by complexity (Haiku for style, Sonnet for complexity and refactoring, Opus for deep type reasoning) and re-verifying afterward. The main agent only ever sees violations the subprocess could not fix. Plankton also defends against rule-gaming: a PreToolUse hook blocks edits to linter configs, a stop hook catches config changes at session end, and a Bash hook blocks legacy package managers in favor of uv and bun. Setup is manual (install the linters, copy the hooks and configs into your project), it covers Python, TypeScript, Shell, YAML, JSON, TOML, Markdown and Dockerfiles, and it pairs with ECC rather than replacing it. A community contribution to the ECC collection. By @affaan-m, listed here with credit to its creator, Plankton itself by @alxfazio. From the affaan-m/ECC repository (MIT). Honest caveats: installation is manual, review the hook code before installing it; spawning model subprocesses on every edit costs tokens and time, so tune the language gates and timeouts for your project. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Plankton Write-Time Code Quality is a free Muse skill that enforces code quality on every file edit, with silent auto-formatting, 20-plus linters, Claude-powered fixes with tiered model routing, plus config tamper protection. Every edit triggers a three-phase hook where formatting fixes many issues invisibly, violations are collected as structured JSON, and a subprocess fixes what the agent missed, re-verifying afterward.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: None. No account, no API key, no payment: this skill is a single instruction file for the agent. Install "Plankton Write-Time Code Quality" for me. It enforces code quality at write time with Plankton: auto-formatting, linting, and Claude-powered fixes on every file edit, through hooks. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/plankton-code-quality/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprints below. I want you to compute the SHA-256 of each downloaded file and compare: - SKILL.md: SHA-256 917920552320fdf0927a3bba61107eee8255dab469af80680dea40d671d51866 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none — this is a plain Markdown guidance file and it contacts nothing by itself) - every shell command it runs (expected: none during installation; the file describes workflows my agent may follow later, when the skill is used) - every place credentials, API keys or personal data are read, stored or sent (expected: none) - any obfuscated or encoded code (expected: none — plain Markdown text) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "plankton-code-quality". 6. Verify with no network calls: frontmatter valid, files in place. 7. Report what was installed, where, and what I still need to do myself (for example: the linters and hook setup the skill describes, such as jaq, ruff and uv, are put in place later, when I start using it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.