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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill pinia-store-setupActivation
22%This description is severely underdeveloped, essentially just a title with auto-generated metadata. It provides no information about what actions the skill performs with Pinia stores and lacks explicit guidance on when Claude should select it. The duplicate trigger term suggests minimal effort in crafting the description.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Pinia stores with state, getters, and actions. Configures store modules, implements composable patterns, and sets up TypeScript typing for stores.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about Vue state management, creating Pinia stores, defineStore, store composition, or migrating from Vuex.'
Include file type triggers like '.ts store files', 'stores directory', or mention specific Pinia concepts like 'getters', 'actions', 'state' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names 'Pinia Store Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'creates', 'configures', 'manages', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and the 'when' is only implied through the trigger terms. There's no explicit 'Use when...' clause or description of capabilities. | 1 / 3 |
Trigger Term Quality | Includes 'pinia store setup' as a trigger term (duplicated), which is relevant but misses common variations users might say like 'state management', 'Vue store', 'Pinia configuration', 'create store', or 'defineStore'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'Pinia' is specific to Vue.js state management, the lack of detail about what aspects of Pinia it handles could cause overlap with other Vue or state management skills. The generic 'Frontend Development' category doesn't help distinguish it. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual Pinia-specific guidance. It contains zero executable code, no store setup patterns, and no concrete instructions. The content describes what a skill should do rather than actually teaching how to set up Pinia stores.
Suggestions
Add executable code examples showing basic Pinia store creation with defineStore(), including state, getters, and actions
Include a concrete workflow: 1) Install pinia, 2) Create store file, 3) Register in main.ts, 4) Use in components with useStore()
Provide specific patterns like composition API vs options API store syntax, and when to use each
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual Pinia configuration examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Pinia stores. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance for setting up Pinia stores. The content describes what the skill does abstractly rather than providing executable instructions or examples. | 1 / 3 |
Workflow Clarity | No workflow steps are provided. Claims to provide 'step-by-step guidance' but includes zero actual steps for creating or configuring a Pinia store. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 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.