agentleFS
Sign inStart free
full-aigc-pluginsfull-aigc-plugins/blender-design-plugin/skills/blender-managed/SKILL.md

blender-managed

Skill4 starsChanged 21 days agoApache-2.0View on GitHub

Start a non-invasive Blender design session from Codex without installing a Blender Add-on. Use for new projects or when the user wants Codex to launch Blender.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --execution-mode review_only for a read-only session.

    line 12
  2. Very specific:

    Wait for the private 0600 session descriptor, then communicate through harness_cli.py.

    line 17
  3. Very specific:

    Keep Blender alive until the user closes it or authorizes session.close.

    line 18
  4. Very specific:

    Verify session.status reports the requested mode.

    line 21
  5. Distinctive:

    If no foreground viewport exists, report that specific condition.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Managed Blender Session

Use python3 scripts/launch_harness.py --session-id <unique-id> --output-root <approved-root>. For an authorized automatic task add --execution-mode auto_with_budget and repeated --export-format blend --export-format mp4 for its requested formats; add --allow-designed-proxies only when the user permitted original substitute assets. Use --execution-mode review_only for a read-only session. Omission remains interactive. The launcher starts scripts/managed_bootstrap.py in foreground mode with --disable-autoexec. Do not change Blender preferences. A project path must be an authorized regular .blend; omit it for a new design.

Wait for the private 0600 session descriptor, then communicate through harness_cli.py. Keep Blender alive until the user closes it or authorizes session.close. Never fall back to unreviewed arbitrary Python when the Harness fails to start.

Verify session.status reports the requested mode. The temporary Codex Live Session panel and viewport header expose progress and takeover controls. Use view.set, view.focus, playback.set_frame and playback.set rather than an expert script for UI review. If no foreground viewport exists, report that specific condition; do not claim the user can see operations. Read command reference.

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.

Check your setup, free