home / skills / nikiskaarup / skills / umbraco-mcp-dev-ops

umbraco-mcp-dev-ops skill

/umbraco-mcp-dev-ops

This skill guides Claude to perform Umbraco developer and ops tasks safely using MCP tool collections to automate setup, health checks, and diagnostics.

npx playbooks add skill nikiskaarup/skills --skill umbraco-mcp-dev-ops

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
2.0 KB
---
name: umbraco-mcp-dev-ops
description: Guide Claude to perform Umbraco developer and ops tasks via MCP tools safely.
---

# Umbraco MCP Dev Ops

## Purpose
Guide Claude to perform Umbraco developer and operational tasks efficiently and safely using the MCP tool collections.

## Scope
- Included: document/data type management, templates and partials, scripts/stylesheets, models builder, health/logs, indexing/search, server diagnostics.
- Excluded by default: content authoring and bulk publishing workflows.

## When to Use
- Automating schema changes, developer assets, or operational diagnostics.
- Running health checks, log analysis, or index maintenance.

## When Not to Use
- Content creation or editorial operations.
- Media uploads or localization tasks.

## Tool Collection Strategy
- Always request the smallest set of tool collections needed for the task.
- See `references/tool-collections.md` for task-to-collection mapping.

## Execution Policy
- Read before write: fetch configuration or scaffolds first.
- Validate before mutate: use validation endpoints when available.
- Prefer search and by-id-array endpoints to reduce calls.
- Paginate large lists and batch changes with clear progress.

## Safety Rules
- Require confirmation for destructive actions (delete, remove folders).
- Require confirmation for broad schema changes affecting many types.
- If permissions are unclear, fetch current user permissions and report limits.

## Response Format
- Summarize actions taken and list affected assets.
- For read-only tasks, return concise findings with counts and key examples.
- Include next steps only when useful (e.g., rebuild models, run checks).

## Examples
- Create a new Document Type with required properties.
- Update a Data Type configuration across the project.
- Rebuild the external search index and report status.
- Run all health checks and summarize warnings.
- Generate Models Builder outputs after schema changes.
- Create a stylesheet or partial view scaffold.

Overview

This skill guides Claude to perform Umbraco developer and operational tasks using the MCP tool collections safely and efficiently. It focuses on schema and asset management, diagnostics, indexing, and maintenance while avoiding editorial content workflows. The skill enforces safety checks and clear execution rules for read and write operations.

How this skill works

The skill inspects Umbraco configuration, document types, data types, templates, stylesheets, models builder outputs, health checks, logs, and search/index state using targeted MCP tool collections. For write operations it fetches scaffolds and current configs first, validates changes via available endpoints, and requests explicit confirmation before destructive or broad-impact actions. It summarizes results, lists affected assets, and suggests next steps when useful.

When to use it

  • Automating schema or data-type updates across environments
  • Rebuilding or inspecting external search indexes and reporting status
  • Running full health checks, log analysis, or server diagnostics
  • Creating or scaffolding developer assets (stylesheets, partial views, models) safely
  • Batch-updating configurations or rebuilding Models Builder outputs

Best practices

  • Request only the minimal tool collections needed for the task to limit scope and permissions
  • Always read current configuration and asset scaffolds before making changes
  • Use validation endpoints and search/by-id-array calls to minimize API calls
  • Paginate large lists and batch changes with progress reports and rollback checkpoints
  • Require explicit user confirmation for deletions or wide-impact schema changes
  • Fetch and report current user permissions if access is unclear

Example use cases

  • Create a new Document Type with required properties and return the new type id and affected files
  • Update a Data Type configuration across multiple document types and list modified assets
  • Run all health checks, summarize warnings, and provide prioritized remediation steps
  • Rebuild an external search index, report progress and final item counts
  • Generate Models Builder outputs after schema changes and identify next deploy steps

FAQ

Will this skill perform editorial content edits?

No. Content authoring and bulk publishing are excluded by default; focus is on developer and ops tasks only.

What safety checks run before destructive actions?

The skill fetches current config, lists affected assets, validates intent, and requires explicit confirmation for deletes or broad-impact schema changes.