CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

separate-responsibilities

Find god files and separate mixed responsibilities into cohesive, independently understandable units. Use when reviewing oversized files, tangled modules, smart and dumb component boundaries, logic mixed with rendering, or code that changes for unrelated reasons.

Quality

87%

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

86%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.

The body is a tight, well-organized instruction-only skill that adds genuine domain judgment without padding. It earns high marks for conciseness and structure, with only minor room for sharper workflow feedback loops.

Suggestions

Add an explicit validate-fix-retry loop to the refactoring sequence (e.g., 'if checks fail, fix the extraction and re-run checks before proceeding') to strengthen workflow clarity for batch/destructive changes.

Make the post-extraction checkpoint more concrete by naming the specific checks to run (tests, typecheck, lint) rather than 'the relevant checks'.

DimensionReasoningScore

Conciseness

Lean and efficient with every section earning its place; assumes Claude's competence and adds only domain-specific judgment, not basic programming concepts.

5 / 5

Actionability

Provides a concrete signals list, sharp decision rules ('A render file with a large prop surface... is not dumb'), and a refactoring sequence; as an instruction-only skill it lacks code but the guidance is specific and actionable.

4 / 5

Workflow Clarity

The 'Refactoring sequence' is clearly ordered with a validation checkpoint ('preserve behavior and run the relevant checks after each coherent extraction'); minor gaps in explicit error-recovery feedback loops keep it below 5.

4 / 5

Progressive Disclosure

A single self-contained skill (~58 lines) with no need for external references and well-organized section headers; the content is appropriately scoped to one file with clear navigation.

5 / 5

Total

18

/

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.

The description is concrete and well-structured, explicitly pairing a clear 'what' with a rich 'when' clause full of natural trigger phrases. It is slightly shy of top marks on specificity and trigger coverage only because a few common synonyms are absent.

DimensionReasoningScore

Specificity

Names the domain (god files, mixed responsibilities) and concrete actions (find, separate into cohesive units) plus several specific signals; minor gaps in coverage keep it just below a 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Find god files and separate mixed responsibilities into cohesive, independently understandable units') and 'when' ('Use when reviewing oversized files, tangled modules...').

5 / 5

Trigger Term Quality

Includes natural review-oriented phrases users would say ('reviewing oversized files', 'tangled modules', 'smart and dumb component boundaries') with good coverage, missing a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (god files and responsibility separation) with distinct triggers; minor overlap risk with general refactoring or code-review skills.

4 / 5

Total

17

/

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

mcclowes/skills

Path

skills/separate-responsibilities/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.