| name | linked-libraries |
| description | Use when a Blender task involves linked libraries, append, link, library override, assets. Part of the Blender reference router; covers linking and appending data, library overrides, and reusing assets across .blend files. |
Blender Linked Libraries and Append/Link Reference
Faithful, original-prose reference for linking and appending data, library overrides, and reusing assets across .blend files. Identifiers (operator names, bpy paths, enum
values, shortcuts, numbers) are preserved verbatim. One subject per file across 76 reference files.
When to use this
Use this sub-skill when the task involves linked libraries, append, link, library override, assets. It applies even when "Blender" is not named but
a .blend file, bpy, or a relevant operator/shortcut is in play.
Workflow
- Open
references/INDEX.md (or references/topics.json) and pick the one file that matches — the INDEX "Covers" column lists the subjects in each file.
- Read only that file; open another only if the task spans subjects. Grep across files when a subject may be split:
rg -n "PATTERN" references/*.md.
- Treat every operator name,
bpy path, enum value, shortcut, and number as an exact reference fact — never invent or paraphrase identifiers.
Gotchas
Recurring failure modes and what to do instead live in the sibling GOTCHA.md.
References
All depth lives in references/ — start at references/INDEX.md, with metadata in
references/topics.json. One subject per file.
Verification
python "$env:DEVROOT\SKILLS\skills\skill-drafting\scripts\validate_skill_package.py" "$env:DEVROOT\SKILLS\skills\blender\linked-libraries"
