SKILLEMALL.ai

AD transformers-js

Use Transformers.js to run state-of-the-art machine learning models directly in JavaScript/TypeScript.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 9 files body ≈ 341 tokens Open the sourcegithub.com analyzed 2 d ago

Use Transformers.js to run state-of-the-art machine learning models directly in JavaScript/TypeScript.

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

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: transformers-js (sickn33/agentic-awesome-skills)

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: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"

    Process rating: all ten parameters 49/100

    • 0Result and completion. Does not say what the result is
    • 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
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 8 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 341 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)
    • +3Description length 102: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +2Single-language instructions
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 8 items
    • +4Reference files are cited in the instructions (1 of 8)
    • +1License stated

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