umbraco-extension-registry

Register, exclude, unregister, or replace Umbraco backoffice extensions via umbExtensionsRegistry APIs.

4|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-extension-registry-albanistrefi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-extension-registry
Source: https://github.com/albanistrefi/umbraco_CLI/tree/main/skills/foundation/umbraco-extension-registry
Command: npx skills add https://github.com/albanistrefi/umbraco_CLI --skill umbraco-extension-registry-albanistrefi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand and safely change Umbraco backoffice UI behavior by managing extensions through the Extension Registry instead of relying on static configuration.

Core Features & Use Cases

  • Runtime extension registration: Dynamically add dashboards, workspace actions, and other backoffice UI elements using umbExtensionsRegistry.register with a manifest.
  • Exclude, unregister, and replace: Hide extensions (exclude), remove them for later re-registration (unregister), or overwrite existing ones (overwrites) to customize default behavior.
  • Conditional and entry-point workflows: Apply rules at startup to register or exclude extensions based on conditions, such as section or user context.

Quick Start

Ask an AI to produce the exact umbExtensionsRegistry code to exclude a given extension alias and register a new dashboard manifest that appears only for a specific section alias.

Frequently Asked Questions about umbraco-extension-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register Umbraco backoffice extensions at runtime instead of using static manifests?

Runtime Umbraco extension registration uses the umbExtensionsRegistry.register API with a manifest to dynamically add dashboards, workspace actions, and UI elements without relying on static package configuration.

Can I replace or hide existing Umbraco dashboards conditionally based on user context?

Yes, you can conditionally hide or replace Umbraco dashboards using extension registry overwrites and exclude rules based on section or user context applied at startup.

What is the difference between excluding and unregistering an Umbraco backoffice extension?

Excluding an Umbraco extension hides it from the backoffice, while unregistering removes it entirely to allow later re-registration with a new manifest.

How do I overwrite default Umbraco workspace actions using the extension registry?

Overwriting Umbraco workspace actions requires using the umbExtensionsRegistry API with an updated manifest containing the correct type, alias, name, element, and meta fields to replace default behavior.

When should I use runtime extension registration instead of static package-based extensions in Umbraco?

Runtime extension registration is necessary when you need conditional or dynamic customization of Umbraco backoffice UI behavior that static package-based extensions cannot provide.

What manifest fields are required to register a new Umbraco backoffice dashboard dynamically?

Registering an Umbraco dashboard dynamically requires a manifest with type, alias, name, element, and meta fields, plus optional conditions and overwrites aligned with official Umbraco documentation.