BC vue-spa-state
按作用域为 Vue 3 SPA 选择并落地状态。仅本组件：ref/computed。父子 1～2 层：props/emit、 v-model。同一页 3+ 层：provide/inject（InjectionKey；改同一份 ref，不要重新 provide）。 跨路由、跨模块、登录态，或同一对象部分字段仅本组件、部分给其他组件：整份进 Pinia。 新 store 用 setup + 箭头函数；选项式只改存量或需要 $reset。含 storeToRefs、store 单向互调、普通函数/守卫/拦截器在 pinia 安装后取 store、按业务域拆分与导出。 在新增或修改 Vue 状态、Pinia、provide/inject、状态管理、跨组件传值， 或判断该用 ref、props 还是 Pinia 时使用。
按作用域为 Vue 3 SPA 选择并落地状态。仅本组件：ref/computed。父子 1～2 层：props/emit、 v-model。同一页 3+ 层：provide/inject（InjectionKey；改同一份 ref，不要重新 provide）。…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1574 tokens
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 360: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.