SKILLEMALL.ai

AC avoid-eval

Use when reviewing scripts, client components, bundles, or runtime behavior related to Never use eval() or unsafe dynamic code execution. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

thedaviddias/Front-End-Checklist Agent Skills author: thedaviddias 2 files body ≈ 437 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
63/100
Has gaps
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

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: 2. 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
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 4 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 437 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
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 237: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 4 items
    • +4Reference files are cited in the instructions (1 of 1)

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