Skip to content
Agent Orchestration
Skill

/jev-blender

Use for all Blender work. Default code-first execution, local QA and bounded Jev diagnostic advice.

BOOST
From plugin
hermes-jev-skills
1.1k13 skills4 agents
Install
$ npx -y skills add kerpopule/hermes-jev-skills --skill jev-blender --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/jev-blender

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use for all Blender work. Default code-first execution, local QA and bounded Jev diagnostic advice.

SKILL.md

jev-blender.SKILL.md
name: jev-blender
description: Use for all Blender work. Default code-first execution, local QA and bounded Jev diagnostic advice.
version: 1.0.0
license: MIT
metadata:
  hermes:
    tags: [jev, blender, 3d, verification]

Default Blender workflow

Use this entry point for Blender tasks, alongside the task's geometry, animation and production skills. It grants no new paid, public, production, credential or customer-data authority. Do not change model routing or restart a gateway to use it.

Choose execution locally

Use a deterministic background script for a known-ahead build or long final render. For repeated inspect/edit cycles, prefer an installed, owned warm-session adapter with private pipes and isolated preferences. Load `blender-warm-session` when installed. Do not install an unreviewed DSH plugin, adopt an existing Blender GUI or expose a control port. If warm execution is unavailable, use the verified background-script route and disclose the fallback.

Keep one bounded resource owner, a whole-job deadline, an exclusive disposable workspace and explicit source/output identities. Preserve source files. Never detach a worker across turns. Blender exit success alone is not artifact acceptance.

Check before asking a model

Measure applicable geometry, materials, framing and lighting against the task specification. Unknown checks must be measured; failures return to the owning planner for a reviewed repair. Do not label an unperformed or inapplicable check as passed. Apply role-aware topology rules, not a blanket closed-solid assumption. Save native checkpoints before risky edits.

Use `jevkit.blender.select(state)` or pipe the closed JSON schema in `docs/blender.md` into `jev blender-next`. No scene files, screenshots, code, names, paths, free text or private measurements may enter this helper. The only permitted symptoms are its fixed vocabulary. `private=true` always bypasses inference.

Known steps run locally. Jev may prioritize a prevalidated read-only inspection only when the visual cause is unclear and a measured candidate probe costs at least one second. Cap the advice request at one second and the owned loop at two model requests and six probes. Skip Jev for cheap work. Its latency and confidence do not prove the selected cause. Preserve abstentions and failures; never lower confidence to obtain an action.

Jev cannot write Blender code, authorize a scene edit, invent arguments or declare completion. Dispatch only exact caller-owned read-only probe IDs. Verify returned results locally, then let the owning planner author any repair. Stop on stale/no-progress observations, exhausted budgets, unknown IDs or script errors. An unavailable chooser returns control to the local planner, not success.

Finish on real evidence

Re-run failed checks on the repaired artifact. Inspect decoded representative views and applicable motion frames. Reopen native files and independently reimport exports where relevant. Only an explicit local artifact verifier can mark the workflow complete. Close the owned worker and verify cleanup. Report timings, failures and untested boundaries honestly. Synthetic decision tests do not prove artistic quality, fewer agent turns, universal speedups or superiority over MCP.

Read more
Ships withhermes-jev-skills

Give your agent a fast, cheap second brain for the small decisions. Your agent burns frontier-model tokens on things that are not thinking: which model should answer this turn, which of 377 skills to load, which retrieved passages matter, which turns survive

Get the whole plugin

Other skills on hermes-jev-skills.