Official agent skill

Dev Server

by Azure in Azure/cosmos-explorer

Start the local webpack dev server and connect to it with the Playwright browser.

OfficialMITAuto-check passedTesting & QA

Install Dev Server

skills CLI
$ npx skills add Azure/cosmos-explorer --skill dev-server -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Azure/cosmos-explorer dev-server --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Azure/cosmos-explorer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/dev-server .claude/skills/dev-server && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dev-server
GitHub stars
131
Token cost
~1.6k tokens
SKILL.md length
532 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Start the local webpack dev server and connect to it with the Playwright browser.

  • Asked to start the dev server
  • SKILL.md covers Pre-Start: Check Dependencies, Check for Existing Server, Start the Dev Server and Wait for Compilation, plus 4 more sections
  • Calls npm and curl
  • Preview the app

What it does

Dev Server is an agent skill from Azure/cosmos-explorer, published by the product's own GitHub organization. Start the local webpack dev server and connect to it with the Playwright browser. Use this skill when asked to start the dev server, preview the app, or interact with the running application in a browser.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Browser testing and Browser automation. It works with webpack, Playwright, Microsoft Azure and Azure Cosmos DB. The repository describes itself as: UI for Azure Cosmos DB. Powers the Azure Portal, https://cosmos.azure.com/, and the Cosmos DB Emulator. The licence is MIT.

When your agent uses it

  • Asked to start the dev server
  • Preview the app
  • Interact with the running application in a browser

Example prompts

  • “/dev-server”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): shell, browser

What it can do on your machine

Read from SKILL.md and the folder at commit 226a7a2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • shell
    • browser

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dev Server loads about 1.6k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 532 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Azure/cosmos-explorer at commit 226a7a2, republished under its MIT licence (© Azure). 532 words, ~1,559 tokens.

