Skip to content
TrustedSkillsbeta
Back to all skills

Umbraco Skill Code Analyzer

Listed
umbraco·vlatest·backend

Analyzes Umbraco .NET code for potential issues and best practices, boosting development efficiency and code quality.

Repository

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-skill-code-analyzer -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 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: dotenvx.com, paulmillr.com.

    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 hostpaulmillr.comundeclareddotenvx.comundeclared

    What it found

    • .claude/skills/umbraco-skill-code-analyzer/scripts/package-lock.json:1371contacts paulmillr.com
      "url": "https://paulmillr.com/funding/"
    • .claude/skills/umbraco-skill-code-analyzer/scripts/package-lock.json:2353contacts paulmillr.com
      "url": "https://paulmillr.com/funding/"
    • .claude/skills/umbraco-skill-code-analyzer/scripts/package-lock.json:1542contacts dotenvx.com
      "url": "https://dotenvx.com"

  • 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.

Commit
78b551bf9c
Manifest
.claude/skills/umbraco-skill-code-analyzer/SKILL.md
Scanned
4 files, 3,573 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 is a static analysis tool designed to validate code examples found within SKILL.md files, specifically for Umbraco development. It checks for issues related to import paths, extension types, deprecated coding patterns, and performs optional TypeScript compilation. The tool helps ensure code quality and adherence to Umbraco best practices by identifying potential problems early in the development process.

When to use it

  • When developing or updating SKILL.md files containing Umbraco code examples.
  • To proactively identify and fix issues with import paths, extension types, and deprecated patterns.
  • As part of a continuous integration workflow to maintain consistent code quality across Umbraco skills.

Key capabilities

  • Import Path Validation: Checks @umbraco-cms/backoffice/* imports against known modules.
  • Extension Type Verification: Validates type: values against recognized Umbraco extension types.
  • Deprecated Pattern Detection: Flags outdated code patterns for potential refactoring.
  • TypeScript Compilation (Optional): Performs syntax and type checking using TypeScript.
  • Detailed Reporting: Generates a code-analysis-report.json file with timestamped results, issue counts, and specific details about detected problems.

Example prompts

This skill doesn't directly respond to user prompts. Instead, it is run as a script within the development environment:

  1. npx skills add https://github.com/umbraco/umbraco-cms-backoffice-skills --skill umbraco-skill-code-analyzer (to install)
  2. cd .claude/skills/umbraco-skill-code-analyzer/scripts && npm install --silent && npx tsx analyze-code.ts (to run the analysis)

Tips & gotchas

  • TypeScript Dependency: Requires Node.js and npm for TypeScript compilation. The CHECK_TYPESCRIPT environment variable can be set to false to skip this step if not needed.
  • Updating Known Values: The tool relies on lists of known modules and extension types, which may need periodic updates via editing the analyze-code.ts script.
  • Report Interpretation: The generated JSON report provides detailed information about identified issues; review it carefully to understand and address any flagged problems.