OmniRoute Backup and Sync CLI
diegosouzapw/OmniRoute
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery.
Install Integrations Lifecycle
$ npx skills add netdata/netdata --skill integrations-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install netdata/netdata integrations-lifecycle --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/netdata/netdata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/integrations-lifecycle .claude/skills/integrations-lifecycle && 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 "integrations-lifecycle" agent skill from https://github.com/netdata/netdata/tree/master/.agents/skills/integrations-lifecycle into .claude/skills/integrations-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations-lifecycle", 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/netdata/netdata/tree/master/.agents/skills/integrations-lifecycleType 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 netdata/netdata --skill integrations-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install netdata/netdata integrations-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/netdata/netdata.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/integrations-lifecycle .agents/skills/integrations-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "integrations-lifecycle" agent skill from https://github.com/netdata/netdata/tree/master/.agents/skills/integrations-lifecycle into .agents/skills/integrations-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations-lifecycle", 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 netdata/netdata --skill integrations-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install netdata/netdata integrations-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/netdata/netdata.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/integrations-lifecycle .cursor/skills/integrations-lifecycle && 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 "integrations-lifecycle" agent skill from https://github.com/netdata/netdata/tree/master/.agents/skills/integrations-lifecycle into .cursor/skills/integrations-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations-lifecycle", 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/netdata/netdata.git --path .agents/skills/integrations-lifecycle--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 netdata/netdata --skill integrations-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install netdata/netdata integrations-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/netdata/netdata.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/integrations-lifecycle .gemini/skills/integrations-lifecycle && 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 "integrations-lifecycle" agent skill from https://github.com/netdata/netdata/tree/master/.agents/skills/integrations-lifecycle into .gemini/skills/integrations-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations-lifecycle", 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 netdata/netdata integrations-lifecycleInstalls 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 netdata/netdata --skill integrations-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/netdata/netdata.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/integrations-lifecycle .github/skills/integrations-lifecycle && 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 "integrations-lifecycle" agent skill from https://github.com/netdata/netdata/tree/master/.agents/skills/integrations-lifecycle into .github/skills/integrations-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations-lifecycle", 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 netdata/netdata --skill integrations-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install netdata/netdata integrations-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/netdata/netdata.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/integrations-lifecycle .opencode/skills/integrations-lifecycle && 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 "integrations-lifecycle" agent skill from https://github.com/netdata/netdata/tree/master/.agents/skills/integrations-lifecycle into .opencode/skills/integrations-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations-lifecycle", 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
integrations-lifecycle- GitHub stars
- 81k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 549 words
- Files
- 18
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery.
- DevOps & Cloud work in your project
- SKILL.md covers You edit metadata or a…, You change the generators,…, Live how-to rule and Path discipline, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Integrations Lifecycle is an agent skill from netdata/netdata. Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery. Covers ibm.d and NPM producers, schemas, generators and dormant taxonomy. Metadata field prose uses collectors-metadata-yaml.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files (for example `consistency.md`, `description-authoring.md` and `gotchas.md`).
It sits in DevOps & Cloud. It works with npm. 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
- “/integrations-lifecycle”
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
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
Integrations Lifecycle loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 549 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 netdata/netdata at commit 2c378f0, republished under its GPL-3.0 licence (© netdata). 549 words, ~1,260 tokens.
Download SKILL.mdSave it as
.claude/skills/integrations-lifecycle/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.- name
- integrations-lifecycle
- description
- Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery. Covers ibm.d and NPM producers, schemas, generators and dormant taxonomy. Metadata field prose uses collectors-metadata-yaml.
integrations-lifecycle
The pipeline that turns source metadata into the integration pages, the umbrella pages, and the in-app catalog. This
skill owns the mechanics and the delivery rules; what a collector metadata.yaml field should say is
.agents/skills/collectors-metadata-yaml/, and config_schema.json is
.agents/skills/collectors-go-design/config-schema.md.
Apply AGENTS.md#skill-selection. For review, select the affected pipeline or artifact contract below and inspect
source plus existing validation evidence. Loading recipes does not require regeneration, dependency installation,
commits or publication. Authorized validation uses current inputs and preserves existing outputs through isolation.
Shared delivery facts:
metadata.yamlis the input. Hand-authored for most integrations; generated for ibm.d modules (fromcontexts.yaml,config.go,module.yaml) and for the NPM catalog (from SNMP profiles byintegrations/gen_npm_catalog.py). Edit the authoritative source, never a generated file.- Every
<dir>/integrations/<slug>.md, every README that is a symlink or whose<!--startmetablock carries amessage: "DO NOT EDIT..."line (a<!--startmetablock alone is not the marker; hand-authored Learn pages have one too), and the umbrella pagessrc/collectors/COLLECTORS.md,SECRETS.md,SERVICE-DISCOVERY.md(no banner) are generated. Do not edit them. - Source PRs carry sources; generated documentation arrives through the post-merge
integrations-regenPR. Validate withgen_integrations.pyand the tests during authorized changes; preview pages in isolation usinghow-tos/preview-collector-page.md(selected collectors or its non-collector route). Preserve existing generated-file edits and keep them out of the source commit. The one place this boundary is written out, with its ibm.d runtime-output exception, isconsistency.md. - The collector taxonomy (
taxonomy.yaml,gen_taxonomy.py) is a dormant early implementation kept for later work; nothing runs it. Do not author, extend, or seed taxonomy content (consistency.md, "The dormant collector taxonomy").
You edit metadata or a collector and need to validate and deliver
| Read | For |
|---|---|
consistency.md | which artifacts move together, the delivery boundary, what CI enforces, the review checklist, the dormant taxonomy |
integrations/README.md | dependencies and the command list for a local run |
how-tos/preview-collector-page.md | selected collector prose; its non-collector route covers flows and other types in an isolated source copy |
description-authoring.md | the catalog sentence and the generated page meta description (the two cross-type description contracts) |
recipes/add-go-collector.md, recipes/update-collector.md | step-by-step for a new or changed go.d collector |
ibm-d.md | the ibm.d generation chain |
how-tos/INDEX.md | retiring a collector, tracing a missing published section, auditing Learn links, Prometheus profiles and the catalog |
Show full SKILL.md (188 more words)Show less
You change the generators, schemas, templates, or CI
| Read | For |
|---|---|
pipeline.md | stages, sources per integration type, validation and rendering, outputs and banners, page locations and learn_rel_path, umbrella pages, both workflows |
schema-reference.md | what each schema validates and the behavior the schema file does not show |
gotchas.md | dead code, silent behaviors, validation traps, the MDX incident |
in-app-contract.md | how cloud-frontend consumes integrations.js and what it treats as a contract |
how-tos/INDEX.md | adding an integration type, the NPM catalog generator |
Citations in this skill name files and symbols, never line numbers; open the file and search for the symbol.
Live how-to rule
Capture timing and authorization follow AGENTS.md#knowledge-capture. Pipeline recipes live in how-tos/ and are
listed in ./how-tos/INDEX.md; prefer updating an existing guide when it already covers most of the question.
Path discipline
.agents/sensitive-data-discipline.md applies: repository files repo-relative, sibling Netdata-org repositories as
${NETDATA_REPOS_DIR}/<repo>/..., no workstation paths.
Related skills
collectors-authoring: read first when authoring a brand-new collector; this skill covers the integration side.collectors-metadata-yaml: the words on the page, field by field.collectors-go-design/config-schema.md: the DynCfg form.docs-learn-site-structure: how the generated pages reachlearn.netdata.cloud(docs/.map/map.yaml, ingest, redirects).collectors-prometheus-profiles: the profile side of the Prometheus catalog.
© 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 17 other files in .agents/skills/integrations-lifecycle of netdata/netdata.
- SKILL.md
- consistency.md
- description-authoring.md
- gotchas.md
- how-tos/INDEX.md
- how-tos/adding-new-integration-type.md
- how-tos/auditing-metadata-learn-links.md
- how-tos/npm-catalog-generation.md
- how-tos/preview-collector-page.md
- how-tos/prometheus-profile-metadata.md
- how-tos/retiring-collector-integration.md
- how-tos/tracing-missing-published-sections.md
- ibm-d.md
- in-app-contract.md
- pipeline.md
- recipes/add-go-collector.md
- recipes/update-collector.md
- schema-reference.md
Open the folder on GitHubat commit 2c378f0
Compare with similar skills
Integrations Lifecycle 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 |
|---|---|---|---|---|---|---|
| Integrations Lifecycle this skillnetdata/netdata | 81k | — | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| OmniRoute Backup and Sync CLIdiegosouzapw/OmniRoute | 74k | — | ~948 | Automated safety check: Pass | MIT | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Thesvgglincker/thesvg | 2.8k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Reflexo ReleaseMyriad-Dreamin/typst.ts | 1.2k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| CI Pipeline Synthesizerkajisho5/ffmpeg-skill | 1.9k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Thesvg
glincker/thesvg
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.
Reflexo Release
Myriad-Dreamin/typst.ts
Guide Reflexo/typst.ts release preparation and operator handoffs.
CI Pipeline Synthesizer
kajisho5/ffmpeg-skill
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.
GitHub Actions Supply Chain Pinning
asyncapi/generator
A skill your agent uses when editing, adding, or reviewing any file under .github/workflows/, or when a CI step installs a CLI tool (npm i -g, npx, pipx, uses: /setup-).
More from netdata/netdata
All 27 skills in this repoDocs 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.
Repo Mirror Sources
netdata/netdata
Inspect Netdata-org source checkouts under NETDATAREPOSDIR, or set up and synchronize that mirror when requested.
Triage Agent Events
netdata/netdata
Investigate Netdata crashes, panics and fatals from agent-events captures or authorized fleet queries.
Triage Codacy
netdata/netdata
Inspect, analyze, troubleshoot, or review Codacy findings and local analyzer/API helpers.
Triage Coverity
netdata/netdata
Inspect or review Coverity Scan defects and saved CID bundles; fetch live findings or apply verified triage decisions when requested.
Triage Sonarqube
netdata/netdata
Inspect, review, or apply authorized triage decisions to SonarCloud issues and security hotspots; also review the Sonar helpers.
Related
Works with
Categories
Questions about Integrations Lifecycle
What does Integrations Lifecycle do?
Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery. Integrations Lifecycle is an agent skill from netdata/netdata. Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery.
When should I use Integrations Lifecycle?
Integrations Lifecycle fits situations like: devOps & Cloud work in your project.
How do I install Integrations Lifecycle in Claude Code?
Run `npx skills add netdata/netdata --skill integrations-lifecycle -a claude-code`. Or copy the skill folder (.agents/skills/integrations-lifecycle in netdata/netdata) into .claude/skills/integrations-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Integrations Lifecycle in Codex?
Run `npx skills add netdata/netdata --skill integrations-lifecycle -a codex`. Or copy the skill folder (.agents/skills/integrations-lifecycle in netdata/netdata) into .agents/skills/integrations-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Integrations Lifecycle 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 integrations-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integrations-lifecycle, .gemini/skills/integrations-lifecycle, .github/skills/integrations-lifecycle and .opencode/skills/integrations-lifecycle in your project.
What does Integrations Lifecycle need to run?
SKILL.md names no scripts, command-line tools or credentials: Integrations Lifecycle is instructions for the agent only.
Does Integrations Lifecycle 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 Integrations Lifecycle 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 Integrations Lifecycle use?
Integrations Lifecycle 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 Integrations Lifecycle use?
About 1.3k tokens (SKILL.md is roughly 5k 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 Integrations Lifecycle?
Skills that share tags, products or a category with Integrations Lifecycle: OmniRoute Backup and Sync CLI (diegosouzapw/OmniRoute, 74k stars), Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars), Thesvg (glincker/thesvg, 2.8k stars) and Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Integrations Lifecycle?
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.