state-management
Implement state management patterns for frontend applications. Use when managing global state, handling complex data flows, or coordinating state across components. Handles React Context, Redux, Zustand, Recoil, and state management best practices.
83
77%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/state-management/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with explicit 'Use when' guidance and good coverage of relevant library names and trigger terms. The main weakness is that the capabilities could be more concrete—listing specific actions like 'create stores', 'configure middleware', or 'implement selectors' rather than the abstract 'implement patterns' and 'best practices'.
Suggestions
Replace abstract phrases like 'implement state management patterns' and 'best practices' with concrete actions such as 'create stores, configure reducers, set up selectors, handle async actions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (state management) and lists specific libraries (React Context, Redux, Zustand, Recoil), but 'implement state management patterns' and 'best practices' are somewhat abstract rather than concrete actions like 'create stores', 'configure reducers', or 'set up selectors'. | 2 / 3 |
Completeness | Clearly answers both what ('Implement state management patterns') and when ('Use when managing global state, handling complex data flows, or coordinating state across components') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'global state', 'Redux', 'Zustand', 'Recoil', 'React Context', 'state management', 'data flows', 'components'. These cover common variations and library names users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on frontend state management with distinct library names (Redux, Zustand, Recoil) that are unlikely to conflict with other skills. The combination of 'global state' and specific library names creates a distinct trigger profile. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples covering multiple state management approaches. However, it's verbose for what Claude needs (explaining basic concepts), lacks validation/testing checkpoints in the workflow, and could benefit from splitting detailed examples into separate reference files. The empty Examples section at the end and placeholder content reduce overall quality.
Suggestions
Remove explanatory text about basic concepts (what props drilling is, why state management matters) - Claude knows this. Focus on patterns and code only.
Add validation checkpoints: how to verify state is working correctly, debugging tips, common errors to check for before considering implementation complete.
Move detailed library implementations (Zustand cart, Redux todos) to separate reference files and keep SKILL.md as a concise overview with quick-start snippets.
Complete or remove the empty 'Examples' section at the end - placeholder content reduces credibility.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., explaining what props drilling is, basic React concepts). The content could be tightened by removing explanatory text Claude already knows and focusing purely on patterns and code. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete TypeScript implementations for Context API, Zustand, Redux Toolkit, and React Query. All examples are copy-paste ready with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | The 5-step process is clearly sequenced for choosing and implementing state management, but lacks validation checkpoints. No guidance on testing state logic, debugging state issues, or verifying correct implementation before proceeding. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic (~400 lines) with inline examples that could be split into separate reference files. The References section links to external docs but related skills links are placeholders. Examples section at the end is empty. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (553 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.