code-pattern-extractor

Analyze codebases to identify reusable code patterns, duplications, and implementation patterns for future development. Use when refactoring code, identifying technical debt, finding opportunities for abstraction, or documenting common patterns in a directory or module. Outputs pattern catalogs, refactoring suggestions, and reusable template code.

1.40x

Quality

77%

Does it follow best practices?

Impact

76%

1.40x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/code-pattern-extractor/SKILL.md

Quality

Content

61%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 thorough, well-structured analysis workflow with concrete output templates and a clear seven-step sequence. Its main weaknesses are repeated content that bloats token usage and a lack of validation checkpoints in the workflow.

Suggestions

Add validation checkpoints to the workflow, e.g. after scanning for duplications add a step to 'Verify candidate patterns are genuine duplications (not coincidental similarity) before cataloging them', and a review gate before emitting refactoring suggestions.

Deduplicate detection criteria — the 'Analysis criteria' in step 2 and the 'Code duplication detection' heuristics cover the same ground; consolidate into one place to tighten the token budget.

Move the detailed pattern-entry, refactoring-suggestion, and template-code format blocks into a separate references file (e.g. references/FORMATS.md) and summarize them inline, improving progressive disclosure and conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient actionable content (templates, formats, heuristics) without over-explaining basic concepts, but detection criteria are restated across steps 2 and the heuristics section and the categorization is repeated, so it could be tightened; not severe enough for a 2, not lean enough for a 4.	3 / 5
Actionability	Provides concrete copy-pasteable templates (pattern entry format, refactoring suggestion format, output structure) plus a real executable fetch example, but the template-code section uses placeholder skeletons (param1/param2, [N]) rather than fully realized examples, leaving minor gaps.	4 / 5
Workflow Clarity	The seven steps are clearly numbered and sequenced, but there are no validation or verification checkpoints (e.g., confirming detected patterns are genuine, reviewing findings with the user before recommending refactors), so it matches the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Well-organized single file with clear section headers and no nested or buried references, but at ~210 lines with several inlined format templates and heuristics that could live in separate reference files, it has minor organization gaps rather than the ideal split structure of a 5.	4 / 5
	Total	14 / 20 Passed

Description

83%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, third-person description that clearly states capabilities and provides explicit 'Use when' triggers with natural phrasing. Minor distinctiveness overlap with general refactoring skills and slight keyword redundancy are the only weaknesses.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('identify reusable code patterns, duplications, and implementation patterns', 'Outputs pattern catalogs, refactoring suggestions, and reusable template code') with only minor coverage gaps; the repetition of 'patterns' slightly limits comprehensiveness, keeping it just below a 5.	4 / 5
Completeness	Explicitly answers both 'what' (analyze codebases to identify patterns/duplications and output catalogs, suggestions, template code) and 'when' ('Use when refactoring code, identifying technical debt, finding opportunities for abstraction, or documenting common patterns') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users actually say ('refactoring code', 'identifying technical debt', 'finding opportunities for abstraction', 'documenting common patterns'); a few synonyms or language-specific terms are missing, so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The pattern-catalog and refactoring-suggestion outputs carve a fairly distinct niche with clear triggers, but 'refactoring code' and 'technical debt' overlap somewhat with general code-review or refactoring skills, leaving minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: ArabelaTso/Skills-4-SE
Path: skills/code-pattern-extractor/SKILL.md
Commit: 4f38503

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.