How do I install the Skin App skill?

Run npx skillmds@latest add openhands/skin-app in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skin App safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skin App?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skin App free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skin App?

openhands (@openhands) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skin App by openhands — Agent Skill

Name: Skin App
Rating: 4.5 (4 reviews)
Author: openhands

Skin App

This instance's skin is a Datadog infra-health dashboard (monitors, error-log patterns, per-app CPU/memory) with one-click agent-assisted fixes. Use this to understand what the dashboard shows, which APIs back it, and how "Fix" conversations originate.

openhands Updated Sep 17, 2026

File contents

This instance's skin: Datadog Monitor

This Agent Canvas instance exists to watch Datadog infrastructure health. Its skin (the default UI tab, code at ~/workspace/skin) is a hash-routed multi-page dashboard served by server.js from public/index.html:

Overview (#/) — portal landing page, one live headline stat per area.
Monitors (#/monitors, green) — alert/warn/healthy counters; alerting monitors as prominent cards. Fix starts an agent conversation to investigate and remediate that alert.
Error logs (#/errors, amber) — last 4 hours, two views:
- Patterns — errors clustered by normalized message template (ids/numbers/paths masked), with hit counts and a raw sample.
- By service — error volume ranked per service.
Memory / CPU (#/resources, blue) — per-app radial gauges of usage vs limits, most-constrained first. Audit starts a right-sizing agent run.

Data flow

server.js proxies the Datadog v1/v2 APIs — the browser never holds credentials:

GET /skin/api/monitors — monitor states (v1 monitors API)
GET /skin/api/logs / GET /skin/api/patterns — error logs & clusters (v2 logs search)
GET /skin/api/resources — CPU/memory metrics vs limits (v1 query)
POST /skin/api/agent — starts an OpenHands conversation for the Fix/Investigate/Audit buttons and returns a deep link to its transcript

Secrets are fetched from the host agent server at request time: DATADOG_TOKEN (API key, read access suffices), DATADOG_APP_KEY (application key). The Datadog site may be overridden with a DATADOG_SITE secret (default datadoghq.com; ddpat personal tokens usually mean a regional site like us5.datadoghq.com).

Working on it

When users report Datadog data looking wrong here, check these endpoints first, then the Datadog API auth (401 with a ddpat_… token usually means wrong site). To change the skin itself, see the skin skill: edit ~/workspace/skin, then POST /skin-api/restart.

---name: skin-appdescription: This instance's skin is a Datadog infra-health dashboard (monitors, error-log patterns, per-app CPU/memory) with one-click agent-assisted fixes. Use this to understand what the dashboard shows, which APIs back it, and how "Fix" conversations originate.---# This instance's skin: Datadog MonitorThis Agent Canvas instance exists to watch Datadog infrastructure health.Its skin (the default UI tab, code at `~/workspace/skin`) is a hash-routedmulti-page dashboard served by `server.js` from `public/index.html`:- **Overview** (`#/`) — portal landing page, one live headline stat per area.- **Monitors** (`#/monitors`, green) — alert/warn/healthy counters; alerting monitors as prominent cards. **Fix** starts an agent conversation to investigate and remediate that alert.- **Error logs** (`#/errors`, amber) — last 4 hours, two views: - **Patterns** — errors clustered by normalized message template (ids/numbers/paths masked), with hit counts and a raw sample. - **By service** — error volume ranked per service.- **Memory / CPU** (`#/resources`, blue) — per-app radial gauges of usage vs limits, most-constrained first. **Audit** starts a right-sizing agent run.## Data flow`server.js` proxies the Datadog v1/v2 APIs — the browser never holdscredentials:- `GET /skin/api/monitors` — monitor states (v1 monitors API)- `GET /skin/api/logs` / `GET /skin/api/patterns` — error logs & clusters (v2 logs search)- `GET /skin/api/resources` — CPU/memory metrics vs limits (v1 query)- `POST /skin/api/agent` — starts an OpenHands conversation for the Fix/Investigate/Audit buttons and returns a deep link to its transcriptSecrets are fetched from the host agent server at request time:`DATADOG_TOKEN` (API key, read access suffices), `DATADOG_APP_KEY`(application key). The Datadog site may be overridden with a`DATADOG_SITE` secret (default `datadoghq.com`; ddpat personal tokensusually mean a regional site like `us5.datadoghq.com`).## Working on itWhen users report Datadog data looking wrong here, check these endpointsfirst, then the Datadog API auth (401 with a `ddpat_…` token usually meanswrong site). To change the skin itself, see the `skin` skill: edit`~/workspace/skin`, then `POST /skin-api/restart`.

Frequently asked questions