SKILLEMALL.ai
GitHub ↗ RU Sign in

BD c3d-cadquery-forms

Use when writing CadQuery src/model.py - baseline, part, detail, refine, rebuild or repair: build the planned forms and get past the OCC kernel. Gives the kernel's native makers per form as an optional toolbox, the probed kernel rules that decide whether the script builds at all, a few strong optional practices, and the four traps our own lint and runtime wrapper are written to catch.

gaoypeng/3dcodeverse Agent Skills author: gaoypeng 2 files body ≈ 1 731 tokens Open the sourcegithub.com↗ analyzed 5 d ago

py - baseline, part, detail, refine, rebuild or repair: build the planned forms and get past the OCC kernel.

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

GeneratorData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
D
49/100
Unfinished process
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 49/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1731 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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +2Single-language instructions
    • +3Description length 387: enough signal without eating the budget
    • +4Structure: 5 headings
    • +3Step-by-step instructions: 9 items
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

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