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.
87
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
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 effectively identifies its niche (Pinia/Vue state management) and includes an explicit 'Use when' clause with relevant trigger terms. The main weakness is that the capability description could be more specific about concrete actions beyond the general 'working with state/getters/actions' phrasing.
Suggestions
Expand specificity by listing concrete actions like 'create reactive stores, persist state, compose stores, handle async actions, integrate with Vue devtools'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Pinia/Vue state management) and mentions some actions (defining stores, working with state/getters/actions, implementing store patterns), but doesn't list comprehensive concrete actions like 'create reactive stores', 'persist state', or 'compose stores'. | 2 / 3 |
Completeness | Clearly answers both what (Pinia Vue state management library, type-safe and extensible) AND when (explicit 'Use when' clause covering defining stores, working with state/getters/actions, implementing store patterns in Vue apps). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Pinia', 'Vue', 'state management', 'stores', 'state', 'getters', 'actions', 'store patterns'. These are terms developers naturally use when working with Vue state management. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - specifically targets Pinia and Vue state management, unlikely to conflict with other skills. The combination of 'Pinia', 'Vue', and specific store terminology creates a unique fingerprint. | 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 index/overview skill that excels at organization and progressive disclosure. It efficiently directs users to detailed reference files while providing key recommendations upfront. The main weakness is the lack of any inline code examples - even a minimal store definition would improve actionability for quick reference.
Suggestions
Add a minimal 'Quick Start' code example showing basic store definition and usage (5-10 lines) to improve actionability without requiring navigation to reference files
Include one concrete code snippet demonstrating storeToRefs() usage since it's highlighted as a key recommendation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. The brief intro assumes Claude knows Vue/state management, and the key recommendations are terse, actionable bullets without unnecessary explanation. | 3 / 3 |
Actionability | The key recommendations provide specific guidance (use storeToRefs, prefer Setup Stores), but there's no executable code in the main skill file. All concrete examples are deferred to reference files, making this an overview without copy-paste ready examples. | 2 / 3 |
Workflow Clarity | This is a reference/overview skill rather than a multi-step process skill. The organization clearly guides users to appropriate reference files based on their task, and the key recommendations provide clear decision points for common scenarios. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-organized one-level-deep references. Topics are logically grouped (Core, Features, Best Practices, Advanced) with descriptive tables linking to specific reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 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.