BD decorators
Vovk.ts decorators — built-in (`@prefix`, `@operation`, `@get/@post/@put/@patch/@del`, `.auto()`) and custom via `createDecorator`. Covers authorization / auth decorators, middleware-style wrapping (pre-handler + post-handler logic), `req.vovk.meta()` for cross-decorator state, stacking order, and the local (`.fn()`) vs HTTP context distinction. Use whenever the user asks to "write a custom decorator", "add auth middleware", "protect an endpoint", "build an authorization decorator", "createDecorator", "stack decorators", "share data between decorator and handler", "prefix all routes", "@auto", "decorator execution order". Does NOT cover procedure authoring → hand off to `procedure` skill. Does NOT cover `@operation` for OpenAPI beyond auth-related fields → hand off to `openapi` skill. Does NOT cover `@operation.x-tool` for tool derivation → hand off to `tools` skill.
A skill covering Vovk.ts decorators — both built-in (@prefix, @operation, @get/@post, etc.) and custom ones via createDecorator. Handles authorization, middleware patterns (pre/post logic), state sharing via req.vovk.meta(), decorator stacking order, and the local vs HTTP context split.
The description is lean and structured: it lists the cases where you'd reach for this skill (write a custom decorator, add auth, protect an endpoint). The file holds 3321 body tokens with no critical findings. Grade B signals solid material with room for improvement — likely some examples or edge cases are thin.
If you're building secured endpoints or layering complex middleware in Vovk, the skill fits. Worth installing if decorators are part of your workflow.
Vovk.ts decorators — built-in (@prefix, @operation, @get/@post/@put/@patch/@del, .auto()) and custom via createDecorator. Covers authorization / auth…
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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
✓ No remarks against the Agent Skills spec
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
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 19 steps, 3 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3321 tokens
- 100Progress reporting. Reports progress
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 879: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +4Structure: 19 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.