pinia
Pinia official Vue state management library, type-safe and extensible. Use when defining stores, working with state/getters/actions, or implementing store patterns in Vue apps.
92
87%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 solid skill description that clearly identifies its niche (Pinia for Vue) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the 'what' portion could be more specific about concrete actions rather than just listing concepts. Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions like 'define reactive stores with defineStore', 'compose stores together', 'use plugins for persistence or devtools integration' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Pinia/Vue state management) and mentions some concepts (stores, state/getters/actions, store patterns), but doesn't list specific concrete actions like 'define reactive stores', 'create computed getters', 'compose stores', or 'persist state'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Pinia Vue state management library, type-safe and extensible) and 'when' with an explicit 'Use when' clause covering defining stores, working with state/getters/actions, and implementing store patterns. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Pinia', 'Vue', 'state management', 'stores', 'state', 'getters', 'actions', 'store patterns'. These cover the main terms a developer would use when seeking help with Pinia. | 3 / 3 |
Distinctiveness Conflict Risk | Pinia is a very specific library within the Vue ecosystem, and the description clearly scopes to Pinia stores, state/getters/actions patterns. This is unlikely to conflict with general Vue skills or other state management library skills like Vuex. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured navigation/index skill that excels at progressive disclosure and conciseness. Its main weakness is the lack of any inline executable code examples—even a minimal store definition in a Quick Start section would significantly improve actionability. The Key Recommendations section partially compensates by providing specific, practical guidance.
Suggestions
Add a 'Quick Start' section with a minimal executable store definition example (setup store style) to improve actionability without sacrificing conciseness.
Remove or shorten the introductory paragraph explaining what Pinia is—Claude already knows this, and the description field covers it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. The introductory sentence is borderline unnecessary (Claude knows what Pinia is), but it's brief. The tables and bullet points are efficient, and every section serves a clear navigational purpose without padding. | 3 / 3 |
Actionability | The skill provides no executable code examples or concrete commands in the body itself—it relies entirely on references for actionable content. The 'Key Recommendations' section offers specific, useful guidance (e.g., use storeToRefs(), prefer Setup Stores) but lacks copy-paste-ready code snippets that would make it fully actionable. | 2 / 3 |
Workflow Clarity | Pinia store management is not a destructive multi-step workflow requiring validation checkpoints. The skill clearly organizes topics from core concepts through features, best practices, and advanced topics in a logical progression. For a reference/navigation skill like this, the structure is unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: a concise overview with well-organized tables pointing to one-level-deep reference files. Topics are logically grouped (Core, Features, Best Practices, Advanced) with clear descriptions and direct links. Navigation is easy and intuitive. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- antfu/skills
- Commit
50deaeb
- 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.