Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
umbraco avatar

Umbraco Backoffice

  • 335 installs
  • 26 repo stars
  • Updated August 1, 2026
  • umbraco/umbraco-cms-backoffice-skills

umbraco-backoffice is an Umbraco CMS agent skill that routes backoffice extension development across 57 extension types with working blueprints and sub-skill references for developers who customize the Umbraco backoffice

About

umbraco-backoffice is the backbone skill in the umbraco/Umbraco-CMS-Backoffice-Skills collection, which ships 58 backoffice extension skills and over 66 skills total across the repository. The skill provides a complete extension map showing where all 57 extension types appear in the Umbraco backoffice UI, working blueprints developers can copy and adapt, and categorized links to specialized sub-skills. Developers reach for umbraco-backoffice when starting a new backoffice customization, understanding how sections, menus, dashboards, workspaces, and trees connect, or selecting the right skill for a specific UI location. Runnable examples include Blueprint 1 combining six skills, TimeDashboard wiring 13 extension types, tree-example using seven skills, and notes-wiki spanning 27 skills with a C# backend.

  • umbraco-backoffice
  • AI & Agent Building
  • AI-coding skill

Umbraco Backoffice by the numbers

  • 335 all-time installs (skills.sh)
  • +13 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #2,184 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/umbraco/umbraco-cms-backoffice-skills --skill umbraco-backoffice

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs335
repo stars26
Last updatedAugust 1, 2026
Repositoryumbraco/umbraco-cms-backoffice-skills

How do you structure Umbraco backoffice extension types correctly?

Helps with ai & agent building tasks.

Who is it for?

Developers customizing Umbraco CMS backoffice UI who need the extension map, tested blueprints, and sub-skill routing across dozens of extension types.

Skip if: Skip umbraco-backoffice when building a non-Umbraco CMS admin UI or a public marketing site without backoffice extension work.

When should I use this skill?

Trigger umbraco-backoffice when the user starts Umbraco backoffice customization, asks where an extension type belongs, or needs blueprint examples for dashboards or workspaces.

What you get

Extension map selections, blueprint-based Umbraco backoffice extensions, and sub-skill routing for dashboards, trees, workspaces, and C# APIs.

  • extension architecture map
  • blueprint-based extension code
  • sub-skill routing plan

By the numbers

  • Maps 57 Umbraco backoffice extension types in the extension map
  • Repository ships 58 backoffice extension skills with runnable blueprints

Files

examples/Blueprint/Blueprint.csprojTextGitHub ↗
<Project Sdk="Microsoft.NET.Sdk.Razor">
  <PropertyGroup>
    <TargetFramework>net10.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <StaticWebAssetBasePath>/</StaticWebAssetBasePath>
  </PropertyGroup>

  <PropertyGroup>
    <PackageId>MyExtension</PackageId>
    <Product>MyExtension</Product>
    <Title>MyExtension</Title>
  </PropertyGroup>


  <ItemGroup>
    <PackageReference Include="Umbraco.Cms.Web.Website" Version="17.*" />
    <PackageReference Include="Umbraco.Cms.Web.Common" Version="17.*" />
    <PackageReference Include="Umbraco.Cms.Api.Common" Version="17.*" />
    <PackageReference Include="Umbraco.Cms.Api.Management" Version="17.*" />
  </ItemGroup>

  <ItemGroup>
    <ClientAssetsInputs Include="Client\**" Exclude="$(DefaultItemExcludes)" />

    <!-- Dont include the client folder as part of packaging nuget build -->
    <Content Remove="Client\**" />

    <!-- However make the Umbraco-package.json included for dotnet pack or nuget package and visible to the solution -->
    <None Include="Client\public\umbraco-package.json" Pack="false" />
  </ItemGroup>

  <ItemGroup>
    <Folder Include="wwwroot\" />
  </ItemGroup>

  <!-- Restore and build Client files -->
  <Target Name="RestoreClient" Inputs="Client\package.json;Client\package-lock.json" Outputs="Client\node_modules\.package-lock.json">
    <Message Importance="high" Text="Restoring Client NPM packages..." />
    <Exec Command="npm i" WorkingDirectory="Client" />
  </Target>

  <Target Name="BuildClient" BeforeTargets="AssignTargetPaths" DependsOnTargets="RestoreClient" Inputs="@(ClientAssetsInputs)" Outputs="$(IntermediateOutputPath)client.complete.txt">
    <Message Importance="high" Text="Executing Client NPM build script..." />
    <Exec Command="npm run build" WorkingDirectory="Client" />
    <ItemGroup>
      <_ClientAssetsBuildOutput Include="wwwroot\App_Plugins\**" />
    </ItemGroup>
    <WriteLinesToFile File="$(IntermediateOutputPath)client.complete.txt" Lines="@(_ClientAssetsBuildOutput)" Overwrite="true" />
  </Target>

</Project>

Related skills

How it compares

Choose umbraco-backoffice over individual sub-skills first when you need the full extension map and blueprint routing before implementing a specific UI location.

FAQ

What does the umbraco-backoffice skill provide?

umbraco-backoffice is the backbone routing skill with a complete map of 57 extension types, working blueprints, and links to specialized Umbraco backoffice sub-skills by UI location.

How many Umbraco backoffice skills ship in the collection?

The Umbraco-CMS-Backoffice-Skills repository includes 58 backoffice extension skills plus additional testing skills, with umbraco-backoffice routing across the full extension map.

When should developers invoke umbraco-backoffice first?

Developers should invoke umbraco-backoffice when starting a new backoffice customization, understanding how extension types connect, or finding the correct sub-skill for a dashboard, tree, or workspace.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.