Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
Analyze SNMP-monitored network devices (switches, routers, firewalls, load balancers) in Dynatrace.
Install Dt Obs Network Devices
$ npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-network-devices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-network-devices --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-network-devices .claude/skills/dt-obs-network-devices && 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-network-devices" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-devices into .claude/skills/dt-obs-network-devices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-network-devices", 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-network-devicesType 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-network-devices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-network-devices --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-network-devices .agents/skills/dt-obs-network-devices && 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-network-devices" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-devices into .agents/skills/dt-obs-network-devices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-network-devices", 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-network-devices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-network-devices --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-network-devices .cursor/skills/dt-obs-network-devices && 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-network-devices" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-devices into .cursor/skills/dt-obs-network-devices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-network-devices", 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-network-devices--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-network-devices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dynatrace/dynatrace-for-ai dt-obs-network-devices --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-network-devices .gemini/skills/dt-obs-network-devices && 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-network-devices" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-devices into .gemini/skills/dt-obs-network-devices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-network-devices", 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-network-devicesInstalls 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-network-devices -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-network-devices .github/skills/dt-obs-network-devices && 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-network-devices" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-devices into .github/skills/dt-obs-network-devices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-network-devices", 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-network-devices -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-network-devices --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-network-devices .opencode/skills/dt-obs-network-devices && 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-network-devices" agent skill from https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-devices into .opencode/skills/dt-obs-network-devices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dt-obs-network-devices", 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-network-devices- GitHub stars
- 163
- Token cost
- ~2.1k tokens
- SKILL.md length
- 811 words
- Files
- 4 (incl. references)
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyze SNMP-monitored network devices (switches, routers, firewalls, load balancers) in Dynatrace.
- Works in 4 steps: Inventory, attributes, or topology (list… → Health or performance (CPU, memory,… → Event-driven signals (SNMP traps, syslog… → …
- Inventory devices
- SKILL.md covers What Network Device Monitoring…, The Three Layers (and how they…, Monitoring Mode Determines… and Routing, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dt Obs Network Devices is an agent skill from Dynatrace/dynatrace-for-ai. Analyze SNMP-monitored network devices (switches, routers, firewalls, load balancers) in Dynatrace. Three data layers: Smartscape topology (EXTNETWORKDEVICE / EXTNETWORKINTERFACE nodes, belongsto and calls edges); com.dynatrace.extension.networkdevice. metrics (CPU, memory, uptime, throughput, saturation, errors); and logs (SNMP traps, syslog, auto-discovery). Use to inventory devices, find down or saturated interfaces, check device CPU/memory/uptime, map topology and neighbors, detect interface errors, and…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/logs.md`, `references/metrics.md` and `references/topology-model.md`).
It sits in DevOps & Cloud, covering Cloud networking. 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
- Inventory devices
- Saturated interfaces
- Check device CPU/memory/uptime
- Map topology and neighbors
Example prompts
- “network device”
- “switch”
- “router”
- “/dt-obs-network-devices”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Inventory, attributes, or topology (list devices, find a device's interfaces, map neighbors, read model/firmware/location) →…
- Health or performance (CPU, memory, uptime, interface up/down, throughput, saturation, errors) → references/metrics.md.
- Event-driven signals (SNMP traps, syslog messages, discovery activity) → references/logs.md.
- Most real questions combine layers (e.g. "which interfaces on the core router are down" = metric status filtered to one device, joined to…
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
No URLs in SKILL.md.
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 Network Devices loads about 2.1k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 253 tokens; SKILL.md has 811 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). 811 words, ~2,112 tokens.
Download SKILL.mdSave it as
.claude/skills/dt-obs-network-devices/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- dt-obs-network-devices
- description
- Analyze SNMP-monitored network devices (switches, routers, firewalls, load balancers) in Dynatrace. Three data layers: Smartscape topology (`EXT_NETWORK_DEVICE` / `EXT_NETWORK_INTERFACE` nodes, `belongs_to` and `calls` edges); `com.dynatrace.extension.network_device.*` metrics (CPU, memory, uptime, throughput, saturation, errors); and logs (SNMP traps, syslog, auto-discovery). Use to inventory devices, find down or saturated interfaces, check device CPU/memory/uptime, map topology and neighbors, detect interface errors, and investigate traps and syslog events. Trigger: "network device", "switch", "router", "firewall", "SNMP", "interface status", "interface down", "interface utilization", "link saturation", "device CPU", "device memory", "device uptime", "device neighbors", "LLDP", "CDP", "SNMP trap", "syslog". Do NOT use for network flow/traffic or top talkers (use dt-obs-network-flows), host NIC throughput (use dt-obs-hosts), or service request/latency (use dt-obs-services).
- license
- Apache-2.0
Network Devices Skill
Analyze SNMP-monitored network infrastructure in Dynatrace — switches, routers, firewalls, load balancers, access points, and any other device polled by a network device extension (the SNMP-generic and vendor SNMP extensions). This skill covers the device and interface data model and routes each question to the right reference file. All DQL lives in the reference files and was validated against a live tenant with dtctl query.
What Network Device Monitoring Tells You
SNMP extensions poll network hardware and expose it in Dynatrace as three layers:
- Topology — an inventory of devices and their interfaces as Smartscape nodes (
EXT_NETWORK_DEVICE,EXT_NETWORK_INTERFACE), with attributes (vendor, model, OS/firmware, location, contact, IPs, MACs, link speed) and relationships (which interface belongs to which device; which devices are neighbors via LLDP/CDP). - Metrics — time series for device health (CPU, memory, uptime) and per-interface health (operational/admin status, in/out throughput, errors, discards, packet mix), under the
com.dynatrace.extension.network_device.*namespace. - Logs — event-driven records: SNMP traps (link-up/down, hardware faults), syslog messages (config changes, authentication, interface events), and auto-discovery activity (devices and neighbors found per poll cycle).
This answers questions such as: Which interfaces are down? Which links are saturated? Is this router's CPU pegged? Which devices rebooted? What is connected to this switch? What traps has this device sent? What syslog errors are recurring?
The Three Layers (and how they join)
| Layer | Query with | Grain | Key fields |
|---|---|---|---|
| Topology | smartscapeNodes "EXT_NETWORK_DEVICE" / smartscapeNodes "EXT_NETWORK_INTERFACE" | One row per device / interface (current inventory) | id, name, monitoring_mode, device_type, location, ip, speed, edges via belongs_to / calls |
| Metrics | timeseries … com.dynatrace.extension.network_device.* | Time series per device / interface | grouped by dt.smartscape.ext_network_device and (interface metrics) dt.smartscape.ext_network_interface |
| Logs | fetch logs | filter dt.openpipeline.source == "…" | Individual log records (traps, syslog, discovery) | joined to topology by expanding the device ip[] array and matching device.address / dt.ingest.source.ip — see references/logs.md |
The join key is the Smartscape ID. Every metric carries a dt.smartscape.ext_network_device dimension (and interface metrics also carry dt.smartscape.ext_network_interface). Use lookup [smartscapeNodes …] to attach human-readable device/interface names to metric results, and to attach live metrics to an inventory listing. Both reference files show this pattern.
Monitoring Mode Determines What Data Exists
Every device has a monitoring_mode. This is the first thing to check — it decides whether metrics exist at all:
monitoring_mode | Meaning | Has metrics? | Has full attributes? |
|---|---|---|---|
Extension | Directly polled by an SNMP extension | Yes — full com.dynatrace.extension.network_device.* set | Yes |
Discovery | Discovered on the network but not directly polled | No | Partial |
Neighbor | Known only because a polled device names it as an LLDP/CDP neighbor | No | Minimal (name, chassis MAC) |
If a device has no metrics, check its
monitoring_modebefore assuming a data gap — onlyExtension-mode devices are polled. When listing "monitored devices," excludeNeighbor(and usuallyDiscovery).
Routing
- Inventory, attributes, or topology (list devices, find a device's interfaces, map neighbors, read model/firmware/location) → references/topology-model.md.
- Health or performance (CPU, memory, uptime, interface up/down, throughput, saturation, errors) → references/metrics.md.
- Event-driven signals (SNMP traps, syslog messages, discovery activity) → references/logs.md.
- Most real questions combine layers (e.g. "which interfaces on the core router are down" = metric status filtered to one device, joined to interface names). The metrics and logs references show these joined queries.
Show full SKILL.md (303 more words)Show less
Related Skills
Network device monitoring is one part of Dynatrace network observability. Route elsewhere when the question is not about device/interface health or topology:
| The user wants… | Use |
|---|---|
| Traffic between entities, top talkers, conversations, connection health (the flows through the network) | dt-obs-network-flows — including NetFlow/IPFIX/sFlow that these same devices export |
| Host NIC throughput / packet drops on OneAgent-monitored hosts (not SNMP devices) | dt-obs-hosts → references/host-metrics.md |
| Service request rate, latency, error rate | dt-obs-services |
| Setting up or configuring an extension (this skill covers the resulting data model, not extension authoring) | dt-obs-extensions |
General Smartscape traversal syntax (traverse, smartscapeEdges, references[…]) | dt-dql-essentials |
Network devices vs. network flows. This skill answers "what is the state of the box and its ports" (SNMP device/interface health and topology).
dt-obs-network-flowsanswers "what traffic is crossing the network" (conversations, bytes, talkers). The same router appears in both: here as anEXT_NETWORK_DEVICEwith interface counters, there as a NetFlow exporter. A future macrodt-obs-networkskill may unify them; until then, cross-link.
Reference Files
- references/topology-model.md — Validated. The Smartscape model:
EXT_NETWORK_DEVICEandEXT_NETWORK_INTERFACEnode types with full field reference, monitoring modes, and thebelongs_to/callsedges. DQL for device inventory (with filtering by mode/type/location/vendor), listing a device's interfaces, resolving an interface to its device, and mapping device/interface neighbor topology. - references/metrics.md — Validated. The
com.dynatrace.extension.network_device.*metric catalog with units, dimensions, and field-typing rules. DQL for device health (top CPU, memory % with fallback, uptime and reboot detection) and interface health (down interfaces, throughput and saturation vs. link speed, error/discard counts, per-device interface detail), each joined to device/interface names. - references/logs.md — Validated. The three log sources: SNMP traps (
extension:com.dynatrace.extension.snmp-traps-generic), syslog (extension:syslog), and auto-discovery activity (extension:com.dynatrace.extension.snmp-auto-discovery). Covers the IP-to-Smartscape join pattern (device.address/dt.ingest.source.ip→snmp.ip), field references for all three sources, and DQL for recent traps with device names, trap frequency by OID, error syslog, top event patterns, combined per-device view, and LLDP/CDP neighbor discovery logs.
© 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 3 other files (references) in skills/dt-obs-network-devices of Dynatrace/dynatrace-for-ai.
- SKILL.md
- references/logs.md
- references/metrics.md
- references/topology-model.md
Open the folder on GitHubat commit 4f9aa71
Compare with similar skills
Dt Obs Network Devices 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 Network Devices this skillDynatrace/dynatrace-for-ai | 163 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Nginx To Higress Migrationhigress-group/higress | 9.5k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Bfe Rd Workflowbfenetworks/bfe | 6.3k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress | 5.1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| NGINX Ingress Policy CRD Guidenginx/kubernetes-ingress | 5.1k | — | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Nginx To Higress Migration
higress-group/higress
Migrate from ingress-nginx to Higress in Kubernetes environments.
Bfe Rd Workflow
bfenetworks/bfe
引导用户在 bfe 代码库中完成一次完整的功能研发流程，包括需求对齐、文档修改、代码实现、集成测试与回归验证. An agent skill from bfenetworks/bfe.
NGINX Ingress Controller Feature Checklists
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
NGINX Ingress Policy CRD Guide
nginx/kubernetes-ingress
Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.
ArvanCloud API Operator
erfnzdeh/arvancloud-agent-skill
Drives ArvanCloud's REST APIs for CDN, DNS, cloud servers, object storage and more, with helper scripts for calls, account inventory and certificates.
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
Categories
Questions about Dt Obs Network Devices
What does Dt Obs Network Devices do?
Analyze SNMP-monitored network devices (switches, routers, firewalls, load balancers) in Dynatrace. Dt Obs Network Devices is an agent skill from Dynatrace/dynatrace-for-ai. Analyze SNMP-monitored network devices (switches, routers, firewalls, load balancers) in Dynatrace.
When should I use Dt Obs Network Devices?
Dt Obs Network Devices fits situations like: inventory devices; saturated interfaces; check device CPU/memory/uptime; map topology and neighbors.
How do I install Dt Obs Network Devices in Claude Code?
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-network-devices -a claude-code`. Or copy the skill folder (skills/dt-obs-network-devices in Dynatrace/dynatrace-for-ai) into .claude/skills/dt-obs-network-devices in your project. Claude Code loads it when a task matches its description.
How do I install Dt Obs Network Devices in Codex?
Run `npx skills add Dynatrace/dynatrace-for-ai --skill dt-obs-network-devices -a codex`. Or copy the skill folder (skills/dt-obs-network-devices in Dynatrace/dynatrace-for-ai) into .agents/skills/dt-obs-network-devices in your project. Codex loads it when a task matches its description.
Can I use Dt Obs Network Devices 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-network-devices -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-network-devices, .gemini/skills/dt-obs-network-devices, .github/skills/dt-obs-network-devices and .opencode/skills/dt-obs-network-devices in your project.
What does Dt Obs Network Devices need to run?
SKILL.md names no scripts, command-line tools or credentials: Dt Obs Network Devices is instructions for the agent only.
Does Dt Obs Network Devices access the network?
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.
Is Dt Obs Network Devices 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 Network Devices use?
Dt Obs Network Devices 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 Network Devices use?
About 2.1k tokens (SKILL.md is roughly 8.4k 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 9k tokens, read only when the agent opens those files.
What are the alternatives to Dt Obs Network Devices?
Skills that share tags, products or a category with Dt Obs Network Devices: Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars), Nginx To Higress Migration (higress-group/higress, 9.5k stars), Bfe Rd Workflow (bfenetworks/bfe, 6.3k stars) and NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dt Obs Network Devices?
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.