Skip to content
TrustedSkillsbeta
Back to all skills

Umbraco Unit Testing

Listed
umbraco·vlatest·testing

Automates Umbraco unit tests, ensuring code quality and preventing regressions within your CMS implementation.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add umbraco/umbraco-cms-backoffice-skills --skill umbraco-unit-testing -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

umbraco

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 6 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: dotenvx.com, feross.org, opencollective.com, paulmillr.com, paypal.me….

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    github.comsource hostwww.patreon.comundeclaredfeross.orgundeclaredpaulmillr.comundeclareddotenvx.comundeclaredopencollective.comundeclaredpaypal.meundeclared

    What it found (3 of 20)

    • plugins/umbraco-testing-skills/skills/umbraco-unit-testing/examples/counter-dashboard/package-lock.json:2805contacts www.patreon.com
      "url": "https://www.patreon.com/feross"
    • plugins/umbraco-testing-skills/skills/umbraco-unit-testing/examples/counter-dashboard/package-lock.json:2849contacts www.patreon.com
      "url": "https://www.patreon.com/feross"
    • plugins/umbraco-testing-skills/skills/umbraco-unit-testing/examples/counter-dashboard/package-lock.json:4400contacts www.patreon.com
      "url": "https://www.patreon.com/feross"
  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned umbraco/umbraco-cms-backoffice-skills at 78b551bf9c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
10 files, 8,540 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to execute unit tests specifically within the Umbraco CMS ecosystem. It allows for automated verification of code changes, ensuring that custom modules and integrations function correctly before deployment.

When to use it

  • Validate new or modified Umbraco controllers, services, and models during development cycles.
  • Automate regression testing when updating dependencies or refactoring existing backoffice logic.
  • Ensure data integrity by running test suites against specific Umbraco configurations.
  • Integrate into CI/CD pipelines to gate deployments based on test pass/fail results.

Key capabilities

  • Executes unit tests tailored for the Umbraco framework architecture.
  • Supports testing of custom packages and extensions within the CMS environment.
  • Provides immediate feedback on code stability and functionality.

Example prompts

  • "Run the full unit test suite for my new content service module."
  • "Execute specific tests related to user authentication logic in the backoffice."
  • "Validate that my custom data type handler works correctly with existing Umbraco models."

Tips & gotchas

Ensure your development environment has all necessary Umbraco dependencies installed before running tests. Unit testing requires a clean, isolated environment; avoid running these tests directly on production instances to prevent unintended side effects or data corruption.