AB blender-3d-modeling
Blender 3D Modeling: Blender 3D suite running headless in the cloud. Use when an agent needs blender 3d modeling, render turntable videos of 3d models for game asset previews, create multi angle product shots from 3d models for e commerce, convert 3d files between formats like glb to blend, glb to fbx, cancel task, task id, check printability through AgentPMT-hosted remote tool calls. Discovery terms: blender 3d modeling, render turntable videos of 3d models for game asset previews.
Blender 3D Modeling: Blender 3D suite running headless in the cloud.
As a process B 75/100 · Nearly there — weak spots: execution cost, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 13243 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 75/100
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 13243 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 189 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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)
- +1No license
- +2Single-language instructions
- +3Description length 487: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 189 items
- +3Output format is stated explicitly
- +4Has examples (49 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.