Automated summary
This skill explains how to use the Umbraco backoffice extension registry to register, exclude, unregister, or replace UI elements.
Strengths
- Covers core registry operations: register, exclude, unregister, replace
- Provides practical, reusable TypeScript code examples
- Emphasizes fetching the latest official docs via WebFetch
- Includes both single and multiple replacement scenarios
Limitations
- Specific to Umbraco CMS, not directly applicable to other platforms
- Requires familiarity with TypeScript and Umbraco backoffice architecture
- Examples are minimal and do not cover conditions or advanced use cases
Use this skill when you need to customize or extend the Umbraco backoffice interface through the extension registry.
Do not use it for other CMSs or frameworks, or for simple theme changes unrelated to the extension registry.
Security analysis
SafeThe skill describes client-side UI extension management for Umbraco, with no destructive commands, system modifications, or data exfiltration. All operations are within the browser environment and do not pose security risks.
No concerns found
How this analysis is madeExamples
I want to add a custom dashboard to the Umbraco backoffice. Show me how to register it using the extension registry.Replace the default 'Save and Preview' workspace action for documents with my own custom action in Umbraco.How do I remove the Umbraco News dashboard from the backoffice using umbExtensionsRegistry.exclude?name: umbraco-extension-registry description: Understand and use extension registry in Umbraco backoffice (foundational concept) version: 1.0.0 location: managed allowed-tools: Read, Write, Edit, WebFetch
Umbraco Extension Registry
What is it?
The Extension Registry is the core system managing all Umbraco backoffice UI elements - almost any UI in the Backoffice is an extension managed by the Extension Registry. The registry allows developers to dynamically add, remove, or modify extensions at runtime using umbExtensionsRegistry. Developers have the same possibilities as Umbraco HQ, meaning you can change almost everything that is by default present in Umbraco.
Documentation
Always fetch the latest docs before implementing:
- Main docs: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry
- Register Extensions: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry/register-extensions
- Replace/Exclude: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry/replace-exclude-or-unregister
- Extension Manifest: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest
- Foundation: https://docs.umbraco.com/umbraco-cms/customizing/foundation
Workflow
- Fetch docs - Use WebFetch on the URLs above
- Ask questions - Register, exclude, or replace? Runtime or static? Conditions needed?
- Generate code - Implement registry operations based on latest docs
- Explain - Show what was created and how extensions are managed
Minimal Examples
Register Extension (Runtime)
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
const manifest = {
type: 'dashboard',
alias: 'My.Dashboard',
name: 'My Dashboard',
element: () => import('./dashboard.element.js'),
meta: {
label: 'My Dashboard',
pathname: 'my-dashboard'
}
};
umbExtensionsRegistry.register(manifest);
Exclude Extension
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
// Permanently hide an extension
umbExtensionsRegistry.exclude('Umb.WorkspaceAction.Document.SaveAndPreview');
Unregister Extension
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
// Remove extension from registry (can be re-registered)
umbExtensionsRegistry.unregister('My.WorkspaceAction.AutoFillWithUnicorns');
Replace Extension (Overwrites)
const manifest = {
type: 'workspaceAction',
alias: 'My.WorkspaceAction.ExternalPreview',
name: 'My Custom Preview',
overwrites: 'Umb.WorkspaceAction.Document.SaveAndPreview',
element: () => import('./custom-preview.element.js'),
// ... rest of manifest
};
umbExtensionsRegistry.register(manifest);
Replace Multiple Extensions
const manifest = {
type: 'workspaceAction',
alias: 'My.CustomSave',
name: 'My Custom Save',
overwrites: [
'Umb.WorkspaceAction.Document.SaveAndPreview',
'Umb.WorkspaceAction.Document.Save'
],
// ... rest of manifest
};
umbExtensionsRegistry.register(manifest);
Entry Point Registration
// entrypoint.ts
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
export const onInit = (host: UmbEntryPointOnInitArgs) => {
// Exclude default dashboard
umbExtensionsRegistry.exclude('Umb.Dashboard.UmbracoNews');
// Register custom dashboard
umbExtensionsRegistry.register({
type: 'dashboard',
alias: 'My.CustomDashboard',
name: 'Custom Dashboard',
element: () => import('./custom-dashboard.element.js'),
meta: {
label: 'Welcome',
pathname: 'welcome'
},
conditions: [
{
alias: 'Umb.Condition.SectionAlias',
match: 'Umb.Section.Content'
}
]
});
};
Dynamic Registration from Server Data
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
async function registerDynamicDashboards() {
// Fetch configuration from server
const response = await fetch('/api/dashboard-config');
const dashboards = await response.json();
// Register each dashboard dynamically
dashboards.forEach(config => {
umbExtensionsRegistry.register({
type: 'dashboard',
alias: config.alias,
name: config.name,
element: () => import(config.elementPath),
meta: {
label: config.label,
pathname: config.pathname
}
});
});
}
Conditional Registration
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
// Register extension only if condition is met
if (userIsAdmin) {
umbExtensionsRegistry.register({
type: 'dashboard',
alias: 'My.AdminDashboard',
name: 'Admin Dashboard',
element: () => import('./admin-dashboard.element.js'),
meta: {
label: 'Admin',
pathname: 'admin'
}
});
}
Batch Operations
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
// Exclude multiple extensions
const extensionsToHide = [
'Umb.Dashboard.UmbracoNews',
'Umb.Dashboard.RedirectManagement',
];
extensionsToHide.forEach(alias => {
umbExtensionsRegistry.exclude(alias);
});
// Register multiple extensions
const myExtensions = [
{ type: 'dashboard', alias: 'My.Dashboard1', /* ... */ },
{ type: 'dashboard', alias: 'My.Dashboard2', /* ... */ },
];
myExtensions.forEach(manifest => {
umbExtensionsRegistry.register(manifest);
});
View Registered Extensions
Navigate to: Settings > Extensions Insights in the backoffice to see all registered extensions.
Key Concepts
umbExtensionsRegistry: Central registry for managing extensions
register(): Add new extension at runtime
exclude(): Permanently hide extension (never displayed)
unregister(): Remove extension from registry (can be re-registered)
overwrites: Replace existing extension(s) with custom implementation
Runtime vs Static:
- Static: Use
umbraco-package.jsonfor most extensions - Runtime: Use
umbExtensionsRegistryfor dynamic/conditional registration
Entry Point: Common place to execute registry operations during startup
Extension Insights: View all registered extensions at Settings > Extensions Insights
Use Cases:
- Hide default Umbraco features
- Register extensions based on server data
- Replace built-in actions with custom logic
- Conditionally enable features
- Dynamic dashboard registration
Sources
- Extension Registry | Umbraco CMS
- Register an Extension | Umbraco CMS
- Replace, Exclude or Unregister | Umbraco CMS
That's it! Always fetch fresh docs, keep examples minimal, generate complete working code.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/umbraco-extension-registry-msh3ut48' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/umbraco-extension-registry-msh3ut48/download' --output '.skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md.part' && mv '.skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md.part' '.skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, WebFetch
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md' && test -s '.skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/umbraco-extension-registry' && cp -R '.skill-downloads/umbraco-extension-registry-msh3ut48' '.claude/skills/umbraco-extension-registry'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/umbraco-extension-registry-msh3ut48'openskills read 'umbraco-extension-registry-msh3ut48'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/umbraco-extension-registry-msh3ut48/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.