SKILLEMALL.ai
GitHub ↗ RU Sign in

BD vue-patterns

Vue.js 3 Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns. Activates for Vue, Nuxt, Vite, or Pinia projects. Use when building or reviewing Vue 3, Nuxt, or Pinia code — Composition API, reactivity, or router navigation.

affaan-m/everything-claude-code Agent Skills author: affaan-m MIT 1 file body ≈ 3 178 tokens Open the sourcegithub.com↗ analyzed 24 h ago

Vue.js 3 Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns.…

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: everything-claude-code

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "origin"

    Process rating: all ten parameters 49/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 85Steps. 31 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3178 tokens
    • 100Running it twice. No mutating operations
    • low 13 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (4 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 316: enough signal without eating the budget
    • +4Structure: 41 headings
    • +3Step-by-step instructions: 31 items
    • +4Has examples (20 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.