umbraco-validation-checks
Audited by Runlayer on Feb 21, 2026
Malicious tool definition detected
Tool: SKILL.md Description: --- name: umbraco-validation-checks description: Browser validation checks for testing Umbraco backoffice extensions manually version: 1.0.0 location: managed allowed-tools: Read --- # Umbraco Extension Validation Checks Reference skill containing validation checks for manual browser testing of Umbraco backoffice extensions.
Malicious tool definition detected
Tool: api-debugging-checks.md Description: # API Debugging Checks ## VA-1: 400 Error Investigation **Common Symptom:** API calls failing, often silently or with generic errors **ALWAYS check for 400 (Bad Request) errors first.** These indicate the data sent to the server is wrong.
Malicious tool definition detected
Tool: configuration-checks.md Description: # Configuration Checks ## VC-1: Section Permissions **Common Symptom:** New section not visible in the backoffice sidebar When creating a new section, it won't appear unless the user's group has permission to access it.
Malicious tool definition detected
Tool: discovered-issues.md Description: # Discovered Issues Log Log new validation issues here as they are discovered.
Malicious tool definition detected
Tool: form-control-checks.md Description: # Form Control Checks ## VF-1: Select/Combobox Behavior **Common Symptom:** Dropdown not working, wrong value selected, or options not appearing > **Key insight:** Empty or broken selects are a common cause of mysterious 400 API errors. When debugging 400 errors, **always check selects first** - if a select has no data or wrong data, the form submits invalid values that the API rejects.
Malicious tool definition detected
Tool: navigation-checks.md Description: # Navigation Checks ## VN-1: Tree Complexity **Common Symptom:** Tree not rendering, items missing, or incorrect hierarchy Trees in Umbraco are complex multi-part systems.
Malicious tool definition detected
Tool: workspace-checks.md Description: # Workspace Checks ## VW-1: Missing Save Button **Common Symptom:** Custom workspace opens correctly, displays data, form fields work, but there is no Save button in the workspace footer. User cannot save changes.