bl-info-migration SKILL.md skillB
bl-info-migration from tmhsdigital/blender-developer-tools is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tmhsdigital/blender-developer-tools/bl-info-migration@git:20261012.96b6076Pins git:20261012.96b6076 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tmhsdigital/blender-developer-tools
- Path
skills/bl-info-migration/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261012.96b6076, committed Oct 12, 2026
- First version recorded
- Apr 26, 2026
- Size
- 11,278 bytes
- Repository stars
- 17
- License
- a license file GitHub does not identify
Migrate a legacy bl_info add-on to the Extensions Platform in three steps, with a before/after diff and the dual-format pattern. Use when the user has a bl_info dictionary in __init__.py, asks whether bl_info is deprecated or still supported, wants to publish to extensions.blender.org or ship an extension .zip, or sees warnings about legacy add-ons at install time. Targets 5.2 LTS; manifests work from 4.2.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# bl_info Migration to the Extensions Platform
## Trigger
Use this skill when the user:
- Has an existing add-on with a `bl_info = {...}` dictionary at the top of `__init__.py`
- Wants to publish to extensions.blender.org or distribute as a `.zip` for the Extensions Platform
- Asks "is bl_info dead?" or "do I have to migrate?"
- Sees a deprecation warning at install time about legacy add-ons
- Mentions `blender_manifest.toml`, "Install legacy Add-on", or "the new extension system"
## Is bl_info still supported?
Yes, with caveats.
- **In 5.2 LTS (current stable; 5.1 is prior stable)**: `bl_info` is supported as a fallback for legacy add-ons. The Edit > Preferences > Add-ons panel still has "Install legacy Add-on" and recognizes `bl_info` dicts.
- **For the Extensions Platform** (extensions.blender.org and the new add-ons UI): you need a `blender_manifest.toml`. `bl_info` is ignored.
- **Dual format** is officially recognized: ship a `blender_manifest.toml` and keep the `bl_info` dict. The platform reads the manifest; legacy installers read `bl_info`. Both code paths work without conditional logic.
…Read the whole file at its exact version.
How to install
mdr add tmhsdigital/blender-developer-tools/bl-info-migration@sha256:2f38a832f7233f13The line at the top of this page pins the label git:20261012.96b6076, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_54c2fjdxuyaxd3mk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Apr 26, 2026 and Oct 12, 2026, about one every 19 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.96b6076 latest | 2026-10-12 | 96b6076 | 11,278 B | B | view · diff |
| git:20261007.4636c25 | 2026-10-07 | 4636c25 | 10,980 B | A | view · diff |
| git:20261005.f80411b | 2026-10-05 | f80411b | 9,112 B | A | view · diff |
| git:20261005.5e0299c | 2026-10-05 | 5e0299c | 8,826 B | A | view · diff |
| git:20261005.040e994 | 2026-10-05 | 040e994 | 8,644 B | A | view · diff |
| git:20261004.0583b45 | 2026-10-04 | 0583b45 | 8,649 B | A | view · diff |
| git:20261003.fefd033 | 2026-10-03 | fefd033 | 8,570 B | A | view · diff |
| git:20260909.e5b1642 | 2026-09-09 | e5b1642 | 8,496 B | A | view · diff |
| git:20260613.e6324e5 | 2026-06-13 | e6324e5 | 8,492 B | A | view · diff |
| git:20260426.5a05f16 | 2026-04-26 | 5a05f16 | 8,491 B | A | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11278 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
tmhsdigital/blender-developer-tools · 17 stars · license a license file GitHub does not identify · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_54c2fjdxuyaxd3mk GET https://markdownregistry.com/api/v1/resolve?ref=tmhsdigital/blender-developer-tools/bl-info-migration GET https://markdownregistry.com/api/v1/blob/2f38a832f7233f1361082d670c203ff2d9885e28044c2750fe121dc6ea36b670
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.