CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

component-managing-state

Use whenever designing, implementing, modifying, reviewing, or refactoring component-based UI development (React, Vue, Angular, Svelte, SolidJS, Astro, Flutter widgets, SwiftUI views, etc.). Guides decisions about state ownership, lifting state up, avoiding prop drilling, passing children and slots, Containment and Specialization.

Quality

72%

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/knowledge/component-managing-state/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 as a router with clear routing logic and a defensible conceptual premise, but the skill is broken as bundled: both files the Router points to are missing, leaving only abstract framing with no actionable substance. Redundancy between the Shared Premise and Scope sections further dilutes an otherwise lean 30-line overview.

Suggestions

Include the referenced bundle files: every row of the Router table links to state-ownership.md or component-composition.md, and neither exists in the skill directory, so the skill currently delivers no substantive guidance when its links are followed.

Inline brief definitions of the core concepts the body depends on (Proximity Principle, Containment, Specialization) — or ensure the referenced files define them — so the overview is not built on undefined terms.

De-duplicate the Shared Premise and Scope sections: the co-location prohibition and the "current structure is not the design" warning each appear twice and could be stated once, tightening conciseness.

DimensionReasoningScore

Conciseness

The 30-line body is mostly lean, but the co-location prohibition appears twice ("Do not mechanically co-locate state and logic in the nearest individual consumer" in Shared Premise vs. "do not initially co-locate state in the nearest consumer" in Scope) and the "don't trust current structure" warning is likewise restated across sections. It is not 4 because this duplication exceeds minor over-explanation; not 2 because there is no padding that explains basics Claude already knows.

3 / 5

Actionability

The body offers high-level decision framing ("Identify the UI unit and the component set that implements it first") and a routing table, but every concrete step and example is deferred to state-ownership.md and component-composition.md — and neither file exists in the bundle, so the specific steps to execute are missing entirely. Terms the guidance depends on ("Proximity Principle", "Containment and Specialization") are used but never defined in the body. It is not 3 because there is no partially-complete executable guidance present; the substantive content is wholly absent.

2 / 5

Workflow Clarity

The Router gives an unambiguous decision procedure ("Route by the required design decisions, not terms in the user's request. Read only the necessary documents, and read both when the decisions overlap") with explicit ordering ("Read state-ownership.md first, then component-composition.md"), and Scope separates first-implementation from refactoring. It is not 5 because the identify-the-UI-unit step is scattered across sections rather than presented as a sequenced workflow; not 3 because for a routing skill the if/then logic and reading order are clear, and no validation checkpoints are needed for this non-destructive design-decision skill.

4 / 5

Progressive Disclosure

Scored against the actual bundle structure: the router table is well-signaled and one level deep, but both referenced files (state-ownership.md and component-composition.md) do not exist anywhere in the skill directory — no references/, scripts/, or assets/ directories are present — so every reference is dangling and the content the skill discloses is absent. It is not 1 because the structure and signaling are clear rather than a monolithic or nested chain; not 3 because this is not merely imperfect organization — the entire referenced payload is missing.

2 / 5

Total

11

/

20

Passed

Description

88%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 description: third-person voice, explicit 'Use whenever' trigger clause with concrete conditions, and a comprehensive enumeration of the skill's decision areas with good framework-synonym coverage. The only weaknesses are a few missing natural trigger terms (e.g., "state management", "props") and slight breadth-driven overlap risk with framework-specific skills.

DimensionReasoningScore

Specificity

"Guides decisions about state ownership, lifting state up, avoiding prop drilling, passing children and slots, Containment and Specialization" enumerates six concrete capability areas covering both the state and composition halves of the skill's scope, with no meaningful coverage gaps. It is not 4 because the listed actions comprehensively cover the skill's stated domain rather than leaving minor gaps.

5 / 5

Completeness

The description explicitly answers both questions: what ("Guides decisions about state ownership, lifting state up, avoiding prop drilling, passing children and slots, Containment and Specialization") and when ("Use whenever designing, implementing, modifying, reviewing, or refactoring component-based UI development"). It is not 4 because the 'when' clause is fully explicit with concrete trigger conditions, not merely present or vague.

5 / 5

Trigger Term Quality

"React, Vue, Angular, Svelte, SolidJS, Astro, Flutter widgets, SwiftUI views" plus "prop drilling" and "lifting state up" are phrases users naturally say, with strong framework-synonym coverage. It is not 5 because common natural terms such as "state management", "props", and "composables" are absent; not 3 because coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The niche (state ownership and composition decisions in component UIs) has distinct triggers naming specific frameworks, so it is mostly distinguishable. It is not 5 because "component-based UI development" spanning eight frameworks is a broad surface with minor overlap risk against closely related skills (e.g., a general React-patterns or state-management-library skill); not 3 because the trigger set is clearly tied to this skill's specific decision domains.

4 / 5

Total

18

/

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

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

choegyumin/agent-skills

Path

skills/knowledge/component-managing-state/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.