umbraco-validation-checks

Run browser-based validation checks for Umbraco backoffice extensions.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-validation-checks-kraftvaerk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umbraco-validation-checks
Source: https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy/tree/main/Kraftvaerk.Umbraco.Alchemy.Frontend/.agents/skills/umbraco-validation-checks
Command: npx skills add https://github.com/kraftvaerk/Kraftvaerk.Umbraco.Alchemy --skill umbraco-validation-checks-kraftvaerk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to debugging common issues encountered when developing and testing Umbraco backoffice extensions, saving developers significant time and frustration.

Core Features & Use Cases

  • Systematic Debugging: Offers categorized checks for configuration, navigation, API interactions, form controls, and workspace behavior.
  • Symptom-Based Guidance: Helps pinpoint the root cause of issues based on observed symptoms.
  • Use Case: When a new Umbraco section fails to appear, this Skill guides you through checking section permissions and manifest registration, quickly resolving the visibility issue.

Quick Start

Load this skill before beginning manual browser validation of your Umbraco extension.

Frequently Asked Questions about umbraco-validation-checks

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

FAQPage Schema
How do I debug an Umbraco backoffice extension that is not working properly?

To debug an Umbraco backoffice extension, use systematic browser-based validation checks covering configuration, navigation, API interactions, form controls, and workspace behavior to isolate and resolve the issue.

Why does my new Umbraco section fail to appear in the backoffice navigation?

A new Umbraco section may fail to appear due to incorrect section permissions or manifest registration errors. Symptom-based troubleshooting helps pinpoint these configuration issues by analyzing observed navigation behavior.

What is the best way to systematically test Umbraco backoffice extensions manually?

The best way to manually test Umbraco backoffice extensions is following categorized validation checks that guide you through configuration, API debugging, and form controls step by step to ensure comprehensive coverage.

How do I troubleshoot API interactions failing inside my Umbraco extension?

Troubleshoot failing Umbraco extension API interactions by running targeted browser validation checks that examine API requests, responses, and workspace behavior to identify the root cause of the failure.

Can I use these validation checks for any Umbraco backoffice extension?

Yes, these validation checks apply broadly to Umbraco backoffice extension development. They provide categorized debugging steps for common issues across configuration, navigation, form controls, and workspace behavior.

What should I check when Umbraco backoffice form controls behave unexpectedly?

When Umbraco backoffice form controls behave unexpectedly, check form control configurations and workspace interactions using systematic troubleshooting steps designed to analyze common symptoms and identify root causes.