agentleFS
SamuelAsherRivelloSamuelAsherRivello/ai-skills-blender/skills/blender-render/SKILL.md

blender-render

Skill11 starsChanged 36 days agoMITView on GitHub

Render existing Blender scenes to still images or frame sequences with preview checks and verified outputs.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify readiness and identify still/sequence output requirements and source scene.

    line 24
  2. Distinctive:

    Verify dimensions, format, alpha and complete frame coverage.

    line 32
  3. Very specific:

    Use scripts/verify_outputs.py for PNG output manifests.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

blender-render

Inputs and scope

Accept existing scene, camera, output path/format/resolution; default to existing usable settings and bounded preview. Also accept optional setting, action/pose, composition, camera, lighting/mood, palette, user references, output specifications and technical constraints when relevant. State assumptions; ask only when a missing answer materially changes the work. A textual style works without reference images. The shared render-style gallery is optional: use an explicitly supplied path or known checkout, inspect a chosen PNG before drawing conclusions, and never fetch missing images automatically.

Use the separately configured official Blender Lab MCP connection. Discover its tools and confirm read-only scene access before mutations; report a connection blocker instead of switching servers. Preserve unrelated objects and settings, scope new content by named collection/run, and checkpoint before destructive edits. Repeated scripts must replace only owned output or create a separate named run. Do not start paid services without authorization.

Use the existing MCP connection whenever it can perform the operation. On Windows, auxiliary execution MUST remain windowless, including brief flashes, during setup, diagnostics, rendering, export, and verification. Before launching, establish suppression for the complete process chain, including client-owned and dependency-owned startup. Use explicit no-console creation (such as subprocess.CREATE_NO_WINDOW) and captured output for reviewed console-only commands. If any required boundary is unknown or unsupported, do not launch: report BLOCKED with the reason and next action, and continue independent safe work. Never retry through a visible terminal, toggle Blender's system console, or weaken suppression. An absolute executable path, cmd /c, Blender --background, or Start-Process -WindowStyle Hidden alone is not proof of no flashes. Keep exit status, bounded timeouts, useful diagnostics without secrets, and cleanup of owned descendants. Do not hide, minimize, restore, focus, or close the existing Blender editor to suppress auxiliary windows. Preserve fresh editor-readiness checks before screenshots.

Parallel visual target and feedback

At the start of a new top-level 3D task, launch one subagent using blender-create-visual-target-2d with the exact prompt, constraints, supplied references/current-scene preview, unchanged features, task ID and an exclusive target directory. Continue Blender inspection and construction immediately while it prepares the prompt-specific target. Nested skills reuse the same pending/completed worker; do not launch one per skill. The target worker must not mutate Blender or recursively delegate.

When it returns, inspect the target and compare a genuine current preview, prioritize visible gaps, apply in-scope corrections and inspect again against the same target version. Use the requested iteration budget, otherwise up to two focused correction passes; report remaining gaps. Preserve render/export/audit-only scope and existing-asset identity. Follow the target skill's parallel-feedback reference when available. If delegation or image generation is unavailable, use parent-side preparation or a supplied target, disclose any prompt-only fallback, and never claim an unperformed comparison. Pure setup checks and explicit user opt-outs bypass this default.

Workflow

  1. Verify readiness and identify still/sequence output requirements and source scene.
  2. Preflight camera, visibility, missing assets, frame range and output destination.
  3. Select a supported render engine/device and report any fallback.
  4. Set a modest preview resolution/sample budget; cap requested frame batches.
  5. Render the preview without overwriting unrelated outputs.
  6. Inspect composition, noise, materials, transparency and exposure against the requested style and any supplied references. Identify the largest visible mismatch and route it to modeling, materials, or lighting before increasing render quality. Samples cannot repair missing construction depth, poor framing, or a mismatched visual treatment.
  7. Record final settings, version, source path and expected files in a run manifest.
  8. Render final output; resume only verified frames from the same source/settings and use a fresh run if settings changed.
  9. Verify dimensions, format, alpha and complete frame coverage; inspect representative final images.
  10. Deliver source, output paths, settings, evidence and any unverified quality/engine assumptions. For requested iteration studies, retain each attempt, select by inspected brief compliance rather than recency, and distinguish visual shortcomings from file-validation failures. Record build time separately from render time; treat a stated soft timing target as a trade-off, not permission to weaken the brief silently.

Execution notes

Use scripts/verify_outputs.py for PNG output manifests. It verifies structure and requested dimensions/channels, not artistic quality or alpha coverage. Run with --help. Actual image inspection remains required. Save the source before recording its path.

Delivery and evidence

Provide editable source and requested outputs, relevant settings/seed/version, observed checks and remaining limitations. Inspect actual images for visual claims. File existence alone is not proof of quality. Prefer previews before expensive batches; do not overwrite unrelated files. Report unavailable downstream checks as unverified.

Editor screenshot readiness

Before capturing genuine editor evidence, verify Blender has an open, visible, non-minimized editor window; maximization is unnecessary. Minimized full-window and area captures have returned black on the tested workstation. If minimized, report the solution: restore Blender from the taskbar. Capture permission is already included in requested Blender work; this is a technical readiness issue. Inspect captured pixels and never label a failed capture, prior screenshot, or clean render as fresh editor evidence. Do not change the user's window state without authorization.

Before every Blender editor/window/area screenshot call, freshly check that the relevant Blender process has a visible, non-minimized editor window; do not reuse an earlier setup result. If Blender is closed, prompt the user to open it. If minimized or hidden, prompt the user to restore/show it (maximization is unnecessary). If inspection is unavailable, report the unknown state and ask the user to make the editor visible. Pause screenshot attempts until the issue is resolved, then repeat the window-state check before capturing. Do not automatically restore/focus the window. This prerequisite applies to editor screenshots, not saved render output. A passing check still requires inspection of the captured pixels; if the image is black or stale, report the failure and prompt the user to restore/show the editor before a fresh check and retry.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.