New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Topology Authoring

by netdata in netdata/netdata

Design, change or review Netdata topology producers and netdata.topology.v1 payloads, including actors, links, evidence, correlation, presentation, modals, overlays and validators.

GPL-3.0Auto-check passedDevOps & Cloud

Install Topology Authoring

skills CLI
$ npx skills add netdata/netdata --skill topology-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install netdata/netdata topology-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/netdata/netdata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/topology-authoring .claude/skills/topology-authoring && rm -rf skills-src

Use ~/.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/

Facts

Skill name
topology-authoring
GitHub stars
81k
Token cost
~3.9k tokens
SKILL.md length
1,458 words
Files
4
Skills in repo
27
Repo updated
First seen
Licence
GPL-3.0

At a glance

Design, change or review Netdata topology producers and netdata.topology.v1 payloads, including actors, links, evidence, correlation, presentation, modals, overlays and validators.

  • Works in 11 steps: Purpose and scale: name the graph users… → Actors: stable identity, display… → Links and direction: compact renderable… → …
  • DevOps & Cloud work in your project
  • SKILL.md covers Owners, Producers, What The Code Enforces and Workflow, plus 2 more sections
  • Calls cmake

What it does

Topology Authoring is an agent skill from netdata/netdata. Design, change or review Netdata topology producers and netdata.topology.v1 payloads, including actors, links, evidence, correlation, presentation, modals, overlays and validators. Operator topology queries use query skills; SNMP profile topology rows use collectors-snmp-profiles.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `how-tos/add-graph-presentation.md`, `how-tos/preserve-semantic-link-types.md` and `how-tos/verify-network-connections-layout-tokens.md`).

It sits in DevOps & Cloud. The repository describes itself as: The fastest path to AI-powered full stack observability, even for lean teams. The licence is GPL-3.0.

When your agent uses it

  • DevOps & Cloud work in your project

Example prompts

  • “/topology-authoring”

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Purpose and scale: name the graph users need, choose which plane carries what, and estimate actor, link, and
  2. Actors: stable identity, display separate from identity, identity / merge_identity / parent_identity,
  3. Links and direction: compact renderable relationships, one-to-many detail in evidence, semantic link types per
  4. Evidence and tables: lossless relationship proof versus actor-owned detail, table roles, actor_labels.
  5. Overlays: templates once, compact refs per row.
  6. Correlation: rule classes, actions, points and claims, and what the aggregator does with them.
  7. Presentation and modals: type-level tokens only, label_policy, ports.sources[], highlight paths, modal
  8. Compact tables: const / dict / values codecs.
  9. Notifications, if any: data.notifications only, origin kept separate from affected_node_id, CTS acceptance
  10. Per-producer contract.
  11. Validate and measure: schema plus semantic validation in tests, the producer's own suites (table above), size

What it can do on your machine

Read from SKILL.md and the folder at commit 2c378f0. 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

    Shell commands in SKILL.md call:

    • cmake

    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

Topology Authoring loads about 3.9k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 1,458 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

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 netdata/netdata at commit 2c378f0, republished under its GPL-3.0 licence (© netdata). 1,458 words, ~3,894 tokens.

Download SKILL.mdSave it as .claude/skills/topology-authoring/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
topology-authoring
description
Design, change or review Netdata topology producers and netdata.topology.v1 payloads, including actors, links, evidence, correlation, presentation, modals, overlays and validators. Operator topology queries use query skills; SNMP profile topology rows use collectors-snmp-profiles.

Topology Producers

Developer skill for assistants working in this repository, not an operator skill. It routes to the documents that own each fact and keeps only the rules and workflow that have no other owner. When you find a fact here and in an owner document, verify the affected contract at its source and correct stale guidance during authorized maintenance.

Apply AGENTS.md#skill-selection. Review the affected planes and existing design/validation evidence; authoring steps below do not require reviewers to create a SOW, redesign unrelated planes or query a live Agent. Live verification recipes apply only when the task includes that operation. A changed validator requires checking the claims it affects.

