CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

immutable-patterns

Use when reviewing scripts, client components, bundles, or runtime behavior related to Prefer immutable data patterns. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/immutable-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well structured with a clean one-level reference split to references/rule.md, and the Check/Fix instructions are specific enough to act on. Its weaknesses are conceptual padding Claude doesn't need, and a workflow whose validation is only implied ('verify in the browser') rather than an explicit checkpoint.

Suggestions

Cut or compress the opening conceptual paragraph on why mutation is bad — Claude already knows this — and let references/rule.md's 'Why It Matters' section carry it.

Make the browser verification step an explicit workflow checkpoint in the Code Review section, e.g. 'After fixes: reload the affected flow in the browser and confirm state updates render correctly; if not, re-check for missed mutations'.

Add one short inline before/after snippet (e.g., user.name = ... vs return { ...user, ...changes }) so the flagged patterns are visible without opening the reference file.

DimensionReasoningScore

Conciseness

The opening paragraph ('Mutating shared objects makes it impossible to track where a value changed... time-travel debug') explains immutability benefits Claude already knows, and the Quick Reference bullets duplicate content that lives in references/rule.md. Mostly efficient, but this conceptual padding and duplication could be trimmed.

3 / 5

Actionability

Concrete, specific guidance: 'Flag direct property assignments on function parameters and push/splice on arrays' and 'Replace in-place mutations with immutable patterns using spread operators', with map/filter/reduce named. No inline code, but the instruction-only guidance is actionable and code examples are delegated to references/rule.md; the gap keeping it from 5 is the absence of even one inline before/after example.

4 / 5

Workflow Clarity

Check → Fix → Explain → Code Review provides a recognizable sequence, and 'state how the change should be verified in the browser' gestures at validation, but there are no explicit validation checkpoints or fix-retry feedback loops. Steps are listed with only implicit checkpoints.

3 / 5

Progressive Disclosure

The body is a lean overview under 50 lines with organized sections, and it clearly signals exactly one one-level-deep reference ('see references/rule.md') for code examples and framework guidance; the bundle confirms rule.md holds the bulk detail, so content is appropriately split and easy to navigate.

5 / 5

Total

15

/

20

Passed

Description

58%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 answers both what and when with an explicit 'Use when...' clause, but its trigger vocabulary is thin — it leans on the rule title plus generic review boilerplate rather than the natural terms (mutate, spread, state) a user would actually say. Distinctiveness within a family of identically-templated rules is a moderate risk.

Suggestions

Add concrete trigger phrases users would naturally say, e.g. 'Use when the user mentions mutation, mutating state, spread operators, or immutable updates in React/Redux/Zustand code'.

Enumerate the specific actions the skill performs, e.g. 'flag push(), splice(), and direct property assignment on shared objects; replace them with spread and map/filter/reduce'.

Differentiate the 'when' clause from sibling rule templates by leading with immutable-pattern-specific terms rather than generic 'reviewing scripts, client components, bundles' phrasing.

DimensionReasoningScore

Specificity

Names the domain ('immutable data patterns') and 1-2 concrete actions ('reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path'), but never enumerates the specific violations it flags (e.g., push/splice, direct property mutation) or the fixes it applies, so coverage is not comprehensive.

3 / 5

Completeness

Both 'what' (review and inspect source plus browser execution path) and an explicit 'when' ('Use when reviewing scripts, client components, bundles, or runtime behavior related to Prefer immutable data patterns') are present. Not a 5 because the trigger phrases are boilerplate tied to the rule name rather than concrete user-facing terms; not a 3 because both halves are explicitly stated.

4 / 5

Trigger Term Quality

Includes relevant keywords ('immutable data patterns', 'scripts', 'client components', 'bundles', 'runtime behavior') but omits the most natural user phrasings such as 'mutate/mutation', 'spread operator', or 'state management', so common variations are missing.

3 / 5

Distinctiveness Conflict Risk

The 'immutable data patterns' niche is distinctive, but the surrounding boilerplate ('reviewing scripts, client components, bundles, or runtime behavior') appears to be a template shared across sibling frontendchecklist rules, creating overlap risk with similar skills in the same family.

3 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/immutable-patterns/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.