use-external-asset-library
Discover approved read-only 3D models, rigs, animations, and bundles from optional external libraries configured in STYLE.md, then copy a selected asset into the repository before loading or modifying it. Use before creating, generating, or downloading a 3D asset when STYLE.md contains external asset libraries.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 4
- Forks
- 3
01 前言 Front Matter
- name
- use-external-asset-library
- engines
- [ "AGNOSTIC" ]
- description
- Discover approved read-only 3D models, rigs, animations, and bundles from optional external libraries configured in STYLE.md, then copy a selected asset into the repository before loading or modifying it. Use before creating, generating, or downloading a 3D asset when STYLE.md contains external asset libraries.
02 资源文件 1
- 参考文档agents/openai.yaml269 B
03 SKILL.md 正文
Use External Asset Library
When to use
Use for 3D model, rig, animation, Blender, WebGL, or game-asset work when STYLE.md contains an External Asset Libraries section.
Workflow
- Read and validate
STYLE.md. Do not ask about libraries during startup or setup when none are configured. - Run
./commands/list-external-asset-libraries.sh. When at least one library exists, inspect appropriate libraries before creating, generating, or downloading another model, rig, or animation. - Inventory candidates with
./commands/inspect-external-asset-library.sh LIBRARY_ID. Treat inventory as filenames and metadata only; do not load or import an external file to preview it. - Evaluate candidate fit, asset-level provenance, license, modification limits, selected art pipeline, architecture, format, rig, animation, and runtime budgets. A configured root is not proof of redistribution rights.
- Copy the selected file or complete bundle with
./commands/copy-external-asset.sh. Record task-local evidence when an active task exists. - Load, import, edit, execute, or use only the repository-local copy below
assets/models/<library-id>/. Verify it in the intended authoring tool or runtime before handoff.
Pipeline Fit
- With
BLENDER, use copied.blendfiles or bundles as working templates or approved reusable assets; never open the external source directly. - With
CODE, use a copied mesh only as authorized reference/template evidence. Do not turn model-library loading into the primary runtime implementation. - With
PROOF_TO_MODEL, preserve copy receipts and source ancestry, and validate rights, recipe, stage evidence, and budgets before using copied models. - With any other workflow, proceed only when the active pipeline and repository architecture explicitly permit the copied format and intended runtime use.
Output
- Selected library id and source-relative asset path.
- Repository-local destination below
assets/models/. - Copy receipt containing the active style hash and copied-file hashes when evidence is requested.
- Rights, compatibility, and use-as-is versus template decision.
Guardrails
- Treat every configured external library and every file beneath it as read-only.
- Never edit, rename, delete, generate into, install into, or otherwise write beneath a library root.
- Never load, import, execute, or use an external-library path directly. Copy first.
- Never follow symbolic links, escape the configured root, overwrite a project asset, or copy outside
assets/models/. - Never create or download a replacement before checking configured libraries, unless the task explains why no compatible authorized candidate exists.
Commands
./commands/list-external-asset-libraries.sh [--style STYLE.md] [--json]./commands/inspect-external-asset-library.sh LIBRARY_ID [--style STYLE.md] [--json]./commands/copy-external-asset.sh LIBRARY_ID RELATIVE_ASSET_PATH [--style STYLE.md] [--evidence .hephaera/.cache/tasks/<task>/FILE.json]
04 同仓库更多 Skills
verify-web3-game-lifecycle
Verify a game's selected Web3 asset, wallet, ownership and trading lifecycle with contract properties, canonical recovery, actual target evidence and separate release readiness.
verify-onchain-game-assets
Verify exact on-chain game collection ownership and quantities at canonical blocks, reconcile inventory events, and design honest match admission. Use for ERC721/ERC1155 inventory, reorg recovery, reservations, or transfer-during-match rules.
plan-web3-game-assets
Define an opt-in Ethereum, Base or Immutable game-asset lifecycle, including token identity, supply, rights, custody, game eligibility and chain-specific dependencies.
integrate-game-wallets
Integrate explicit player-wallet connection, scoped SIWE authentication, authority invalidation and reviewed target-specific handoff without application-held player keys.
integrate-game-asset-trading
Integrate explicitly selected game asset settlement with exact unsigned intents, scoped approvals, idempotent operations and canonical receipt reconciliation. Use for NFT listing, buying, cancellation, retries or marketplace integration.
build-evm-game-contracts
Author and verify host-owned EVM game collections and explicit mint, burn, craft or admin rules with pinned Solidity tooling. Use for contract source and deployment candidates; deployment and player signing require separate authorization.