frontend-state
상태 관리 에이전트. 애플리케이션 상태 관리를 설계하고 구현합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill frontend-state30
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
0%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 description is extremely weak across all dimensions. It provides only a vague category label ('state management agent') without concrete actions, natural trigger terms, or explicit usage guidance. The description would be nearly impossible to distinguish from other development-related skills in a large skill library.
Suggestions
Add specific concrete actions like 'Implements Redux stores, creates React Context providers, designs Zustand stores, manages global application state'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions state management, Redux, Zustand, global state, React context, store setup, or state architecture'
Specify the technology stack or frameworks supported to create distinctiveness (e.g., React, Vue, Angular state management patterns)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like '설계하고 구현합니다' (design and implement) without listing concrete actions. It doesn't specify what kind of state management patterns, tools, or specific operations are supported. | 1 / 3 |
Completeness | Only partially answers 'what' with vague terms and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains only generic terms '상태 관리' (state management) and '애플리케이션' (application). Missing natural trigger terms users would say like Redux, Zustand, React state, global state, store, context, etc. | 1 / 3 |
Distinctiveness Conflict Risk | Very generic description that could conflict with any skill related to application development, architecture, or frontend development. No distinct triggers to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a role description rather than actionable guidance. It lists what the state management agent should do but provides zero concrete implementation details, code examples, or workflows. Claude would not know how to actually design or implement state management from this content alone.
Suggestions
Add concrete code examples showing Context API patterns (e.g., createContext, useContext, Provider setup)
Include a workflow for state management design: 1) Identify state needs, 2) Choose local vs global, 3) Implement pattern, 4) Validate with specific checks
Provide specific patterns or anti-patterns for state optimization (e.g., when to split contexts, memoization strategies)
Reference or link to detailed documentation for complex patterns like state synchronization
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts Claude knows, but it's essentially just a list of responsibilities without actionable content - it's lean but empty rather than efficiently informative. | 2 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The skill only describes what the agent does (Context API 설계, 전역 상태 관리) without showing how to actually implement any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. The skill lists responsibilities but provides no sequence for how to design or implement state management, nor any validation checkpoints. | 1 / 3 |
Progressive Disclosure | Output locations are specified (src/contexts/, src/store/) which provides some structure, but there are no references to detailed documentation, examples, or patterns that would help with actual implementation. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 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.