Owners

Read the owner for the plane you touch; do not work from memory of it.

OwnerOwns
src/plugins.d/FUNCTION_TOPOLOGY_SCHEMA.jsonEvery required field and closed token (icons, colors, layout, cell types, visibility, projections, arrow, direction, severities, rule classes). Named record definitions are additionalProperties: false; the type registries, evidence, scale_keys, correlation.rules, and the maps under data.tables.actor / .relationship are maps keyed by producer-chosen ids (propertyNames = id); dictionaries, stats, extensions, badge_map, and link_aggregation.metrics are open maps; required_params[] items are objects with no further constraint.
src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.mdThe payload contract, plane by plane, plus per-producer Shape sections and the aggregator rules a producer relies on.
src/plugins.d/FUNCTION_TOPOLOGY_IMPLEMENTATION_SCOPE.mdMigration state per producer, Cloud aggregator and frontend scope, the CTS gate, and design that is not yet in the schema.
src/go/pkg/topology/v1Go builders and the semantic validator (validate.go, validate_notification.go).
src/go/plugin/go.d/collector/snmp_topology/ARCHITECTURE.mdSNMP producer internals, where to change what, and its validation commands.
src/go/pkg/l2topology/parity/README.mdThe L2 parity runbook against the enlinkd oracle.
src/go/tools/functions-validation/README.md#validate-topology-v1-fixturesValidating any topology payload file from the CLI.
src/plugins.d/FUNCTION_UI_REFERENCE.md, src/plugins.d/FUNCTION_UI_DEVELOPER_GUIDE.mdFunction transport: envelope, v: 3, selections, info responses.
docs/npm/topology/What operators are told the topology means. Change it when a user-visible meaning changes.

If the task also changes or reviews the collector that hosts the producer, .agents/skills/collectors-authoring/SKILL.md routes that work. SNMP profile topology: rows (which OIDs feed the producer) belong to collectors-snmp-profiles; this skill starts where those rows have become observations.

Producers

FunctionProducerTests
topology:network-connectionssrc/collectors/network-viewer.plugin/network-viewer-topology.c (shared renderer; Windows main in network-viewer-windows.c, container rules in network-viewer-topology-containers.c)src/collectors/network-viewer.plugin/tests/validate_topology_payload.py, validate_topology_container_fixtures.py, the C unit tests test_network_viewer_topology_containers.c and test_network_viewer_apps_lookup_client.c, and fixtures under tests/fixtures/topology/ (all under src/collectors/network-viewer.plugin/tests/)
topology:streamingsrc/web/api/functions/function-topology-streaming.c (path facts from src/streaming/stream-path.c)no producer-level test; src/go/tools/functions-validation/fixtures/topology-v1/streaming.json is a hand-authored schema sample that does not mirror the emitted shape
topology:snmpsrc/go/plugin/go.d/collector/snmp_topology/ (render in internal/topologyv1)topology_scenario_golden_test.go, internal/topologyv1/golden_test.go, see src/go/plugin/go.d/collector/snmp_topology/ARCHITECTURE.md#validation-checklist
topology:vspheresrc/go/plugin/go.d/collector/vsphere/func_topology*.gofunc_topology_test.go
topology:cato_networkssrc/go/plugin/go.d/collector/cato_networks/topology.go, catofunc/topology.gotopology_test.go

All five emit netdata.topology.v1; no producer still emits a pre-v1 payload. Remaining per-producer refinements are tracked in src/plugins.d/FUNCTION_TOPOLOGY_IMPLEMENTATION_SCOPE.md#current-migration-inventory. Cross-producer fixtures live in src/go/tools/functions-validation/fixtures/topology-v1/ (none for topology:cato_networks); the Cloud aggregator itself is not in this repository.

What The Code Enforces

