Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Read the live Hermes desktop DOM/CSS over CDP. An agent skill from NousResearch/hermes-agent.
Install Inspecting Hermes Desktop Dom
$ npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NousResearch/hermes-agent inspecting-hermes-desktop-dom --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/software-development/inspecting-hermes-desktop-dom .claude/skills/inspecting-hermes-desktop-dom && rm -rf skills-srcUse ~/.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/
Install the "inspecting-hermes-desktop-dom" agent skill from https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-dom into .claude/skills/inspecting-hermes-desktop-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspecting-hermes-desktop-dom", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-domType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NousResearch/hermes-agent inspecting-hermes-desktop-dom --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/software-development/inspecting-hermes-desktop-dom .agents/skills/inspecting-hermes-desktop-dom && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inspecting-hermes-desktop-dom" agent skill from https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-dom into .agents/skills/inspecting-hermes-desktop-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspecting-hermes-desktop-dom", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NousResearch/hermes-agent inspecting-hermes-desktop-dom --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/software-development/inspecting-hermes-desktop-dom .cursor/skills/inspecting-hermes-desktop-dom && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "inspecting-hermes-desktop-dom" agent skill from https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-dom into .cursor/skills/inspecting-hermes-desktop-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspecting-hermes-desktop-dom", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NousResearch/hermes-agent.git --path skills/software-development/inspecting-hermes-desktop-dom--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NousResearch/hermes-agent inspecting-hermes-desktop-dom --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/software-development/inspecting-hermes-desktop-dom .gemini/skills/inspecting-hermes-desktop-dom && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "inspecting-hermes-desktop-dom" agent skill from https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-dom into .gemini/skills/inspecting-hermes-desktop-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspecting-hermes-desktop-dom", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NousResearch/hermes-agent inspecting-hermes-desktop-domInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/software-development/inspecting-hermes-desktop-dom .github/skills/inspecting-hermes-desktop-dom && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "inspecting-hermes-desktop-dom" agent skill from https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-dom into .github/skills/inspecting-hermes-desktop-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspecting-hermes-desktop-dom", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NousResearch/hermes-agent inspecting-hermes-desktop-dom --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NousResearch/hermes-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/software-development/inspecting-hermes-desktop-dom .opencode/skills/inspecting-hermes-desktop-dom && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "inspecting-hermes-desktop-dom" agent skill from https://github.com/NousResearch/hermes-agent/tree/main/skills/software-development/inspecting-hermes-desktop-dom into .opencode/skills/inspecting-hermes-desktop-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspecting-hermes-desktop-dom", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
inspecting-hermes-desktop-dom- GitHub stars
- 253k
- Used in
- 1 other repo
- Token cost
- ~1.6k tokens
- SKILL.md length
- 702 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Read the live Hermes desktop DOM/CSS over CDP. An agent skill from NousResearch/hermes-agent.
- Frontend & Design work in your project
- SKILL.md covers Overview, When to Use, The port and Reading the DOM, plus 3 more sections
- Calls npm, curl and node
What it does
Inspecting Hermes Desktop Dom is an agent skill from NousResearch/hermes-agent. Read the live Hermes desktop DOM/CSS over CDP.
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 Frontend & Design. The repository describes itself as: The agent that grows with you. The licence is MIT.
When your agent uses it
- Frontend & Design work in your project
Example prompts
- “/inspecting-hermes-desktop-dom”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit b30f95a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmcurlnodenpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, curl and npx, 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
Inspecting Hermes Desktop Dom loads about 1.6k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 702 words of instructions outside code blocks.
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 NousResearch/hermes-agent at commit b30f95a, republished under its MIT licence (© NousResearch). 702 words, ~1,557 tokens.
Download SKILL.mdSave it as
.claude/skills/inspecting-hermes-desktop-dom/SKILL.md (or your agent's skills folder).- name
- inspecting-hermes-desktop-dom
- description
- Read the live Hermes desktop DOM/CSS over CDP.
- version
- 1.0.0
- author
- Hermes Agent
- license
- MIT
- platforms
- linux, macos, windows
Inspecting the live Hermes desktop DOM
Overview
When you are developing apps/desktop and the user is running that same app
(hgui / npm run dev), you can read the live rendered DOM of the window
they are looking at — computed styles, geometry, which CSS rule actually won,
console output — instead of inferring it from .tsx and being wrong.
Dev-server runs open a Chrome DevTools Protocol port on 127.0.0.1:9222
automatically. The renderer is a Chromium page, so everything DevTools can read,
a script can read.
This does not replace looking at it. CDP answers factual questions ("what is the computed padding", "did this element render", "which selector matches"). It cannot tell you whether the result looks good. Colour balance, spacing feel, and "is this ugly" still need the user's eyes or a screenshot. Answer facts with CDP; hand aesthetics to the user.
When to Use
- Verifying a UI change actually took effect in the running app
- "Why is this element still X?" — find the winning rule before editing anything
- Locating a stable selector for a component you're about to change
- Checking a design token's computed value on a real node
- Reading renderer console errors the user mentions but can't copy out
Don't use for: perf profiling or heap work (node-inspect-debugger,
debugging-hermes-desktop), or anything where the real question is "does this
look right".
The port
Open on 127.0.0.1:9222 for any dev-server run. Closed in exactly two cases
(apps/desktop/electron/dev-cdp.ts):
- packaged builds — always, and no environment value overrides it;
- no
HERMES_DESKTOP_DEV_SERVER— an unpackagedelectron .againstdist/is how the packaged app gets smoke tested, so it behaves like one.
HERMES_DESKTOP_CDP_PORT moves the port (=9333) or disables it (=off).
Check before doing anything else:
curl -s --max-time 3 http://127.0.0.1:${HERMES_DESKTOP_CDP_PORT:-9222}/json/versionEmpty → no port. Do not guess another port silently.
Never relaunch the user's app to get a port. That destroys their session and their state. Launch your own isolated instance instead (below).
Reading the DOM
apps/desktop/scripts/eval.mjs is the one-liner:
cd apps/desktop
node scripts/eval.mjs "document.querySelectorAll('[data-slot]').length"For multi-step work use the shared client — it has target discovery and promise-aware eval:
import { CDP, SELECTORS } from './scripts/perf/lib/cdp.mjs'
const cdp = await CDP.connect({ port: 9222, match: '5174' })
const out = await cdp.eval(`JSON.stringify({
radius: getComputedStyle(document.documentElement).getPropertyValue('--radius-scalar').trim(),
composer: !!document.querySelector('[data-slot="composer-rich-input"]')
})`)
cdp.close()SELECTORS in scripts/perf/lib/cdp.mjs holds the stable data-slot hooks
(composer, thread viewport, assistant message, turn pair, profile rail). Prefer
them over inventing a querySelector — they are updated as a unit when
components move.
The question this is best at: which rule won?
Editing every call site because a style "isn't applying" is the classic waste. Read the real node first:
const el = document.querySelector('[data-slot="aui_assistant-message-root"] a')
JSON.stringify({
ownClasses: el.className,
weight: getComputedStyle(el).fontWeight,
parents: (() => {
const out = []
let n = el
while ((n = n.parentElement) && out.length < 6) out.push(n.className)
return out
})()
})If the node carries no class of its own, the value is inherited — sweeping
call sites will not fix it, and you need the ancestor rule. A plugin stylesheet
(e.g. @tailwindcss/typography's prose a { font-weight: 500 }) routinely beats
a utility class; override on the shared class, not at each usage.
Show full SKILL.md (263 more words)Show less
Your own isolated instance
When there is no port, or you must not disturb the user's window:
cd apps/desktop
HERMES_HOME=$HOME/.hermes/cache/scratch/cdp-probe-home \
HERMES_DESKTOP_DEV_SERVER=http://127.0.0.1:5174 \
HERMES_DESKTOP_CDP_PORT=9333 \
npx electron . --user-data-dir=$HOME/.hermes/cache/scratch/cdp-probe-userdataThe separate --user-data-dir dodges Electron's single-instance lock, so it
cannot collide with a running hgui; the separate HERMES_HOME keeps it away
from real sessions. Pick a port other than 9222 for the same reason. Run it in
the background and kill it when done.
npm run perf:serve does the same with a temp HERMES_HOME baked in, if you
also want the perf harness.
Pitfalls
- Never kill the user's dev server or app to "free" anything. A mid-serve
kill nukes Chromium's socket pool, and the resulting
ERR_NETWORK_CHANGEDgets blamed on whatever you just changed. - A throwaway
HERMES_HOMEhas no backend. The app logsECONNREFUSEDforhermes:apiand may exit on its own. The renderer still mounts and the DOM is readable — read promptly, and don't mistake a self-exited probe for a broken port. Chromium logsDevTools listening on ws://127.0.0.1:<port>/…when it binds; that line is the proof the port opened. - Poll, don't probe once. A just-launched app needs a second or two before the port answers.
- Never dump the whole DOM. The desktop renders hundreds of nodes and
outerHTMLwill bury your context. Project down to a small JSON object inside the evaluated expression. - Pass
matchtoCDP.connect. Without it you may attach to the pet overlay, quick-entry window, or a devtools target instead of the main window. cdp.evalreturns the value; rawRuntime.evaluatedouble-nests it (.result.result.value). Use the wrapper.import.meta.env.DEVistrueundervite devin this repo. The note inapps/desktop/scripts/profile-typing-lag.mdclaiming otherwise is stale.
© NousResearch, 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 skills/software-development/inspecting-hermes-desktop-dom of NousResearch/hermes-agent.
Open the folder on GitHubat commit b30f95a
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NousResearch/hermes-agent, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Inspecting Hermes Desktop Dom 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Inspecting Hermes Desktop Dom this skillNousResearch/hermes-agent | 253k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from NousResearch/hermes-agent
All 31 skills in this repoAI Presenter Video
NousResearch/hermes-agent
Produces a presenter-led video from a topic or script plus one authorized presenter image, with captions, lip-sync checks and acceptance reports.
Word DOCX Toolkit
NousResearch/hermes-agent
Creates, reads, edits and templates Word .docx files with python-docx scripts, including tracked changes, comments, tables of contents and health checks.
Grounded Citations
NousResearch/hermes-agent
Attaches a numbered, URL-backed citation to every outside fact in an answer or document, rejecting quotes that aren't real.
PDF
NousResearch/hermes-agent
PDF files: create, read, merge, fill, OCR, edit text. An agent skill from NousResearch/hermes-agent.
Scrollcraft
NousResearch/hermes-agent
Premium scroll-driven landing pages; scroll = timeline. An agent skill from NousResearch/hermes-agent.
XLSX
NousResearch/hermes-agent
Create, read, edit Excel .xlsx workbooks and CSVs. An agent skill from NousResearch/hermes-agent.
Related
Categories
Questions about Inspecting Hermes Desktop Dom
What does Inspecting Hermes Desktop Dom do?
Read the live Hermes desktop DOM/CSS over CDP. An agent skill from NousResearch/hermes-agent. Inspecting Hermes Desktop Dom is an agent skill from NousResearch/hermes-agent. Read the live Hermes desktop DOM/CSS over CDP.
When should I use Inspecting Hermes Desktop Dom?
Inspecting Hermes Desktop Dom fits situations like: frontend & Design work in your project.
How do I install Inspecting Hermes Desktop Dom in Claude Code?
Run `npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a claude-code`. Or copy the skill folder (skills/software-development/inspecting-hermes-desktop-dom in NousResearch/hermes-agent) into .claude/skills/inspecting-hermes-desktop-dom in your project. Claude Code loads it when a task matches its description.
How do I install Inspecting Hermes Desktop Dom in Codex?
Run `npx skills add NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a codex`. Or copy the skill folder (skills/software-development/inspecting-hermes-desktop-dom in NousResearch/hermes-agent) into .agents/skills/inspecting-hermes-desktop-dom in your project. Codex loads it when a task matches its description.
Can I use Inspecting Hermes Desktop Dom 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 NousResearch/hermes-agent --skill inspecting-hermes-desktop-dom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inspecting-hermes-desktop-dom, .gemini/skills/inspecting-hermes-desktop-dom, .github/skills/inspecting-hermes-desktop-dom and .opencode/skills/inspecting-hermes-desktop-dom in your project.
What does Inspecting Hermes Desktop Dom need to run?
Going by SKILL.md and its folder, Inspecting Hermes Desktop Dom needs the command-line tools its instructions call (npm, curl, node and npx). Our summary lists: Node.js.
Does Inspecting Hermes Desktop Dom access the network?
SKILL.md contains no URLs. Its commands use npm, curl and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Inspecting Hermes Desktop Dom 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 Inspecting Hermes Desktop Dom use?
Inspecting Hermes Desktop Dom is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Inspecting Hermes Desktop Dom 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 Inspecting Hermes Desktop Dom?
Skills that share tags, products or a category with Inspecting Hermes Desktop Dom: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Inspecting Hermes Desktop Dom?
NousResearch (a GitHub organization) maintains it in NousResearch/hermes-agent, which has 252,613 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 11, 2026.
Source: NousResearch/hermes-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.