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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pinia/SKILL.md

The canonical home for this skill is pinia in antfu/skills

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured index that excels at progressive disclosure, pointing cleanly to real reference files. It is slightly weakened by an unnecessary intro paragraph and version stamp, and by the absence of any executable code or workflow sequence in the body itself.

Suggestions

Trim or remove the introductory paragraph explaining what Pinia is and move the version/date stamp into a dedicated note or deprecated section to avoid penalizing conciseness.

Add a brief, executable quick-start code snippet (e.g. defining a setup store with storeToRefs) in the body so guidance is copy-paste ready without forcing a reference hop.

If any common Pinia workflow involves multi-step verification (e.g. SSR hydration or testing setup), surface a short sequenced checklist with a validation step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the opening paragraph re-explains what Pinia is (which Claude knows) and a version/date stamp ('Pinia v3.0.4, generated at 2026-01-28') adds time-sensitive detail outside a deprecated section, so it is not fully lean.	2 / 3
Actionability	The 'Key Recommendations' name specific APIs (storeToRefs, @pinia/testing) and patterns, but the body has no executable code or commands — concrete detail is delegated to references, leaving guidance actionable but incomplete at the copy-paste level.	2 / 3
Workflow Clarity	Content is well-organized but there is no multi-step process or sequence; it is a navigational index with no validation checkpoints, so it does not reach the explicit-sequence-with-checkpoints anchor at 3.	2 / 3
Progressive Disclosure	Clear overview with categorized reference tables (Core, Features, Best Practices, Advanced) pointing one level deep to real files (all 9 referenced files exist), giving easy navigation matching the well-signaled one-level-deep anchor.	3 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, uses third-person/infinitive voice, and explicitly covers both what the skill does and when to trigger it with natural, domain-specific keywords. It avoids fluff and is clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'defining stores, working with state/getters/actions, or implementing store patterns' — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly states what it does ('Pinia official Vue state management library, type-safe and extensible') and when to use it ('Use when defining stores...'), satisfying both what and when with an explicit trigger.	3 / 3
Trigger Term Quality	Includes natural terms users say (Pinia, Vue, state management, stores, state, getters, actions); good coverage rather than the partial-variation coverage at 2.	3 / 3
Distinctiveness Conflict Risk	Scoped to Pinia/Vue state management with distinct triggers (stores, getters, actions), giving it a clear niche unlikely to conflict with unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: JetBrains/skills
Path: pinia/SKILL.md
Commit: e0f258b

Reviewed: 1 month ago

Table of Contents

Discovery Implementation Validation

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.