Use this map to locate enforcement and its known limits. Before relying on a claim affected by the task, verify it in the current schema, validator and relevant tests. Do not re-audit unrelated behavior or infer enforcement from this summary alone; distinguish intended contract from what the checked implementation actually rejects.

  • JSON Schema (FUNCTION_TOPOLOGY_SCHEMA.json): structure, required fields, closed tokens, unknown properties. A violation is an error from any validator that loads the schema. It does not check cross-references or row counts.
  • Go semantic validator (topologyv1.ValidateDecodedData on data, topologyv1.ValidateDecodedResponse on a whole envelope; both return an error, there is no warning level): actor and link reference bounds (evidence references only where the table type declares source_evidence), column-length equality with rows, dictionary indexes, label-policy display types, search columns and label-key shape independently of optional actor presentation, declared actor aggregation-scope memberships, the ports.sources[] rules except the actor_table carve-out below (and show_bullets is read untyped, so only the schema rejects a non-boolean), highlight-path column types (including that a path_table not under data.tables.actor is owned by actor, the one use the validator makes of table_type.owner), every overlay-refs convention rule except the id-pattern rule (schema-only), correlation rules and point/claim key columns, all modal projections, and the presentation, correlation, and overlay token vocabularies. Structural tokens (orientation, direction_role, link_type.aggregation.*, evidence_type.role, table_type.role and aggregation, column.role, layer, view.mode, supported_modes, evidence_policy) are schema-only; the Go validator never reads them. Producer tests call ValidateDecodedData (cato_networks/topology_test.go is the reference shape). The CLI tool always validates against one JSON Schema first, defaulting to FUNCTION_UI_SCHEMA.json, which rejects a topology payload, so a topology run passes --schema ../plugins.d/FUNCTION_TOPOLOGY_SCHEMA.json from src/go (src/go/tools/functions-validation/README.md#validate-topology-v1-fixtures); it then calls ValidateDecodedResponse.
  • Go builders (Table.Validate) and the decoded semantic validator enforce scalar numeric validity, typed-set member types, and nullability as errors across the compact-table codecs. Contract: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#compact-tables; validation workflow: src/go/tools/functions-validation/README.md#validate-topology-v1-fixtures.
  • The CLI tool (src/go/tools/functions-validation) counts a topology payload's rows as max(actor rows, link rows) (topologyv1.GraphRowsFromDecodedData) for its --min-rows and --require-rows gates, so an actor-only payload passes; nothing in pkg/topology caps row counts.
  • Not checked by the Go validator although the contract states them: actor_labels key, value, source, and kind column types (only actor_column is type-checked), search.label_keys[] against any label registry (string shape only), correlation key_space values (schema-required, never read), unknown optional column ids on actor_table port sources, and the owner of a detail table named as an actor_table source by port bullets, modal sections, or modal labels (a link- or evidence-owned table is accepted there).
  • The network-connections 64 MiB budget is a producer-side hard stop (a 413 Function error), not a validator check (src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#network-connections-shape).
  • The SNMP scenario golden suite skips, not fails, without the external fixture checkout (src/go/plugin/go.d/collector/snmp_topology/ARCHITECTURE.md#scenario-golden-suite). A green run without the skip line checked proves nothing.
  • Nothing enforces: payload size on realistic data, actor identity stability across restarts, that a modal section is a recipe rather than a duplicated table, or that a type id follows the semantic conventions. Those are review items.
Show full SKILL.md (535 more words)Show less

Workflow

Select the steps for the affected planes; a new producer considers every applicable plane. Implementation reads its owners before design, while review checks the resulting contracts and evidence. Guide means src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md.

  1. Purpose and scale: name the graph users need, choose which plane carries what, and estimate actor, link, and evidence row counts and raw payload size on realistic data before choosing shapes. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#mental-model (planes), src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#producer-checklist (measure on realistic or captured fixtures).
  2. Actors: stable identity, display separate from identity, identity / merge_identity / parent_identity, search, and the aggregation scopes an actor type advertises. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#required-actor-semantics; scopes and grouping: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#aggregation-rules, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#network-connections-actor-grouping.
  3. Links and direction: compact renderable relationships, one-to-many detail in evidence, semantic link types per meaning, orientation plus direction_role. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#required-link-semantics.
  4. Evidence and tables: lossless relationship proof versus actor-owned detail, table roles, actor_labels. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#evidence-plane, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#detail-tables, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#actor-labels-and-modal-composition.
  5. Overlays: templates once, compact refs per row. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#telemetry-overlays. Go builders: topologyv1.NewActorOverlayRefsBuilder, NewLinkOverlayRefsBuilder (src/go/pkg/topology/v1); in go.d pass job.Name() as collect_job, never job.FullName() (src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#vsphere-shape).
  6. Correlation: rule classes, actions, points and claims, and what the aggregator does with them. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#correlation-plane, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#aggregator-behavior.
  7. Presentation and modals: type-level tokens only, label_policy, ports.sources[], highlight paths, modal recipes over existing sources; recipes in how-tos/add-graph-presentation.md. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#presentation-plane, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#closed-token-vocabulary, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#actor-labels-and-modal-composition.
  8. Compact tables: const / dict / values codecs. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#compact-tables. Go builders: topologyv1.NewTableBuilder, MustTable, NewStringDictionary (src/go/pkg/topology/v1).
  9. Notifications, if any: data.notifications only, origin kept separate from affected_node_id, CTS acceptance verified before Agents emit. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#notifications.
  10. Per-producer contract. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#network-connections-shape, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#streaming-shape and src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#streaming-modal-sections, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#snmpl2-shape and src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#snmp-logical-l3-and-control-plane-links, src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#vsphere-shape.
  11. Validate and measure: schema plus semantic validation in tests, the producer's own suites (table above), size on realistic data, and the checklist. Guide: src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#producer-checklist.

Rules Without A Code Owner

  • Raw captures of real payloads stay under .local/ (repository rule, AGENTS.md). actor_labels inherits the Function's sensitive-data classification (src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#actor-labels-and-modal-composition); streaming detail tables carry node and Cloud identifiers that never become graph labels and are redacted before they reach logs, docs, SOWs, or review artifacts (src/plugins.d/FUNCTION_TOPOLOGY_DEVELOPER_GUIDE.md#streaming-shape).
  • Sparse grouping columns: test that a consumer keeps actor identity for null or empty grouping keys instead of merging every null row into one bucket.
  • Fail explicitly on any size or row limit; never truncate a topology and present it as complete.
  • Validators need negative tests: missing label-policy columns, non-display label columns, a missing port-bullet source table, bad highlight-path columns, an invalid token, and a modal projection over a missing source. A producer that emits data.notifications tests schema and semantic parity, omission of the field, and malformed entries.
  • A C producer can be syntax-checked without a full build: configure with cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON, then run the file's command from build/compile_commands.json with -fsyntax-only.
  • Design the schema does not carry yet (four-dimension table merge policy, loose-side materialization) is recorded in src/plugins.d/FUNCTION_TOPOLOGY_IMPLEMENTATION_SCOPE.md#design-not-yet-in-the-schema; do not emit it and do not document it as contract.

How-Tos

  • how-tos/add-graph-presentation.md: add type-level presentation, port bullets, legends, and per-actor highlight paths to a producer, with the negative tests that catch the usual mistakes.
  • how-tos/preserve-semantic-link-types.md: keep protocol, confidence, and inferred state as distinct link types.
  • how-tos/verify-network-connections-layout-tokens.md: check a live local Agent's link layout tokens and correlation wiring without exposing identifiers.

Capture timing and authorization follow AGENTS.md#knowledge-capture. Authorized developer recipes stay in this skill and are listed above; operator recipes belong under docs/netdata-ai/skills/.

© netdata, GPL-3.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 in .agents/skills/topology-authoring of netdata/netdata.

  • SKILL.md
  • how-tos/add-graph-presentation.md
  • how-tos/preserve-semantic-link-types.md
  • how-tos/verify-network-connections-layout-tokens.md

Open the folder on GitHubat commit 2c378f0

Compare with similar skills

Topology Authoring 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.

Topology Authoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Topology Authoring this skillnetdata/netdata81k—~3.9kAutomated safety check: PassGPL-3.0
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw35k6 repos~4.2kAutomated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k9 repos~4.3kAutomated safety check: PassNone
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed

  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    35k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed

  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 9 repos~4.3k tokens
    DevOps & CloudAuto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Analyze GitHub Action Logs

    withastro/astro

    Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed

  • KubeSphere Multi-Tenant Management

    kubesphere/kubesphere

    Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.

    17k GitHub starsUsed in 1 repo~3.1k tokens
    DevOps & CloudAuto-check passed

More from netdata/netdata

All 27 skills in this repo

  • Docs Learn PR Preview

    netdata/netdata

    Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.

    81k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Repo Mirror Sources

    netdata/netdata

    Inspect Netdata-org source checkouts under NETDATAREPOSDIR, or set up and synchronize that mirror when requested.

    81k GitHub stars~1.2k tokensUpdated today
    Auto-check: notes

  • Triage Agent Events

    netdata/netdata

    Investigate Netdata crashes, panics and fatals from agent-events captures or authorized fleet queries.

    81k GitHub stars~2.4k tokensUpdated today
    Auto-check: notes

  • Triage Codacy

    netdata/netdata

    Inspect, analyze, troubleshoot, or review Codacy findings and local analyzer/API helpers.

    81k GitHub stars~2.2k tokensUpdated today
    Auto-check: notes

  • Triage Coverity

    netdata/netdata

    Inspect or review Coverity Scan defects and saved CID bundles; fetch live findings or apply verified triage decisions when requested.

    81k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Triage Sonarqube

    netdata/netdata

    Inspect, review, or apply authorized triage decisions to SonarCloud issues and security hotspots; also review the Sonar helpers.

    81k GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

Categories

Questions about Topology Authoring

What does Topology Authoring do?

Design, change or review Netdata topology producers and netdata.topology.v1 payloads, including actors, links, evidence, correlation, presentation, modals, overlays and validators. Topology Authoring is an agent skill from netdata/netdata.v1 payloads, including actors, links, evidence, correlation, presentation, modals, overlays and validators.

When should I use Topology Authoring?

Topology Authoring fits situations like: devOps & Cloud work in your project.

How do I install Topology Authoring in Claude Code?

Run `npx skills add netdata/netdata --skill topology-authoring -a claude-code`. Or copy the skill folder (.agents/skills/topology-authoring in netdata/netdata) into .claude/skills/topology-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Topology Authoring in Codex?

Run `npx skills add netdata/netdata --skill topology-authoring -a codex`. Or copy the skill folder (.agents/skills/topology-authoring in netdata/netdata) into .agents/skills/topology-authoring in your project. Codex loads it when a task matches its description.

Can I use Topology Authoring 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 netdata/netdata --skill topology-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topology-authoring, .gemini/skills/topology-authoring, .github/skills/topology-authoring and .opencode/skills/topology-authoring in your project.

What does Topology Authoring need to run?

Going by SKILL.md and its folder, Topology Authoring needs the command-line tools its instructions call (cmake).

Does Topology Authoring 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 Topology Authoring 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 Topology Authoring use?

Topology Authoring is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Topology Authoring use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Topology Authoring?

Skills that share tags, products or a category with Topology Authoring: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Topology Authoring?

netdata (a GitHub organization) maintains it in netdata/netdata, which has 80,838 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 8, 2026.

Source: netdata/netdata on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.