umbraco-menu

Create Umbraco backoffice menu manifests with aliases and placement rules.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-menu-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-menu
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/umbraco-menu
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill umbraco-menu-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement Umbraco backoffice menus correctly by guiding you to the official extension and menu-item documentation and translating it into a working manifest setup.

Core Features & Use Cases

  • Menu container creation: Define a custom menu (type: menu) that can host related navigation or actions.
  • Menu item extension: Add link-style menu items (type: menuItem, kind: link) that appear in one or more menus.
  • Extend existing menus: Register items into built-in Umbraco menus (for example, the Help menu) with proper aliases and metadata.
  • Use case: You need a “My Menu” section for internal navigation and a “My Menu Item” that links to your documentation page, displayed in the correct backoffice area.

Quick Start

Ask the agent to implement a new custom menu alias “My.Menu” and one link menu item that appears in “My.Menu” and points to your target URL.

Frequently Asked Questions about umbraco-menu

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

FAQPage Schema
How do I add a custom menu to the Umbraco backoffice?

You create a custom Umbraco backoffice menu by registering a menu container using a TypeScript manifest with correct aliases and metadata. This generates a new navigation grouping to host related link items within the CMS interface.

How do I add a link item to an existing Umbraco backoffice menu?

You add link items to existing Umbraco backoffice menus by registering a menuItem extension of kind link in your manifest. This specifies the target menu alias, metadata, and destination URL for proper placement in the navigation.

What is the difference between menu and menuItem types in the Umbraco extension registry?

In the Umbraco extension registry, a menu type defines a container that hosts navigation groupings, while a menuItem type defines individual link entries placed inside those containers. Both require distinct manifest configurations with proper aliases and metadata.

Do I need TypeScript to create Umbraco backoffice menu extensions?

Yes, TypeScript is required to implement Umbraco backoffice menu extensions. You must generate TypeScript manifest files for both menu and menuItem types to register extensions correctly within the extension registry.

Can I extend the built-in Help menu in Umbraco with custom links?

You can extend the built-in Umbraco Help menu by registering a menuItem extension with the correct alias. This adds custom link items to the existing backoffice menu using proper metadata and placement rules.

How do I test registered menu rendering in the Umbraco backoffice?

To test registered menu rendering in Umbraco, you deploy your TypeScript manifest files and verify the backoffice UI displays the custom menu containers and link items. The Skill explains how to validate rendering against the official documentation requirements.