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

85%

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

82%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 skill body with concrete commands and templates. The main gap is the absence of an explicit validation feedback loop for the generated rules file and hook installation.

Suggestions

Add an explicit verify step after generating .ai-style-rules.md (e.g., re-read the file and confirm all three mandatory sections are present and non-empty) with a fix-and-retry loop, to lift workflow_clarity to 5.

Collapse the redundancy between 'How It Works' and the 'Workflow' section — keep one as the canonical sequence and reference it from the other to tighten conciseness.

Merge 'Best Practices' into 'Anti-Patterns' as positive/negative pairs, or trim overlapping items, to reduce token cost without losing guidance.

DimensionReasoningScore

Conciseness

Dense, action-oriented body using tables and numbered steps with no preamble explaining known concepts; minor redundancy between 'How It Works', 'Best Practices', and 'Anti-Patterns' could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready bash commands, a concrete 4-option grilling-protocol template, named output-file sections, and exact hook mechanisms (settings.json path, @-reference) covering the common cases.

5 / 5

Workflow Clarity

Clear two-branch sequence with an auto-detect gate and one-at-a-time grilling checkpoint; however the file-writing/hook-install steps lack an explicit validate-then-retry feedback loop on the generated rules output.

4 / 5

Progressive Disclosure

No bundle files exist; the body is a single well-sectioned file with clear headers and no nested references, easy to navigate, though it exceeds the simple-skill line count so a 5 is not warranted.

4 / 5

Total

17

/

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.

A strong, specific description with explicit what/when triggers and a negative boundary clause. Slightly more action enumeration in the description itself would push specificity to a 5.

DimensionReasoningScore

Specificity

Names concrete actions ('prevent style drift', 'aligns meta-architecture only, not syntax', 'behavioral constraint on all subsequent coding tasks') with comprehensive domain coverage, though the full action enumeration lives in the body rather than the description itself.

4 / 5

Completeness

Explicitly answers both 'what' (legacy style inheritance, meta-architecture alignment) and 'when' (Use when... onboarding / typing the slash command), and adds an explicit negative trigger ('Do NOT use for pure research...').

5 / 5

Trigger Term Quality

Includes natural user-facing triggers ('/inherit-legacy-style', 'onboarding an AI coding agent onto a hand-written legacy project', 'style drift', 'code-style alignment') with good synonym coverage; a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (legacy-project style inheritance) with an explicit negative boundary that minimizes overlap with general code-review or init skills.

5 / 5

Total

18

/

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.

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.