SKILLEMALL.ai

AD vscode-extension-builder-lawvable

Build VS Code extensions from scratch or convert existing JS/React/Vue apps. Supports commands, webviews (React/Vue), custom editors, tree views, and AI agent integration via file-bridge IPC. Use when user wants to create a VS Code extension, convert a web app to an extension, add webviews or custom UIs to VS Code, implement tree views, build custom file editors, integrate with AI agents, or package/publish extensions (.vsix).

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 39 files · 14 scripts body ≈ 1 773 tokens Open the sourcegithub.com↗ analyzed 75 min ago

Build VS Code extensions from scratch or convert existing JS/React/Vue apps.

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorVS CodeSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
D
39/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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: 39. 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 39/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. 5 mutating operations with no state check
    • 40Consistency. Frontmatter name (vscode-extension-builder-lawvable) differs from the folder (vs-code-extension-antoine-louis)
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 100Steps. 14 steps
    • 100Execution cost. Instruction body is 1773 tokens
    • low 11 top-level sections: this looks like several domains in one skill

    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
    • +2Single-language instructions
    • +3Description length 430: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 14 items
    • +4Has examples (12 code blocks)
    • +4Reference files are cited in the instructions (8 of 8)
    • +1License stated

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