pinia-store-setup
Pinia Store Setup - Auto-activating skill for Frontend Development. Triggers on: pinia store setup, pinia store setup Part of the Frontend Development skill category.
35
3%
Does it follow best practices?
Impact
95%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/pinia-store-setup/SKILL.mdQuality
Discovery
7%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 minimal and essentially just restates the skill name without providing any useful detail about capabilities, use cases, or trigger scenarios. It reads as auto-generated boilerplate with a duplicated trigger term, offering almost no guidance for Claude to determine when to select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Pinia stores with state, getters, and actions using the Composition API or Options API pattern.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about Vue state management, creating Pinia stores, defineStore, composable stores, or migrating from Vuex.'
Include natural keyword variations users might say such as 'Vue store', 'state management', 'Vuex alternative', 'defineStore', 'reactive state', or 'store composition'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names 'Pinia Store Setup' without describing any concrete actions. There are no specific capabilities listed such as creating stores, defining state/getters/actions, or configuring Pinia plugins. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'pinia store setup' repeated twice. Missing natural variations users might say like 'Vue state management', 'create a store', 'defineStore', 'Pinia plugin', 'composable store', or 'Vue store'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Pinia' does narrow the domain to a specific Vue.js state management library, which provides some distinctiveness. However, the lack of detail about what aspects of Pinia it covers could cause overlap with general Vue or state management skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill contains no actual instructional content about Pinia store setup. It is entirely a meta-description of what the skill claims to do, without any code, commands, patterns, or concrete guidance. It would provide zero value to Claude when attempting to help a user set up a Pinia store.
Suggestions
Replace the meta-description sections with actual Pinia store setup code, e.g., a complete example using `defineStore()` with state, getters, and actions in the Composition API style.
Add a concrete workflow: 1) Install pinia, 2) Create store file, 3) Register in main.ts, 4) Use in component—with executable code for each step.
Remove all 'When to Use', 'Example Triggers', and 'Capabilities' sections—these are trigger metadata, not instructional content. Replace with actionable patterns like Options API vs Setup Store syntax.
Include common pitfalls or validation guidance, such as ensuring the Pinia plugin is registered before store usage, or TypeScript typing patterns for stores.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about Pinia store setup. Every section describes the skill rather than teaching it. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no specific Pinia API usage, no store definition patterns. The content is entirely vague and descriptive, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. The phrase 'step-by-step guidance' is promised but never delivered. There are no validation checkpoints or any actual process described. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no meaningful structure, no references to detailed files, and no actual technical content to organize. The sections are all boilerplate headers with no substance. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.