CtrlK
BlogDocsLog inGet started
Tessl Logo

inherit-legacy-style

Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a hand-written legacy codebase or extracting a project's unwritten coding rules.

68

Quality

83%

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

75%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, well-structured instruction skill with concrete commands, numeric thresholds, and an exact question template for its one-at-a-time conflict protocol. Its main costs are redundancy — the same workflow restated in 'How It Works' and 'Examples' — and the absence of output-validation checkpoints after generating rules or installing hooks.

Suggestions

Delete the 'How It Works' section (a near-verbatim restatement of 'Workflow') and merge 'When to Activate'/'When to Use' into one section to cut roughly a quarter of the body.

Add validation checkpoints after the risky write steps, e.g. verify the generated .ai-style-rules.md contains all three mandatory sections and the CLAUDE.md soft-hook reference resolves before declaring completion.

Move the Grilling Protocol question template and signal-threshold rules into a references/ file (e.g. references/grilling-protocol.md) linked from SKILL.md to slim the main body to a true overview.

DimensionReasoningScore

Conciseness

The workflow is described three times — the detailed 'Workflow' section, a near-verbatim 'How It Works' restatement, and again in 'Examples' — plus overlapping 'When to Activate'/'When to Use' sections. It is mostly efficient with no concept-teaching padding, so it fits anchor 3 ('could be tightened') rather than 2 ('several padded sections') or 4 ('minor instances').

3 / 5

Actionability

Fully concrete guidance throughout: executable commands ('git ls-files | grep -cE ...', 'git log -3 --stat', 'git diff <last_hash> HEAD --stat'), exact thresholds ('minority <5% AND count <10', 'sources ≲50, 3 vs 2 is NOT a majority'), a literal 4-option question template, tier tables with numeric cutoffs, and a precise output file spec. For an instruction-only skill this is copy-paste-ready.

5 / 5

Workflow Clarity

The sequence is clear and well-branching (Step 0 auto-detect → Branch A steps 1–6 / Branch B → per-turn enforcement) with a strong user feedback loop — the Grilling Protocol presents exactly one question and suspends until answered. It falls short of 5 because no step validates outputs, e.g. verifying the generated rules file parses or that an installed hook actually fires.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced (all referenced files are project artifacts like .ai-style-rules.md and settings.json), so there are no dangling references. The ~150-line body is well-sectioned and navigable, but it exceeds the simple-skill threshold and inlines detail (grilling protocol, signal thresholds) that could live in a one-level-deep reference file — matching anchor 4's 'minor organization gaps'.

4 / 5

Total

16

/

20

Passed

Description

92%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: concrete, third-person, artifact-naming capabilities paired with an explicit 'Use when' trigger clause covering both onboarding and rule-extraction scenarios. The only weakness is that a few natural user phrasings around style consistency are absent from the trigger terms.

Suggestions

Add one or two natural user phrasings to the trigger clause, e.g. 'keeping AI-generated code consistent with the project's existing style' or 'matching the codebase's existing conventions'.

Mention that the skill is language/framework-agnostic in the description so users with non-JavaScript legacy stacks recognize it applies to them.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named artifacts — 'scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook' — comprehensive and fully specific, matching the top anchor rather than the 'minor gaps' of 4.

5 / 5

Completeness

It explicitly answers both parts: the 'what' (scan for implicit conventions, resolve conflicts, write .ai-style-rules.md with Golden Files/naming rules/DONTs, optional CLAUDE.md hook) and a concrete 'Use when onboarding an AI agent onto a hand-written legacy codebase or extracting a project's unwritten coding rules' trigger clause, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Good coverage of natural terms ('style drift', 'legacy projects', 'onboarding an AI agent', 'hand-written legacy codebase', 'unwritten coding rules') plus file names (.ai-style-rules.md, CLAUDE.md), but a few phrasings a user would naturally say ('keep AI consistent with our code style', 'match the existing style') are missing, so it sits between anchors 4 and 5, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Clear niche — inheriting unwritten style rules from legacy hand-written codebases — with distinct trigger phrases; only negligible overlap with 'init' via the optional CLAUDE.md write, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.