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.
Install with Tessl CLI
npx tessl i github:supercent-io/skills-template --skill state-management83
Quality
77%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/state-management/SKILL.mdDiscovery
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 trigger term coverage across popular state management libraries. The main weakness is that the capability description uses somewhat abstract language ('implement patterns', 'handles best practices') rather than listing specific concrete actions the skill enables.
Suggestions
Replace vague action phrases with specific concrete actions like 'configure Redux stores, create selectors, set up React Context providers, implement state persistence'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (state management) and lists specific libraries (React Context, Redux, Zustand, Recoil), but the actions are somewhat vague - 'implement patterns' and 'handles best practices' don't describe concrete actions like 'configure stores', 'create 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 | Good coverage of natural terms users would say: 'global state', 'state management', 'React Context', 'Redux', 'Zustand', 'Recoil', 'data flows', 'components'. These are terms developers naturally use when discussing state management needs. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on frontend state management with distinct library names (Redux, Zustand, Recoil) that create unique triggers. Unlikely to conflict with general React skills or backend state management. | 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 code examples covering multiple state management approaches. The main weaknesses are verbosity (could trim metadata, empty examples, and obvious explanations), missing validation/testing guidance for state implementations, and the monolithic structure that could benefit from splitting advanced topics into separate files.
Suggestions
Remove the empty 'Examples' section at the end or populate it with meaningful content - placeholder sections waste tokens
Add a validation/testing step showing how to verify state management is working correctly (e.g., using React DevTools, Zustand devtools, or simple test patterns)
Trim the metadata section and move detailed references to a separate REFERENCES.md file to reduce the main skill's token footprint
Consider splitting Redux Toolkit and advanced patterns into a separate ADVANCED.md file, keeping SKILL.md focused on Context API and Zustand for most use cases
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the 'When to use this skill' section that restates obvious use cases, and the metadata/references sections that add bulk without instructional value. The code examples are good but the surrounding explanations could be tighter. | 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, types, and usage patterns. | 3 / 3 |
Workflow Clarity | The 5-step structure provides a logical progression, but lacks explicit validation checkpoints. For state management, there's no guidance on testing state changes, debugging state issues, or verifying correct implementation. The decision criteria in Step 1 are helpful but subsequent steps don't include verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one large file. The References section links to external docs, but there's no splitting of advanced patterns (like middleware, selectors, or testing) into separate files. The Examples section at the end is empty placeholder content. | 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 | |
- 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.