CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ipollowork-maintainable-code

Mandatory iPolloWork code-change gate for modern, minimal, performant, reuse-first implementation and clean repository ownership. Use whenever AI creates, edits, deletes, or refactors application code, server code, packages, scripts, tests, dependencies, schemas, routes, UI, or generated-file workflows. Reuse existing code before creating files, keep one source of truth, prevent parallel implementations and junk directories, justify every new file or dependency, and audit the current change before completion.

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

73%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 well-structured, highly actionable policy skill with an explicit sequenced workflow, validation feedback loop, and a real, well-placed one-level reference and audit script. Its weaknesses are cross-section rule repetition that inflates token cost and a SKILL.md that carries the entire policy rather than splitting repo-placement detail into the existing reference.

Suggestions

Consolidate repeated rules: state the single-owner, junk-path, and no-single-caller-abstraction rules once in the Creation Gate, and remove their restatements in Non-Negotiable Outcomes, Reuse Decision, and Completion Standard.

Move the Frontend Rules and Server placement tables into references/repository-boundaries.md (which already contains a placement map) and keep SKILL.md to the workflow, gates, and a pointer to that reference.

Include the exact typecheck/test commands per verification category (e.g., the owning package's script names) so the Verification By Risk section is copy-paste executable like the audit command.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and never explains concepts Claude already knows — but it restates the same rules multiple times: single-owner/one-source-of-truth appears in Non-Negotiable Outcomes, Creation Gate, Server, and Completion Standard; junk/dead paths ('new', 'old', 'v2', abandoned files) appear in three sections; 'do not add a generic abstraction for one caller' appears in both Creation Gate and Reuse Decision. Mostly efficient, but it could be tightened by consolidating these repetitions. Not a 4 because the redundancy is more than minor (the Non-Negotiable Outcomes section largely previews later sections); not a 2 because there is no padded explanation or filler.

3 / 5

Actionability

Mostly executable guidance: concrete search targets ('Search... with `rg`' over named directories like `apps/app/src/components/ui`, `apps/server/src`, `packages/types`), an exact audit command ('node .codex/skills/ipollowork-maintainable-code/scripts/audit-changes.mjs'), a situation→action decision table, and concrete checks like 'git diff --check'. Not a 5 because key verification steps name the activity ('run the owning package typecheck and focused tests') without the actual commands, and several gates remain policy statements rather than executable steps.

4 / 5

Workflow Clarity

The 'Required Workflow' is a clearly sequenced 9-step process with explicit validation checkpoints and a feedback loop — step 8 runs package checks plus the audit script, step 9 says 'Resolve every error. Fix warnings or give a concrete... reason' — supplemented by a risk-based verification matrix and a completion checklist. This matches the 5 anchor (explicit validation, error-recovery loop, checklist) rather than the 4 anchor, which requires a validation gap.

5 / 5

Progressive Disclosure

Good structure: the single reference ('Read references/repository-boundaries.md before adding a file, directory, dependency...') is well-signaled at the exact decision point, is one level deep, and is a real, substantive bundle file; the audit script is likewise real. Not a 5 because SKILL.md is the full policy document (~125 lines) rather than an overview — the Frontend Rules and Server/Generated Files placement rules largely duplicate the reference's placement map and could be split out; not a 3 because what references exist are clearly signaled and organized.

4 / 5

Total

16

/

20

Passed

Description

80%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 description that clearly and explicitly states both what the skill enforces and when to use it, with concrete policy actions and good domain keywords. Its main weaknesses are the broad all-code-changes trigger (overlap risk with other code skills) and policy-level rather than operational phrasing.

Suggestions

Narrow the trigger clause to the owning context (e.g., 'Use when creating, editing, or refactoring code in the iPolloWork repository') to reduce overlap with generic code, testing, or review skills.

Add natural synonyms users would say — 'fix', 'update', 'add a feature', 'clean up code' — to the trigger enumeration so it matches how users actually phrase code-change requests.

DimensionReasoningScore

Specificity

Lists several specific concrete actions — "Reuse existing code before creating files", "keep one source of truth", "prevent parallel implementations and junk directories", "justify every new file or dependency", "audit the current change before completion" — covering the gate's behaviors with only minor gaps. It is not a 5 because the phrasing stays at the policy level rather than naming fully operational actions, and not a 3 because far more than 1-2 concrete actions are enumerated.

4 / 5

Completeness

Explicitly answers both parts: the 'what' is a concrete enumeration ("Reuse existing code... keep one source of truth... prevent parallel implementations... justify every new file or dependency... audit the current change") and the 'when' is an explicit trigger clause ("Use whenever AI creates, edits, deletes, or refactors application code, server code, packages..."). This matches the 5 anchor's 'both what AND when with concrete trigger phrases' exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "creates, edits, deletes, or refactors" plus "application code, server code, packages, scripts, tests, dependencies, schemas, routes, UI" — terms users actually say. It falls short of the 5 anchor because common synonyms like "fix", "update", "add a feature", or file extensions (.ts, .tsx) are absent, but it clearly exceeds the 3 anchor's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The niche itself is distinct (an iPolloWork maintainability/code-quality gate), but the trigger fires on essentially every code change ("whenever AI creates, edits, deletes, or refactors... code, packages, scripts, tests, dependencies, routes, UI"), creating real overlap risk with any other code-related skill (testing, review, refactoring skills). Not a 2 because the branded, narrow 'what' prevents generic collision; not a 4 because the trigger scope is maximally broad within the code domain.

3 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Devin-AXIS/iPolloWork

Path

.codex/skills/ipollowork-maintainable-code/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.