Umbraco.Automate: Skill for Claude Code

.claude/skills/demo-site-management/SKILL.md

demo-site-management is a skill for Claude Code from umbraco/Umbraco.Automate. It costs 50 tokens per session (1,882 once invoked), scanned A, original, MIT.

A development-site management skill for the Umbraco.Automate demo site, including starting, stopping, checking, restarting, and opening it.

In plain words
What is it for?
It is for launching the demo site with the required profile, checking whether it is running, discovering its port, stopping it, restarting it, or opening it in a browser.
Why use it?
It handles the site's dynamic port discovery, so developers do not need to find or manage the site address manually.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is umbraco/Umbraco.Automate's own configuration. It tells Claude Code how to work on Umbraco.Automate itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Umbraco.Automate configures →

Reuse

Borrowing it

Nothing to install: this file belongs to umbraco/Umbraco.Automate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/umbraco/Umbraco.Automate/v18/dev/.claude/skills/demo-site-management/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/umbraco/Umbraco.Automate

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for demo-site-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/umbraco/umbraco.automate/demo-site-management/github.svg)](https://agentmods.dev/skills/umbraco/umbraco.automate/demo-site-management)
Your own site
<a href="https://agentmods.dev/skills/umbraco/umbraco.automate/demo-site-management"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco.automate/demo-site-management/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for demo-site-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/umbraco/umbraco.automate/demo-site-management"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco.automate/demo-site-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,882 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01882
Opus 5.5 $0.00020 $0.00753
Sonnet 5.5 $0.00010 $0.00376
Haiku 4.5 $0.00005 $0.00188

Measured 29d ago against content hash dc10e4bbfb1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

demo-site-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 29d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/demo-site-management/SKILL.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Demo Site Management

Manage the Umbraco.Automate demo site. Each worktree gets its own stable dev port, assigned once by Umbraco.Community.WorktreeDevPort and stored in that worktree's own git config — no named pipe, socket, or discovery endpoint to query.

Command: $ARGUMENTS

Execute the requested demo site operation.

Available commands

  • start: Start demo site with the DemoSite profile
  • stop: Stop the running demo site
  • status: Check if site is running and show its port
  • restart: Stop and restart the demo site
  • open: Open the demo site in default browser

Current Environment

  • Working directory: !pwd
  • Git branch: !git branch --show-current 2>/dev/null || echo "not in git repo"
  • Background tasks: !echo "Check with /tasks command for active background tasks"

Implementation Guide

For "start"

  1. Check if already running using multi-method detection:
    • Try reading the port (see "Get the worktree's dev port" section) and connecting to it
    • Check if background tasks exist with "DemoSite" in description
    • If running, report and exit
  2. Detect demo site path:
    • Read Directory.Packages.props and extract the major from the Umbraco.Cms.Core version (range lower bound or fixed, e.g. [18.0.0, …) or 18.0.0 → 18)
    • Demo site path: demos/v{major}/Umbraco.Automate.DemoSite
  3. Ensure the frontend assets exist (a fresh clone or worktree has none, and the Automate section then renders blank with no error):
    • Run scripts/build-frontend.ps1 (Windows) or bash scripts/build-frontend.sh (macOS/Linux) from the repo root
    • On Windows, run it with the PowerShell tool, not pwsh ... through Bash: a worktree-isolated session's Bash tool refuses to shell out to pwsh
    • Safe to run every start: it is a no-op when both wwwroot folders are already populated
    • On a fresh worktree it runs npm ci + npm run build at the repo root and can take a few minutes - allow a long timeout and never run npm by hand instead
    • It handles the Node version itself (reads engines.node, and prepends an installed nvm-for-windows version to PATH for that process only - never run nvm use)
    • If it exits non-zero, stop and report its message: starting the site anyway gives a blank section with no error
  4. If not running, start in background: cd demos/v{major}/Umbraco.Automate.DemoSite && dotnet run --launch-profile DemoSite
  5. Wait 15-20 seconds for startup (the package picks a free port on first run in this worktree, or reuses the one it already picked)
  6. Read the port (see "Get the worktree's dev port" section)
  7. Report:
    • Task ID for later stopping (save this for future commands)
    • Port number
    • Site URL (https://127.0.0.1:<port>)

Read the full file on GitHub · 152 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 29d ago Changed · +1 lines dc10e4bbfb1c
  2. 1mo ago Changed · -72 lines · +3 tokens per session a51366cfdd18
  3. 1mo ago Changed · +15 lines 320e19fc846a
  4. 2mo ago First seen · 208 lines · 47 tokens per session scan A 723e5082d84a

Subscribe to this mod's changes

demo-site-management is a skill published in the GitHub repository umbraco/Umbraco.Automate (5 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 1,882 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens