Skills
dotCMS VTL Custom Field Migration
by dotCMS
Migrate dotCMS Velocity custom field templates from the legacy Dojo and Dijit API to DotCustomFieldApi.
Our verdict
We have not reviewed dotCMS VTL Custom Field Migration yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About dotCMS VTL Custom Field Migration
A skill maintained in the dotCMS core repository. It converts VTL custom field templates that use Dojo or Dijit patterns to the modern DotCustomFieldApi. By default it returns one inline file with the new code inside the new edit mode check and the original code untouched in the else branch, ready to paste into the content type editor. On request it splits the result into old, new and router files, or converts between the two shapes.
Best for
dotCMS developers moving custom fields to the new editor
Use cases
- Update a dotCMS custom field for the new edit mode
- Find what needs to change in a pasted VTL snippet
- Collapse a three-file migration into one inline file
Notes
Why it matters
Every dotCMS site with custom fields has to make this move to the new editor. The skill turns a fiddly manual rewrite into a repeatable step that keeps the old behaviour as a fallback.
Source
- Skill file: .claude/skills/dot-ui-vtl-migration/SKILL.md in dotCMS/core.
- Repository: 972 GitHub stars, a custom licence (check the repository). Checked 24 Oct 2026 through the GitHub API.
- Last change to the skill: 1 Oct 2026.
- This page was written from the skill's own SKILL.md. It is not an Enterprise DNA source review and the skill has not been installed or tested by us.
Pros
- Maintained by the dotCMS team
- Keeps the legacy code intact as a fallback
- Output is ready to paste
Cons
- Only relevant to dotCMS
- Licence is not declared in a standard form
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
Health and security
Is dotCMS VTL Custom Field Migration looked after, and what do its setup files show
Security check static checks
50 out of 100
- Critical certifi bundles emSign root CAs with compromised intermediate CA keys (affects certifi 2026.7.22, pinned in .claude/skills/dot-ui-vtl-migration/scripts/uv.lock).
- Medium pytest has vulnerable tmpdir handling (affects pytest 8.3.4, pinned in .claude/skills/dot-ui-vtl-migration/scripts/uv.lock).
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
Security finding
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.