BC css-border-gradient
Apply subtle gradient-border treatments for premium web surfaces. Use when cards, pricing panels, nav bars, modals, buttons, or hero surfaces need a refined edge highlight without a loud glow.
Apply subtle gradient-border treatments for premium web surfaces.
As a process C 63/100 · Has gaps — 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Obfuscation
obf-base64-blobdemo/index.html:19Long base64-looking blob (quoted — discussed, not commanded)const encodedHtml = "PCFE…bWw+Cjxo…aCI+Cjxo…OyB
quoted -
low Secrets in code
secret-high-entropy-tokendemo/index.html:19High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const encodedHtml = "PCFE…bWw+Cjxo…aCI+Cjxo…OyB
quoted
Files scanned: 4. 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 63/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
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 673 tokens
- 100Running it twice. No mutating operations
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 192: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.