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.
40
11%
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
22%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 thin and template-like, providing almost no useful information beyond the skill name. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The duplicated trigger term ('pinia store setup, pinia store setup') suggests auto-generated content without human review.
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 scenarios, e.g., 'Use when the user asks about Vue state management, creating Pinia stores, defineStore, or migrating from Vuex to Pinia.'
Include common keyword variations users might use such as 'Vue store', 'state management', 'defineStore', 'Vuex alternative', 'reactive state', or 'composition API store'.
| 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 barely answers 'what does this do' beyond the title, and the 'when' clause is essentially just restating the skill name as trigger terms. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | It includes 'pinia store setup' as a trigger term (duplicated), which is a relevant keyword. However, it misses common variations users might say like 'Vue state management', 'Pinia getters', 'Pinia actions', 'Vue store', 'defineStore', or 'composition API store'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Pinia' provides some specificity that distinguishes it from generic state management or Vuex skills, but the lack of detail about what specific Pinia tasks it handles could cause overlap with other frontend or Vue-related skills. | 2 / 3 |
Total | 6 / 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 is essentially a placeholder with no actionable content. It repeatedly describes itself in abstract terms ('provides automated assistance for pinia store setup') without ever showing how to set up a Pinia store—no code, no commands, no concrete patterns. It would provide zero value to Claude beyond what it already knows.
Suggestions
Add concrete, executable code examples showing Pinia store setup (e.g., defineStore with state, getters, actions using the Composition API style).
Include a clear workflow: 1) install pinia, 2) create store file, 3) register in main.ts, 4) use in components—with actual code for each step.
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) that describe the skill rather than teaching the task.
Add project-specific conventions or patterns that go beyond basic Pinia documentation, such as store organization patterns, typing best practices, or testing approaches.
| 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. Every section restates the same vague idea—that it helps with 'pinia store setup'—without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance: no code examples, no Pinia store definition patterns, no setup instructions, no commands. The skill describes rather than instructs, 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 mentioned as a capability but never delivered. There are no validation checkpoints or process descriptions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to reference either, but the content itself lacks any meaningful organization. | 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
13d35b8
- 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.