agentleFS
Sign inStart free
FreedomIntelligenceFreedomIntelligence/BlenderLore/skills/blender-pipeline/reproduction/SKILL.md

blender-pipeline-reproduction

Skill97 starsChanged 2 months agoApache-2.0View on GitHub

Reproduce a maintained Blender showcase recipe from authorized video, tutorial, image, or local asset inputs while enforcing visual-acceptance and asset-distribution gates.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

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

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

    Use scripts/reproduce.sh to select one exact recipe.

    line 8
  2. Very specific:

    Add --render-tutorial-html only when a human-facing display copy is useful.

    line 34
  3. Very specific:

    Follow the selected recipe's distribution_contract.asset_delivery exactly:

    line 40
  4. Distinctive:

    Read references/execution-contract.md when adding a recipe or diagnosing a validation failure.

    line 49

≈ “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

Blender Showcase Reproduction

Use scripts/reproduce.sh to select one exact recipe. The command is a dry run unless the user explicitly authorizes --execute.

The packaged public catalog is metadata-only. It records the current public showcase identity, input bindings, dynamic acceptance contracts, known gaps, and distribution policy; it contains no source assets or tutorial media. A public preview URL is acceptance evidence, not permission to download or reuse the asset. A recipe that is disabled, blocked, incomplete, or not independently accepted must fail before download, model invocation, or Blender execution.

Tutorial inputs

  • For an authorized existing tutorial, use --tutorial-mode provided and one or more --tutorial files. The operational truth is tutorial.md plus steps_verified.json.
  • To extract an operational tutorial from video, explicitly use --tutorial-mode extract, --video-url, at least one --image, and a positive --tutorial-window-budget. Extraction delegates to the sibling tutorial extraction skill, defaults to the balanced profile and gpt-5.6-sol. The supplied video-to-visual-tutorial skill produces a complete procedure; a compatibility adapter supplies the existing replay files. gpt-5.5 is an explicit whole-run fallback only and requires --tutorial-fallback-reason.
  • Paid extraction requires BLENDER_PIPELINE_API_ENDPOINT and an owner-only secret file named by BLENDER_PIPELINE_API_KEY_FILE. Dry runs do not read credentials, download media, call a model, or write a run directory.
  • Add --render-tutorial-html only when a human-facing display copy is useful. It is rendered from the same complete Markdown without a second model call and never replaces tutorial.md.

Asset delivery

Follow the selected recipe's distribution_contract.asset_delivery exactly:

  • bundled-open: allowed only with package-local source, exact hash, SPDX identifier, and package-local license evidence.
  • user-supplied: require a lawful local --asset; never fetch, publish, or commit it or the isolated staged copy.
  • blocked: stop. An adapter, public URL, or matching-looking asset does not unlock the recipe.

Read references/execution-contract.md when adding a recipe or diagnosing a validation failure.

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