umbraco-collection

Implement Umbraco backoffice Collection extensions with manifests, repositories, and views.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building a custom Umbraco backoffice collection from scratch is complex because it requires wiring together manifests, repository/data access, context state, views, and actions in the correct extension architecture.

Core Features & Use Cases

  • Collection architecture guidance: Breaks down the required parts (collection, repository, data source, context, views, and actions) so you can implement a complete collection end-to-end.
  • Official-doc driven implementation: Uses the latest Umbraco documentation links as the reference baseline to reduce outdated patterns and integration mistakes.
  • Reusable patterns and scaffolding: Provides TypeScript-level example structures for types, repository manifests, context, table view rendering, and condition targeting.

Quick Start

Fetch the latest Umbraco collection docs, then implement a full collection by creating the collection manifest, repository + data source, context, a table view, and a refresh action using the provided aliases and extension patterns.

Frequently Asked Questions about umbraco-collection

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

FAQPage Schema
How do I create a custom Umbraco backoffice collection with TypeScript?

To create an Umbraco backoffice collection, you define the extension manifests, repository layer, collection context, table views, and actions using TypeScript patterns for data fetching and rendering.

What components are required to build an Umbraco collection extension?

Building an Umbraco collection requires a collection manifest, repository with data source, collection context, table view, and collection actions, all wired together using correct extension aliases and conditions.

How do I implement searchable and pageable entity lists in the Umbraco backoffice?

You implement searchable, filterable, pageable entity lists by configuring the Umbraco collection context and repository data fetching, then rendering the results through a custom table view with selection and bulk actions.

Do I need to follow the official Umbraco collections documentation when building extensions?

Yes, following the official Umbraco collections documentation is required to avoid outdated patterns, ensure correct extension manifest architecture, and properly configure repository manifests and condition targeting.

What is the repository pattern used for in Umbraco backoffice collections?

The repository pattern in Umbraco backoffice collections handles data fetching for the collection data source, providing working TypeScript structures to retrieve entities before rendering them in the table view.

Can I add bulk and refresh interactions to an Umbraco collection view?

Yes, you can add bulk and refresh interactions to Umbraco collections by defining collection actions and wiring them to the collection context, enabling entity selection and data updates within the backoffice UI.