Soloncode Skin Skill
opensolon/soloncode
Generate installable SolonCode Web UI skin zip packages from natural-language design requests.
3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/).
$ npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-ext-monitors --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/Dynatrace/dynatrace-for-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dt-obs-ext-monitors .claude/skills/dt-obs-ext-monitors && 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 "dt-obs-ext-monitors" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitors into .claude/skills/dt-obs-ext-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-ext-monitors", 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/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitorsType 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 Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-ext-monitors --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dynatrace/dynatrace-for-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dt-obs-ext-monitors .agents/skills/dt-obs-ext-monitors && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dt-obs-ext-monitors" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitors into .agents/skills/dt-obs-ext-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-ext-monitors", 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 Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-ext-monitors --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dynatrace/dynatrace-for-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dt-obs-ext-monitors .cursor/skills/dt-obs-ext-monitors && 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 "dt-obs-ext-monitors" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitors into .cursor/skills/dt-obs-ext-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-ext-monitors", 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/Dynatrace/dynatrace-for-ai.git --path skills/dt-obs-ext-monitors--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 Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-ext-monitors --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dynatrace/dynatrace-for-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dt-obs-ext-monitors .gemini/skills/dt-obs-ext-monitors && 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 "dt-obs-ext-monitors" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitors into .gemini/skills/dt-obs-ext-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-ext-monitors", 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 Dynatrace/dynatrace-for-ai dt-obs-ext-monitorsInstalls 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 Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Dynatrace/dynatrace-for-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dt-obs-ext-monitors .github/skills/dt-obs-ext-monitors && 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 "dt-obs-ext-monitors" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitors into .github/skills/dt-obs-ext-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-ext-monitors", 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 Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-ext-monitors --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dynatrace/dynatrace-for-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dt-obs-ext-monitors .opencode/skills/dt-obs-ext-monitors && 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 "dt-obs-ext-monitors" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-ext-monitors into .opencode/skills/dt-obs-ext-monitors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-ext-monitors", 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.
dt-obs-ext-monitors3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/).
Dt Obs Ext Monitors is an agent skill from Dynatrace/dynatrace-for-ai. 3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/). Use when sending external synthetic test outcomes, CI monitor data, or third-party check results to Dynatrace. Covers token scope, full event schema for externaltestrun and externalteststep (including dt.securitycontext, ci., trace correlation, and pipeline-added fields), curl and Java DTO examples, and DQL verification. Triggers: "ingest test results", "send monitor results"…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/event-ingestion.md`).
It sits in Frontend & Design. It works with Java. The repository describes itself as: Skills, prompts, and instructions for building AI agents on top of Dynatrace production context. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 4f9aa71. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are dql).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Dt Obs Ext Monitors loads about 1.5k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 213 tokens; SKILL.md has 512 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.
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.
The full file from Dynatrace/dynatrace-for-ai at commit 4f9aa71, republished under its Apache-2.0 licence (© Dynatrace). 512 words, ~1,475 tokens.
.claude/skills/dt-obs-ext-monitors/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Send 3rd-party test and monitor results to Dynatrace Grail using the events ingest API.
This is the canonical replacement for the deprecated POST /api/v1/synthetic/ext/tests endpoint.
Events posted to /platform/ingest/custom/events/{endpoint} land in Grail and are processed
by OpenPipeline, which:
external.test.availability, external.test.duration) for alerting and SLOstest.id as an EXT_TEST Smartscape node — enabling Davis Problems to
attach to a named entity ("External test X went down") rather than floating without topology contextresult.status.category to step events (SUCCESS / SKIPPED / FAIL) for dashboard filteringTwo event types form a test result:
| Type | Purpose |
|---|---|
external_test_run | Overall pass/fail result for one test execution |
external_test_step | One step within that run (optional; enables step-level metrics) |
Two token types are accepted:
| Token type | Scope |
|---|---|
| Classic Api-Token | openpipeline.events.custom |
| Platform Token / OAuth | openpipeline:events.custom:ingest |
Common wrong guess that does NOT work: events.ingest.
Prerequisite: The ingest endpoint must be created in OpenPipeline before sending events. The
external.testsendpoint is provisioned automatically by the default Dynatrace 3rd-party monitors Monaco bundle. Seereferences/event-ingestion.mdfor setup details and custom endpoint creation.
Send one minimal test result (replace external.tests with your configured endpoint name):
curl -X POST "https://{env-id}.live.dynatrace.com/platform/ingest/custom/events/external.tests" \
-H "Authorization: Api-Token {token}" \
-H "Content-Type: application/json" \
-d '[{
"event.kind": "EXTERNAL_TEST_EVENT",
"event.type": "external_test_run",
"test.id": "my-api-health-check",
"test.run.id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"test.name": "My API Health Check",
"test.type": "api",
"test.run.status": "passed",
"test.run.availability": 1,
"test.run.duration_ms": 245,
"test.run.location": "us-east-1",
"dt.security_context": "team-checkout",
"timestamp": "2024-01-15T10:30:00Z"
}]'Expected response: HTTP 200 (empty body).
Full event schema, step events, extended examples with error fields and CI metadata, Java DTO shapes, and DQL queries:
references/event-ingestion.md
After sending, confirm the event appears:
fetch events, from:now()-1h
| filter event.type == "external_test_run"
| fields timestamp, test.id, test.name, test.run.status, test.run.duration_ms, test.run.location
| sort timestamp desc
| limit 20[{...}]), not an object wrapper ({"events":[...]}).timestamp must be ISO 8601 UTC (e.g. "2024-01-15T10:30:00Z").test.run.availability must be integer 1 or 0, not a string.test.run.id and test.id as the parent run event.test.step.id (unique within the run) in addition to test.run.id.event.kind: "EXTERNAL_TEST_EVENT" must be present — used by Grail for event classification.
Routing to the correct pipeline is driven by event.type, not event.kind.dt.smartscape.ext_test or result.status.category — these are written by
the pipeline after ingestion and will be overwritten if included.dt.security_context controls data access policies; it’s recommended to set it on every event to enable
per-team access control and cost attribution in multi-team tenants.Send the same test.id from multiple locations — each with a different test.run.location
value — to build a multi-location test. OpenPipeline creates one EXT_TEST node per test.id
and one availability metric timeseries per (test.id, location) pair.
This enables two alerting tiers out of the box:
| Alert type | Fires when |
|---|---|
| Local outage | A single location's availability drops (per-location timeseries) |
| Global outage | Average across all locations drops below threshold (e.g. majority failing) |
Threshold maths for a 3-location test: 1 location failing → avg 0.67 (no alert at 0.5 threshold); 2 failing → avg 0.33 (fires); all 3 failing → avg ≈ 0 (fires immediately).
Keep test.id stable across all locations — changing it creates a new Smartscape node and
breaks metric history.
dt.smartscape.frontend to
draw EXT_TEST → FRONTEND dependency edges in Smartscape© Dynatrace, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in skills/dt-obs-ext-monitors of Dynatrace/dynatrace-for-ai.
Open the folder on GitHubat commit 4f9aa71
Dt Obs Ext Monitors 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 |
|---|---|---|---|---|---|---|
| Dt Obs Ext Monitors this skillDynatrace/dynatrace-for-ai | 163 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Soloncode Skin Skillopensolon/soloncode | 197 | — | ~1.9k | Automated safety check: Pass | MIT | |
| RayRailly/tinte | 624 | — | ~712 | Automated safety check: Pass | MIT | |
| OpenOlat Frontend and Theming GuideOpenOLAT/OpenOLAT | 447 | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Accessibility Selenium Testingfugazi/test-automation-skills-agents | 249 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Huxerui App DevelopmentLangLang03/LineCodePro | 102 | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
opensolon/soloncode
Generate installable SolonCode Web UI skin zip packages from natural-language design requests.
Railly/tinte
Generate code screenshots via ray.tinte.dev API. An agent skill from Railly/tinte.
OpenOLAT/OpenOLAT
Covers OpenOlat's SASS theme architecture, CSS class conventions, DOM structure, and roughly 540 Java component renderers for styling work.
fugazi/test-automation-skills-agents
Accessibility testing toolkit using Selenium WebDriver 4+ with Java 21+ and axe-core engine.
LangLang03/LineCodePro
Develop HuxerUI SDK apps: create/open projects, build UI and app-side components, configure CMake/CLI, review, and troubleshoot.
gradusnikov/eclipse-chatgpt-plugin
Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.
Dynatrace/dynatrace-for-ai
Analyze dashboards and notebooks using Davis analyzers — anomaly detection, novelty scoring, and correlation.
Dynatrace/dynatrace-for-ai
Set up the Dynatrace iOS SDK (OneAgent) in an iOS project using Swift Package Manager.
Dynatrace/dynatrace-for-ai
End-to-end Dynatrace alerting lifecycle — anomaly detector setup and model selection (static threshold, adaptive baseline, seasonal baseline), alert event storage in Grail, problem grouping and…
Dynatrace/dynatrace-for-ai
AWS cloud resource monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization.
Dynatrace/dynatrace-for-ai
DAVIS problem analysis including root cause identification, impact assessment, and correlation with other telemetry.
Dynatrace/dynatrace-for-ai
Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go.
Works with
Categories
3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/). Dt Obs Ext Monitors is an agent skill from Dynatrace/dynatrace-for-ai. 3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/).
Dt Obs Ext Monitors fits situations like: sending external synthetic test outcomes; CI monitor data; third-party check results to Dynatrace.
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a claude-code`. Or copy the skill folder (skills/dt-obs-ext-monitors in Dynatrace/dynatrace-for-ai) into .claude/skills/dt-obs-ext-monitors in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a codex`. Or copy the skill folder (skills/dt-obs-ext-monitors in Dynatrace/dynatrace-for-ai) into .agents/skills/dt-obs-ext-monitors in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-ext-monitors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dt-obs-ext-monitors, .gemini/skills/dt-obs-ext-monitors, .github/skills/dt-obs-ext-monitors and .opencode/skills/dt-obs-ext-monitors in your project.
SKILL.md names no scripts, command-line tools or credentials: Dt Obs Ext Monitors is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Dt Obs Ext Monitors is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Dt Obs Ext Monitors: Soloncode Skin Skill (opensolon/soloncode, 197 stars), Ray (Railly/tinte, 624 stars), OpenOlat Frontend and Theming Guide (OpenOLAT/OpenOLAT, 447 stars) and Accessibility Selenium Testing (fugazi/test-automation-skills-agents, 249 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Dynatrace (a GitHub organization) maintains it in Dynatrace/dynatrace-for-ai, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 1, 2026.
Source: Dynatrace/dynatrace-for-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.