Download SKILL.mdSave it as .claude/skills/dev-server/SKILL.md (or your agent's skills folder).
name
dev-server
description
Start the local webpack dev server and connect to it with the Playwright browser. Use this skill when asked to start the dev server, preview the app, or interact with the running application in a browser.
allowed-tools
shell, browser

Dev Server Skill

Use this skill to start the Cosmos Explorer webpack dev server and connect to it with the Playwright MCP browser for interactive testing, debugging, or previewing the application.

Pre-Start: Check Dependencies

Before starting the dev server, check whether npm install needs to be run:

bash
if [ ! -d node_modules ] || [ package.json -nt node_modules ] || [ package-lock.json -nt node_modules ]; then
  npm install
fi

On Windows PowerShell:

powershell
if (-not (Test-Path node_modules) -or
    (Get-Item package.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime -or
    (Get-Item package-lock.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime) {
    npm install
}

Always run this check before starting the dev server.

Check for Existing Server

Before starting a new server, check if one is already running on port 1234:

powershell
try {
    $response = Invoke-WebRequest -Uri "https://localhost:1234/_ready" -SkipCertificateCheck -UseBasicParsing -ErrorAction Stop
    if ($response.StatusCode -eq 200) {
        Write-Host "Dev server is already running and ready!"
    }
} catch {
    Write-Host "No dev server detected, starting a new one..."
}

If the server is already running and ready, skip to Connect the Playwright Browser.

Start the Dev Server

Start the webpack dev server as a detached background process so it persists across session changes:

bash
npm start

The dev server:

  • Runs at https://localhost:1234 (HTTPS with self-signed certificate)
  • Uses webpack dev mode with live reload
  • Exposes a /_ready health-check endpoint

Wait for Compilation

After starting the server, poll the /_ready endpoint until it returns HTTP 200. Do not proceed to browser navigation until /_ready returns 200.

On Windows PowerShell:

powershell
$timeout = 120
$elapsed = 0
while ($elapsed -lt $timeout) {
    try {
        $response = Invoke-WebRequest -Uri "https://localhost:1234/_ready" -SkipCertificateCheck -UseBasicParsing -ErrorAction Stop
        if ($response.StatusCode -eq 200) {
            Write-Host "Dev server is ready!"
            break
        }
    } catch {
        # Server not ready yet
    }
    Start-Sleep -Seconds 3
    $elapsed += 3
}
if ($elapsed -ge $timeout) {
    Write-Error "Dev server did not become ready within $timeout seconds"
}

On bash:

bash
timeout=120
elapsed=0
while [ $elapsed -lt $timeout ]; do
  if curl -sk https://localhost:1234/_ready 2>/dev/null | grep -q "Compilation complete"; then
    echo "Dev server is ready!"
    break
  fi
  sleep 3
  elapsed=$((elapsed + 3))
done
if [ $elapsed -ge $timeout ]; then
  echo "Dev server did not become ready within $timeout seconds" >&2
fi

Connect the Playwright Browser

Once the dev server is ready, use the Playwright MCP browser tools to navigate to the application.

Navigate to the desired entry point:

  • https://localhost:1234/hostedExplorer.html — Hosted explorer (standalone mode). Best for general UI testing and interaction without Azure Portal framing.
  • https://localhost:1234/explorer.html — Portal explorer (Azure Portal iframe mode). Requires portal context/messages to initialize fully.
  • https://localhost:1234/index.html — Emulator mode. Requires a local Cosmos DB Emulator running on port 8081.
  • https://localhost:1234/testExplorer.html — Test explorer (dev mode only). Used for E2E test harness.
Default Navigation

When no specific page is requested, navigate to https://localhost:1234/hostedExplorer.html as it provides the most complete standalone experience.

Dismiss Webpack Warnings Overlay

After the page loads, a webpack dev server overlay may appear inside an iframe showing DefinePlugin warnings. If a "Dismiss" button (×) is visible in the overlay, click it to close the warnings before proceeding with any other interaction.

Show full SKILL.md (227 more words)Show less

Available Pages Reference

URLEntry PointDescription
/hostedExplorer.htmlsrc/HostedExplorer.tsxStandalone hosted explorer (cosmos.azure.com)
/explorer.htmlsrc/Main.tsxPortal iframe explorer
/index.htmlsrc/Index.tsxEmulator explorer
/testExplorer.htmltest/testExplorer/TestExplorer.tsTest harness (dev mode only)
/terminal.htmlsrc/Terminal/index.tsNotebook terminal
/quickstart.htmlsrc/quickstart.tsQuickstart page
/selfServe.htmlsrc/SelfServe/SelfServe.tsxSelf-serve configuration
/galleryViewer.htmlsrc/GalleryViewer/GalleryViewer.tsxNotebook gallery viewer

Troubleshooting

HTTPS / Self-Signed Certificate Errors

The dev server uses HTTPS with a self-signed certificate. If the Playwright browser fails to navigate with an error like ERR_CERT_AUTHORITY_INVALID or any other SSL/TLS certificate error, stop immediately and tell the user:

The Playwright MCP server needs the --ignore-https-errors argument to connect to the dev server's self-signed certificate. Please add --ignore-https-errors to your Playwright MCP server configuration and try again.

Do not attempt workarounds (e.g., creating new browser contexts manually). The --ignore-https-errors flag is the correct fix.

Guidelines

  • Always start the dev server as a detached background process so it survives session changes.
  • Always wait for /_ready to return 200 before navigating the browser.
  • Ignore certificate errors in shell HTTP requests (e.g., -SkipCertificateCheck, curl -k). For the Playwright browser, the --ignore-https-errors MCP argument must be configured.
  • If the dev server is already running on port 1234, reuse it instead of starting a new one.
  • If the server fails to start, check for port conflicts (netstat -ano | findstr :1234 on Windows).
  • When stopping the dev server, use Stop-Process with the specific PID of the node process.

© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/dev-server of Azure/cosmos-explorer.

Open the folder on GitHubat commit 226a7a2

Compare with similar skills

Dev Server next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dev Server compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Server this skillAzure/cosmos-explorer131—~1.6kAutomated safety check: PassMIT
playwright-cli Browser Automationgithub/gh-aw5.3k23 repos~2.8kAutomated safety check: PassMIT
Playwright Skilllackeyjb/playwright-skill3.2k—~1.9kAutomated safety check: PassMIT
Playwright CLItestdino-hq/playwright-skill3851 repos~2.5kAutomated safety check: PassMIT
Playwright Bot Bypassgreekr4/playwright-bot-bypass200—~3.4kAutomated safety check: PassMIT
UI Previewtingly-dev/tingly-box351—~2kAutomated safety check: NotesMPL-2.0

Similar skills

  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Playwright Skill

    lackeyjb/playwright-skill

    Complete browser automation with Playwright. An agent skill from lackeyjb/playwright-skill.

    3.2k GitHub stars~1.9k tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Playwright CLI

    testdino-hq/playwright-skill

    Automates browser interactions for testing and validating your own web applications using playwright-cli.

    385 GitHub starsUsed in 1 repo~2.5k tokens
    Testing & QAAuto-check passed
  • Playwright Bot Bypass

    greekr4/playwright-bot-bypass

    This skill should be used when the user asks to "bypass bot detection", "avoid CAPTCHA", "stealth browser automation", "undetected playwright", "bypass Google bot check", "rebrowser-playwright", or…

    200 GitHub stars~3.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • UI Preview

    tingly-dev/tingly-box

    Capture headless-Chrome screenshots of the tingly-box frontend (running locally in mock mode) so frontend changes can be visually verified in environments without a real browser.

    351 GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check: notes
  • Open Browser

    JasonHonKL/Openbrowser

    A skill your agent uses whenever the task involves browsing web pages, extracting page content, clicking forms, or completing web workflows.

    114 GitHub stars~1.6k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

More from Azure/cosmos-explorer

  • Run Unit Tests

    Azure/cosmos-explorer

    Official

    Run unit tests for the Cosmos Explorer project. An agent skill from Azure/cosmos-explorer.

    131 GitHub stars~638 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Dev Server

What does Dev Server do?

Start the local webpack dev server and connect to it with the Playwright browser. Dev Server is an agent skill from Azure/cosmos-explorer, published by the product's own GitHub organization. Start the local webpack dev server and connect to it with the Playwright browser.

When should I use Dev Server?

Dev Server fits situations like: asked to start the dev server; preview the app; interact with the running application in a browser.

How do I install Dev Server in Claude Code?

Run `npx skills add Azure/cosmos-explorer --skill dev-server -a claude-code`. Or copy the skill folder (.github/skills/dev-server in Azure/cosmos-explorer) into .claude/skills/dev-server in your project. Claude Code loads it when a task matches its description.

How do I install Dev Server in Codex?

Run `npx skills add Azure/cosmos-explorer --skill dev-server -a codex`. Or copy the skill folder (.github/skills/dev-server in Azure/cosmos-explorer) into .agents/skills/dev-server in your project. Codex loads it when a task matches its description.

Can I use Dev Server in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/cosmos-explorer --skill dev-server -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-server, .gemini/skills/dev-server, .github/skills/dev-server and .opencode/skills/dev-server in your project.

What does Dev Server need to run?

Going by SKILL.md and its folder, Dev Server needs the command-line tools its instructions call (npm and curl). Our summary lists: Node.js. Its frontmatter pre-approves these tools: shell, browser.

Does Dev Server access the network?

SKILL.md contains no URLs. Its commands use npm and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dev Server safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dev Server use?

Dev Server is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Server use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dev Server?

Skills that share tags, products or a category with Dev Server: playwright-cli Browser Automation (github/gh-aw, 5.3k stars), Playwright Skill (lackeyjb/playwright-skill, 3.2k stars), Playwright CLI (testdino-hq/playwright-skill, 385 stars) and Playwright Bot Bypass (greekr4/playwright-bot-bypass, 200 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Server?

Azure (a GitHub organization, an official publisher) maintains it in Azure/cosmos-explorer, which has 131 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.

Source: Azure/cosmos-explorer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.