CtrlK
BlogDocsLog inGet started
Tessl Logo

inherit-legacy-style

Legacy-project style inheritance skill. Use when the user types /inherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent "style drift" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.

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

77%

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-sequenced workflow with concrete commands and strong validation feedback loops. The main drag is conciseness — 'How It Works' and 'Examples' duplicate the Workflow — and the absence of any bundle files leaves a monolithic single-file structure.

Suggestions

Collapse or remove the 'How It Works' section — it restates the Workflow; let the Workflow and 'Per-Turn Enforcement' carry the mechanism.

Trim the 'Examples' section to one short scenario or move the three worked examples into a separate references file referenced one level deep.

Move the tier/signal-threshold tables and the 4-dimension scan detail into a reference file, keeping SKILL.md as a lean overview that points to it.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but the 'How It Works' section restates the Workflow in prose and 'Examples' re-derives the same branches, so some tokens do not earn their place; it could be tightened by collapsing the redundant sections.

2 / 3

Actionability

Fully concrete and executable: real commands ('git ls-files | grep -cE ...', 'git diff <last_hash> HEAD --stat'), exact 4-option grilling format, tier/signal-threshold tables, and a precise three-section spec for '.ai-style-rules.md'.

3 / 3

Workflow Clarity

Clear branching sequence (Step 0 auto-detect → Branch A 6 steps / Branch B 5 steps) with explicit checkpoints (signal-threshold noise reduction, one-at-a-time grilling that suspends until answered) and an Anti-Patterns checklist guarding fragile operations.

3 / 3

Progressive Disclosure

No bundle files exist, so all content lives in a single ~150-line SKILL.md; it is well-sectioned but monolithic, and the redundant 'How It Works'/'Examples' content is inline material that could be split or trimmed rather than referenced one level deep.

2 / 3

Total

10

/

12

Passed

Description

90%

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, well-targeted description with explicit what/when triggers and a useful exclusion clause. Its only weakness is that the named actions are conceptual ('align meta-architecture') rather than concrete operations.

DimensionReasoningScore

Specificity

Names the domain and several capabilities ('prevent style drift', 'aligns meta-architecture only, not syntax', 'becomes a behavioral constraint'), but the actions are meta-level concepts rather than the concrete file operations that anchor a 3.

2 / 3

Completeness

Clearly answers what ('Legacy-project style inheritance skill... aligns meta-architecture only, not syntax') and when (explicit 'Use when...' clause with multiple triggers and a negative-trigger exclusion).

3 / 3

Trigger Term Quality

Strong natural-language triggers users would actually say: 'onboarding an AI coding agent onto a hand-written legacy project', 'style drift', and the slash command '/inherit-legacy-style', plus a 'Do NOT use for...' exclusion.

3 / 3

Distinctiveness Conflict Risk

A clear niche (legacy style inheritance / drift prevention) with distinct triggers and an explicit 'Do NOT use for pure research or one-off questions' guard, making mis-triggering unlikely.

3 / 3

Total

11

/

12

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.

Validation14 / 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.