Token Map
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
Suggest and validate semantic dictionary (SD) mappings for new security integrations using vendor API samples or live events.
$ npx skills add Dynatrace/dynatrace-for-ai --skill dt-sec-semantic-mapping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-sec-semantic-mapping --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-sec-semantic-mapping .claude/skills/dt-sec-semantic-mapping && 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-sec-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-sec-semantic-mapping into .claude/skills/dt-sec-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-sec-semantic-mapping", 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-sec-semantic-mappingType 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-sec-semantic-mapping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-sec-semantic-mapping --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-sec-semantic-mapping .agents/skills/dt-sec-semantic-mapping && 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-sec-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-sec-semantic-mapping into .agents/skills/dt-sec-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-sec-semantic-mapping", 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-sec-semantic-mapping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-sec-semantic-mapping --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-sec-semantic-mapping .cursor/skills/dt-sec-semantic-mapping && 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-sec-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-sec-semantic-mapping into .cursor/skills/dt-sec-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-sec-semantic-mapping", 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-sec-semantic-mapping--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-sec-semantic-mapping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-sec-semantic-mapping --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-sec-semantic-mapping .gemini/skills/dt-sec-semantic-mapping && 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-sec-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-sec-semantic-mapping into .gemini/skills/dt-sec-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-sec-semantic-mapping", 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-sec-semantic-mappingInstalls 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-sec-semantic-mapping -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-sec-semantic-mapping .github/skills/dt-sec-semantic-mapping && 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-sec-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-sec-semantic-mapping into .github/skills/dt-sec-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-sec-semantic-mapping", 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-sec-semantic-mapping -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-sec-semantic-mapping --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-sec-semantic-mapping .opencode/skills/dt-sec-semantic-mapping && 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-sec-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-sec-semantic-mapping into .opencode/skills/dt-sec-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-sec-semantic-mapping", 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-sec-semantic-mappingSuggest and validate semantic dictionary (SD) mappings for new security integrations using vendor API samples or live events.
Dt Sec Semantic Mapping is an agent skill from Dynatrace/dynatrace-for-ai. Suggest and validate semantic dictionary (SD) mappings for new security integrations using vendor API samples or live events. Use when: mapping a new security vendor data to Dynatrace SD; checking required fields; validating namespaces; highlighting discrepancies vs the semantic dictionary; proposing mapping improvements; running runtime validation against live tenant data.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including reference files (for example `references/intake-and-constraints.md`, `references/mapping-workflow.md` and `references/runtime-validation.md`).
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.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.dynatrace.comFrom 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 Sec Semantic Mapping loads about 1.5k tokens when it runs, and up to ~44k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 584 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). 584 words, ~1,470 tokens.
.claude/skills/dt-sec-semantic-mapping/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.Build and validate semantic-dictionary-aligned mappings for new security integrations.
Use this skill when a user wants to:
security.events fields (Workflow A).The Semantic Dictionary (SD) defines the canonical field set for security.events. See references/semantic-reference.md for the canonical reference: local-vs-live sources, queryable Grail tables, when-to-query decision matrix, and the authority rule (live SD wins on disagreement).
Always run the intake checklist in references/intake-and-constraints.md before generating or validating a mapping. If inputs are incomplete, continue with a partial draft but explicitly list missing evidence and confidence limits.
All baseline material lives inside this skill:
samples/ — real integration payloads covering all finding types and providers. Consulted as a fallback when primary references (SD, data-model-notes, known-discrepancies, validation-rules, object-type-expectations) leave a specific question unresolved — not as a routine step on every workflow run.references/semantic-reference.md — SD reference, field taxonomy, event types, provider taxonomy, and entity scopingreferences/validation-policy-and-reporting.md — validation rules, acceptable discrepancies, and report templatesreferences/intake-and-constraints.md — intake checklist, output contract, object.type expectations, and OpenPipeline constraintsThe mapping MUST address the correct set of event.type values per finding class. Detection integrations are push-based and do not use scan cycles — never require scan events for detection.
See validation-policy-and-reporting.md § Event-Type Coverage for the full table, severity rules, and the alternative-classification path when a detection-class mapping incorrectly emits *_SCAN events.
This skill operates in three modes. Detect the mode from context:
| Mode | Input | Procedural source |
|---|---|---|
| Workflow A — Suggest a new mapping | Raw vendor API payloads only | references/mapping-workflow.md § Workflow A (Phase 1 mapping table → user approval → Phase 2 sample JSON) |
| Workflow B1 — Static validation | Existing mapping + vendor API samples | references/mapping-workflow.md § Workflow B — classify input mode (final ingested / theoretical), apply rules, produce diff-highlighted table |
| Workflow B2 — Runtime validation | Existing mapping + live tenant access | references/runtime-validation.md — load the security (AppSec) events supporting skill first (REQUIRED Step 0), then run the query pack, produce a Validation Summary table |
All workflows follow the output contracts in references/intake-and-constraints.md and the report templates in references/validation-policy-and-reporting.md. Validation rules (event-type coverage, required fields, scan references, namespace requirements, value/type checks, vendor-namespace duplication) live in references/validation-policy-and-reporting.md.
See references/validation-policy-and-reporting.md for the canonical list of acceptable SD deviations and vendor-namespace patterns. Do NOT raise critical/major issues for fields on that list. Genuinely unknown fields (not in local refs AND not in the live SD — see references/semantic-reference.md) must be questioned per references/validation-policy-and-reporting.md.
This skill covers:
This skill does not cover:
references/semantic-reference.md — SD reference plus data-model notes: local sources, live (queryable) sources, DQL patterns, when-to-query decision matrix, authority rule, field taxonomysecurity.events and Grail tablesreferences/intake-and-constraints.md — intake checklist, output contract, OpenPipeline constraints, and object.type namespace expectationsreferences/mapping-workflow.md — how to build and refine a mapping candidatereferences/validation-policy-and-reporting.md — full validation rule set, known discrepancies, and discrepancy report templatesreferences/runtime-validation.md — optional real-environment query validation pack© 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 20 other files (references) in skills/dt-sec-semantic-mapping of Dynatrace/dynatrace-for-ai.
Open the folder on GitHubat commit 4f9aa71
Dt Sec Semantic Mapping 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 Sec Semantic Mapping this skillDynatrace/dynatrace-for-ai | 162 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Maps Geographyasgeirtj/system_prompts_leaks | 69k | — | ~717 | Automated safety check: Pass | CC0-1.0 | |
| Suggestion Boxpaperclipai/paperclip | 99k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Feature Maponyx-dot-app/onyx | 32k | — | ~459 | Automated safety check: Pass | Custom licence | |
| Semantic Liststhedaviddias/Front-End-Checklist | 74k | — | ~504 | Automated safety check: Pass | MIT |
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
asgeirtj/system_prompts_leaks
Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable
paperclipai/paperclip
Quietly suggest a concrete improvement after observing material, generalizable friction in agent work.
onyx-dot-app/onyx
Use the Onyx feature map (.agents/feature-map/) to learn what a product surface does, the code behind it, and what a change can break.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic list elements.
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.
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
3rd-party test and monitor result ingestion into Dynatrace Grail via the platform events ingest API (platform/ingest/custom/events/).
Dynatrace/dynatrace-for-ai
DAVIS problem analysis including root cause identification, impact assessment, and correlation with other telemetry.
Suggest and validate semantic dictionary (SD) mappings for new security integrations using vendor API samples or live events. Dt Sec Semantic Mapping is an agent skill from Dynatrace/dynatrace-for-ai. Suggest and validate semantic dictionary (SD) mappings for new security integrations using vendor API samples or live events.
Dt Sec Semantic Mapping fits situations like: : mapping a new security vendor data to Dynatrace SD; checking required fields; validating namespaces; highlighting discrepancies vs the semantic dictionary.
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-sec-semantic-mapping -a claude-code`. Or copy the skill folder (skills/dt-sec-semantic-mapping in Dynatrace/dynatrace-for-ai) into .claude/skills/dt-sec-semantic-mapping in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-sec-semantic-mapping -a codex`. Or copy the skill folder (skills/dt-sec-semantic-mapping in Dynatrace/dynatrace-for-ai) into .agents/skills/dt-sec-semantic-mapping 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-sec-semantic-mapping -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-sec-semantic-mapping, .gemini/skills/dt-sec-semantic-mapping, .github/skills/dt-sec-semantic-mapping and .opencode/skills/dt-sec-semantic-mapping in your project.
SKILL.md names no scripts, command-line tools or credentials: Dt Sec Semantic Mapping is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: docs.dynatrace.com. 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 Sec Semantic Mapping 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 43k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Dt Sec Semantic Mapping: Token Map (nexu-io/open-design, 100k stars), Maps Geography (asgeirtj/system_prompts_leaks, 69k stars), Suggestion Box (paperclipai/paperclip, 99k stars) and Feature Map (onyx-dot-app/onyx, 32k 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 162 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.