Frontmcp Authorities
agentfront/frontmcp
A skill your agent uses when implementing authorization and access control for FrontMCP tools, resources, prompts, or skills, deciding who may invoke what.
Suggest and validate semantic dictionary (SD) mappings for audit log integrations using raw vendor log payloads or live ingested events.
Install Dt Obs Log Semantic Mapping
$ npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-log-semantic-mapping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-log-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-obs-log-semantic-mapping .claude/skills/dt-obs-log-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-obs-log-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-log-semantic-mapping into .claude/skills/dt-obs-log-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-log-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-obs-log-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-obs-log-semantic-mapping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-log-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-obs-log-semantic-mapping .agents/skills/dt-obs-log-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-obs-log-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-log-semantic-mapping into .agents/skills/dt-obs-log-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-log-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-obs-log-semantic-mapping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-log-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-obs-log-semantic-mapping .cursor/skills/dt-obs-log-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-obs-log-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-log-semantic-mapping into .cursor/skills/dt-obs-log-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-log-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-obs-log-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-obs-log-semantic-mapping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-log-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-obs-log-semantic-mapping .gemini/skills/dt-obs-log-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-obs-log-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-log-semantic-mapping into .gemini/skills/dt-obs-log-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-log-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-obs-log-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-obs-log-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-obs-log-semantic-mapping .github/skills/dt-obs-log-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-obs-log-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-log-semantic-mapping into .github/skills/dt-obs-log-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-log-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-obs-log-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-obs-log-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-obs-log-semantic-mapping .opencode/skills/dt-obs-log-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-obs-log-semantic-mapping" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-log-semantic-mapping into .opencode/skills/dt-obs-log-semantic-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-log-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.
Facts
- Skill name
dt-obs-log-semantic-mapping- GitHub stars
- 162
- Token cost
- ~966 tokens
- SKILL.md length
- 348 words
- Files
- 9 (incl. references)
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Suggest and validate semantic dictionary (SD) mappings for audit log integrations using raw vendor log payloads or live ingested events.
- : mapping a vendor audit log feed
- SKILL.md covers Purpose, Log Classes, Workflows and Key Concepts, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Authentication logs
What it does
Dt Obs Log Semantic Mapping is an agent skill from Dynatrace/dynatrace-for-ai. Suggest and validate semantic dictionary (SD) mappings for audit log integrations using raw vendor log payloads or live ingested events. Use when: mapping a vendor audit log feed, authentication logs, user activity logs to the Dynatrace SD; checking required semantic fields; proposing OpenPipeline processor extraction rules based on DQL; running runtime validation (fetches live logs by log.source, then applies static validation).
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/data-model-notes.md`, `references/mapping-workflow.md` and `references/openpipeline-constraints.md`).
It sits in Backend & APIs. It works with Okta. 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.
When your agent uses it
- : mapping a vendor audit log feed
- Authentication logs
- User activity logs to the Dynatrace SD
- Checking required semantic fields
Example prompts
- “/dt-obs-log-semantic-mapping”
What it can do on your machine
Read from SKILL.md and the folder at commit 4f9aa71. 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
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.
Network
Links to these hosts (documentation or services it may open):
docs.dynatrace.com
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
Dt Obs Log Semantic Mapping loads about 966 tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 348 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 Dynatrace/dynatrace-for-ai at commit 4f9aa71, republished under its Apache-2.0 licence (© Dynatrace). 348 words, ~966 tokens.
Download SKILL.mdSave it as
.claude/skills/dt-obs-log-semantic-mapping/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- dt-obs-log-semantic-mapping
- description
- Suggest and validate semantic dictionary (SD) mappings for audit log integrations using raw vendor log payloads or live ingested events. Use when: mapping a vendor audit log feed, authentication logs, user activity logs to the Dynatrace SD; checking required semantic fields; proposing OpenPipeline processor extraction rules based on DQL; running runtime validation (fetches live logs by log.source, then applies static validation).
- license
- Apache-2.0
dt-obs-log-semantic-mapping
Build and validate semantic-dictionary-aligned mappings for audit log integrations.
Purpose
Use this skill when a user wants to:
- Suggest a mapping from a raw vendor audit log payload to Dynatrace
fetch logsfields (Workflow A). - Validate a mapping against a pasted ingested log event (Workflow B1 — static).
- Validate against live tenant data via live tenant access (Workflow B2 — runtime: fetches logs by
log.source, then runs B1 on the result).
Log Classes
| Class | Description | Key namespaces | Example sources |
|---|---|---|---|
authentication | Login, logout, MFA, token | audit.*, actor.*, browser.*, device.* | CyberArk, Okta, Azure SignInLogs |
authorization | Access decisions, permission changes | audit.*, actor.*, object.* | CyberArk, Okta |
user_action | CRUD on platform resources | audit.*, actor.*, object.*, product.* | Okta, GitHub, Sonatype |
http | HTTP request/response (WAF, network devices) | http.*, url.*, server.*, geo.*, client.* | Akamai SIEM, Cloudflare |
Workflows
| Mode | Input | Source |
|---|---|---|
| Workflow A — Suggest mapping | Raw vendor log payload | references/mapping-workflow.md § Workflow A |
| Workflow B1 — Static validation | Pasted ingested log event | references/mapping-workflow.md § Workflow B1 |
| Workflow B2 — Runtime validation | log.source value + live tenant access | references/runtime-validation.md — fetches logs, then runs B1 |
Key Concepts
Content field burial: The primary validation concern. Fields in content (the raw vendor payload) that could be promoted to top-level semantic attributes but are not. The skill always inventories buried vs promoted fields and proposes OpenPipeline extraction rules to fix gaps.
Prerequisite: When proposing OpenPipeline processor extraction rules, load the
dt-dql-essentialsskill first. OpenPipeline processors use DQL functions (parse,fieldsAdd,splitString, etc.) — using non-DQL syntax produces invalid rules.
Sparse mappings are valid: Integrations like GitHub or Sonatype may only populate core fields. Minimum required: timestamp, log.source, content, loglevel, audit.action, audit.identity.
References
references/data-model-notes.md— Log SD field taxonomy, audit namespace, enums, sample-derived patterns and known discrepanciesreferences/mapping-workflow.md— Intake checklist, Workflow A and B1 procedures, content field analysis, field priority orderreferences/validation-rules.md— Required fields, content/enum/type rules, discrepancy severityreferences/openpipeline-constraints.md— OpenPipeline processor command/function/operator/matcher restrictions;parseJsonunavailability +parse→fieldsFlattenalternative; iterative operators for array castingreferences/report-format.md— Mapping table, diff table, OpenPipeline sketch, Validation Summary templatesreferences/runtime-validation.md— Workflow B2: fetch live records, then run B1samples/audit-logs.json— Mapped samples: CyberArk, Okta, Azure SignInLogs, Sonatype, GitHubsamples/http-logs.json— Mapped samples: Akamai SIEM (WAF/HTTP class)- Dynatrace Log Semantic Dictionary
© 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
Files
SKILL.md and 8 other files (references) in skills/dt-obs-log-semantic-mapping of Dynatrace/dynatrace-for-ai.
- SKILL.md
- references/data-model-notes.md
- references/mapping-workflow.md
- references/openpipeline-constraints.md
- references/report-format.md
- references/runtime-validation.md
- references/validation-rules.md
- samples/audit-logs.json
- samples/http-logs.json
Open the folder on GitHubat commit 4f9aa71
Compare with similar skills
Dt Obs Log 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 Obs Log Semantic Mapping this skillDynatrace/dynatrace-for-ai | 162 | — | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Frontmcp Authoritiesagentfront/frontmcp | 146 | — | ~7.1k | Automated safety check: Pass | Apache-2.0 | |
| Implementing Device Posture Assessment In Zero Trustmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Implementing Google Workspace Sso Configurationmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Implementing Scim Provisioning With Oktamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Identity Access Managementsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Implementing Device Posture Assessment In Zero Trust
mukul975/Anthropic-Cybersecurity-Skills
Implements device posture assessment as a zero trust access control by integrating endpoint health signals from CrowdStrike ZTA, Microsoft Intune, and Jamf into conditional access policies that…
Implementing Google Workspace Sso Configuration
mukul975/Anthropic-Cybersecurity-Skills
Configures SAML 2.0 single sign-on for Google Workspace against a third-party identity provider (Okta, Azure AD/Entra ID, ADFS), with Workspace as the Service Provider, to centralize authentication…
Implementing Scim Provisioning With Okta
mukul975/Anthropic-Cybersecurity-Skills
Implement automated user lifecycle provisioning and deprovisioning using the SCIM 2.0 protocol with Okta as the identity provider.
Identity Access Management
sickn33/agentic-awesome-skills
Set up and manage SSO, SCIM provisioning, and MFA for startup teams using Google Workspace, Okta, or Azure AD.
Managing Cloud Identity With Okta
mukul975/Anthropic-Cybersecurity-Skills
Implement Okta as a centralized cloud identity provider: configure SSO with AWS, Azure, and GCP, deploy phishing-resistant MFA with Okta FastPass, automate user provisioning/deprovisioning, and…
More from Dynatrace/dynatrace-for-ai
All 33 skills in this repoDt Obs Analytics
Dynatrace/dynatrace-for-ai
Analyze dashboards and notebooks using Davis analyzers — anomaly detection, novelty scoring, and correlation.
Dt Setup iOS
Dynatrace/dynatrace-for-ai
Set up the Dynatrace iOS SDK (OneAgent) in an iOS project using Swift Package Manager.
Dt Alerting
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…
Dt Obs AWS
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.
Dt Obs Ext Monitors
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 Problems
Dynatrace/dynatrace-for-ai
DAVIS problem analysis including root cause identification, impact assessment, and correlation with other telemetry.
Related
Works with
Categories
Questions about Dt Obs Log Semantic Mapping
What does Dt Obs Log Semantic Mapping do?
Suggest and validate semantic dictionary (SD) mappings for audit log integrations using raw vendor log payloads or live ingested events. Dt Obs Log Semantic Mapping is an agent skill from Dynatrace/dynatrace-for-ai. Suggest and validate semantic dictionary (SD) mappings for audit log integrations using raw vendor log payloads or live ingested events.
When should I use Dt Obs Log Semantic Mapping?
Dt Obs Log Semantic Mapping fits situations like: : mapping a vendor audit log feed; authentication logs; user activity logs to the Dynatrace SD; checking required semantic fields.
How do I install Dt Obs Log Semantic Mapping in Claude Code?
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-log-semantic-mapping -a claude-code`. Or copy the skill folder (skills/dt-obs-log-semantic-mapping in Dynatrace/dynatrace-for-ai) into .claude/skills/dt-obs-log-semantic-mapping in your project. Claude Code loads it when a task matches its description.
How do I install Dt Obs Log Semantic Mapping in Codex?
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-log-semantic-mapping -a codex`. Or copy the skill folder (skills/dt-obs-log-semantic-mapping in Dynatrace/dynatrace-for-ai) into .agents/skills/dt-obs-log-semantic-mapping in your project. Codex loads it when a task matches its description.
Can I use Dt Obs Log Semantic Mapping 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 Dynatrace/dynatrace-for-ai --skill dt-obs-log-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-obs-log-semantic-mapping, .gemini/skills/dt-obs-log-semantic-mapping, .github/skills/dt-obs-log-semantic-mapping and .opencode/skills/dt-obs-log-semantic-mapping in your project.
What does Dt Obs Log Semantic Mapping need to run?
SKILL.md names no scripts, command-line tools or credentials: Dt Obs Log Semantic Mapping is instructions for the agent only.
Does Dt Obs Log Semantic Mapping access the network?
SKILL.md names 1 domain. As links in the text: docs.dynatrace.com. This is read from the text; nothing was executed.
Is Dt Obs Log Semantic Mapping 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 Dt Obs Log Semantic Mapping use?
Dt Obs Log 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.
How many tokens does Dt Obs Log Semantic Mapping use?
About 966 tokens (SKILL.md is roughly 3.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 12k tokens, read only when the agent opens those files.
What are the alternatives to Dt Obs Log Semantic Mapping?
Skills that share tags, products or a category with Dt Obs Log Semantic Mapping: Frontmcp Authorities (agentfront/frontmcp, 146 stars), Implementing Device Posture Assessment In Zero Trust (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Implementing Google Workspace Sso Configuration (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Implementing Scim Provisioning With Okta (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dt Obs Log Semantic Mapping?
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.