This is a routing skill that helps you pick the right testing approach for Umbraco backoffice extensions. It doesn't do the testing itself. Instead, it analyzes what you're trying to test and points you to one of four specialized skills: unit testing for isolated components, MSW testing for API mocking, mocked backoffice for UI integration without a backend, or E2E for full workflows. The decision guide is solid and the tree-example reference shows all four levels working together with 32 tests total. If you're building Umbraco extensions and tired of guessing which testing tool to reach for, this gives you a clear map of when to use what.
npx -y skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-testing --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
wshobson/agents
dbt-labs/dbt-agent-skills
github/awesome-copilot