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

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/knowledge/component-managing-state/SKILL.md

Quality

Content

50%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 conceptually with a clear router and ownership questions, but it is undermined by references to two files that are not actually present and by some repetition. It reads as an overview whose supporting detail is missing.

Suggestions

Provide the referenced state-ownership.md and component-composition.md (or inline their essential guidance), since the router currently points to files that do not exist in the bundle.

Collapse the repeated 'do not co-locate state in the nearest consumer' guidance in Shared Premise and Scope into a single statement to reduce redundancy.

Add a concrete decision checklist or step sequence (e.g., identify UI unit → list ownership questions → choose root → decide content ownership) so the workflow is unambiguous rather than implied.

Dimension	Reasoning	Score
Conciseness	Mostly efficient conceptual prose, but the prohibition on co-locating state in the nearest consumer is restated nearly verbatim across the Shared Premise and Scope sections, and some admonitions could be tightened.	3 / 5
Actionability	It provides concrete decision questions (which component is the set root, who owns content vs. placement) and a routing table, but the main executable path ('Read state-ownership.md') points to files that are not present, leaving the guidance incomplete.	3 / 5
Workflow Clarity	A loose sequence exists (identify UI unit → determine ownership boundaries → route by decision), and there are no destructive/batch operations requiring validation, but the steps are not crisply sequenced with explicit checkpoints.	3 / 5
Progressive Disclosure	The router table clearly signals one-level-deep references to state-ownership.md and component-composition.md, but those referenced files do not exist in the bundle, so the overview points to detail that is missing rather than appropriately split.	3 / 5
	Total	12 / 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.

The description is strong: it states explicit triggers, names concrete capabilities, and lists the relevant frameworks, answering both what and when clearly. Its only gaps are minor—missing file-extension synonyms and a small overlap risk with adjacent UI skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the lifecycle ('designing, implementing, modifying, reviewing, or refactoring') and specific decision areas ('state ownership, lifting state up, avoiding prop drilling, passing children and slots, Containment and Specialization'), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers 'when' ('Use whenever designing, implementing, modifying, reviewing, or refactoring component-based UI development') and 'what' ('Guides decisions about state ownership, lifting state up...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural coverage via explicit framework names ('React, Vue, Angular, Svelte, SolidJS, Astro, Flutter widgets, SwiftUI views') plus the activity verbs users say, but lacks common file-extension synonyms (.jsx, .vue) that would round it out to the top anchor.	4 / 5
Distinctiveness Conflict Risk	The niche (state ownership and composition decisions in component-based UI) is clear and framed with specific frameworks, but it could still overlap with closely related general React/UI styling or component-library skills, so it sits just below minimal-conflict.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: choegyumin/agent-skills
Path: skills/knowledge/component-managing-state/SKILL.md
Commit: 62ef4cc

Reviewed: 3 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.