Official agent skill

Create Status Provider

Add a new section to the agent status output (agent status command)

OfficialApache-2.0Auto-check: notesDevOps & Cloud

Install Create Status Provider

skills CLI

$ npx skills add DataDog/datadog-agent --skill create-status-provider -a claude-code

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

GitHub CLI

$ gh skill install DataDog/datadog-agent create-status-provider --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/DataDog/datadog-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-status-provider .claude/skills/create-status-provider && 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/

Paste into Claude Code

Install the "create-status-provider" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider into .claude/skills/create-status-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-status-provider", 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

$skill-installer install https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider

Type 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.

skills CLI

$ npx skills add DataDog/datadog-agent --skill create-status-provider -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent create-status-provider --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-status-provider .agents/skills/create-status-provider && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "create-status-provider" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider into .agents/skills/create-status-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-status-provider", 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.

skills CLI

$ npx skills add DataDog/datadog-agent --skill create-status-provider -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent create-status-provider --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-status-provider .cursor/skills/create-status-provider && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "create-status-provider" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider into .cursor/skills/create-status-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-status-provider", 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

$ gemini skills install https://github.com/DataDog/datadog-agent.git --path .agents/skills/create-status-provider

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DataDog/datadog-agent --skill create-status-provider -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent create-status-provider --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-status-provider .gemini/skills/create-status-provider && rm -rf skills-src

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

Paste into Gemini CLI

Install the "create-status-provider" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider into .gemini/skills/create-status-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-status-provider", 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.

GitHub CLI

$ gh skill install DataDog/datadog-agent create-status-provider

Installs 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).

skills CLI

$ npx skills add DataDog/datadog-agent --skill create-status-provider -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-status-provider .github/skills/create-status-provider && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "create-status-provider" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider into .github/skills/create-status-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-status-provider", 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.

skills CLI

$ npx skills add DataDog/datadog-agent --skill create-status-provider -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DataDog/datadog-agent create-status-provider --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DataDog/datadog-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-status-provider .opencode/skills/create-status-provider && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "create-status-provider" agent skill from https://github.com/DataDog/datadog-agent/tree/main/.agents/skills/create-status-provider into .opencode/skills/create-status-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-status-provider", 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: create-status-provider
GitHub stars: 3.8k
Token cost: ~685 tokens
SKILL.md length: 294 words
Files: 1
Skills in repo: 35
Repo updated: Oct 8, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Add a new section to the agent status output (agent status command)

Works in 5 steps: Gather information from the user → Read reference examples → Implement the provider → …
DevOps & Cloud work in your project
SKILL.md covers Instructions, Important Notes and Usage
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Status Provider is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization. Add a new section to the agent status output (agent status command)

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Datadog. The repository describes itself as: Main repository for Datadog Agent. The licence is Apache-2.0.

When your agent uses it

DevOps & Cloud work in your project

Example prompts

“/create-status-provider”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Gather information from the user
Read reference examples
Implement the provider
Register the provider
Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 20eff25. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Write
- Edit
- Glob
- Grep
- AskUserQuestion
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

Create Status Provider loads about 685 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 294 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion

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 DataDog/datadog-agent at commit 20eff25, republished under its Apache-2.0 licence (© DataDog). 294 words, ~685 tokens.

Download SKILL.mdSave it as .claude/skills/create-status-provider/SKILL.md (or your agent's skills folder).

name: create-status-provider
description: Add a new section to the agent status output (agent status command)
allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion
argument-hint: [provider-name]
model: sonnet

Add a new status provider to the Datadog Agent. Status providers contribute sections to the agent status output in JSON, plain text, and HTML formats.

Instructions

Step 1: Gather information from the user

Use AskUserQuestion to collect the following. If $ARGUMENTS provides the provider name, skip that question.

Provider name: Display name for this status section (e.g. "DogStatsD", "Forwarder").
Section name: Grouping key. Providers with the same section are grouped. "collector" always appears first.
What data to display: What information should this section show?
Placement: Inside an existing component's Provides struct (most common) or standalone module?
Conditional?: Should the provider only appear when a feature is enabled?

Step 2: Read reference examples

Before writing any code, read the appropriate reference files to follow existing patterns:

What	Reference file
Provider interface	`comp/core/status/component.go`
Provider implementation + templates	`comp/dogstatsd/status/statusimpl/status.go` and its `status_templates/` directory
Registration in component Provides	`comp/trace/status/statusimpl/status.go`
Template helpers (humanize, etc.)	`comp/core/status/render_helpers.go`

Step 3: Implement the provider

Create the provider implementation following the reference. Also create the status_templates/<name>.tmpl and status_templates/<name>HTML.tmpl files following the templates in the reference's status_templates/ directory.

To make a provider conditional, return nil from the constructor when the feature is disabled.

Step 4: Register the provider

Register using status.NewInformationProvider(yourProvider{...}) — either in an existing component's Provides struct (most common) or as a standalone Module(). The reference files show both patterns.

Step 5: Verify

Build: dda inv agent.build --build-exclude=systemd
Lint: dda inv linter.go
Report the results to the user.

Important Notes

Template directory must be named exactly status_templates and embedded via //go:embed status_templates.
Use a top-level key (e.g. "myFeatureStats") to namespace data in the shared stats map.
For HeaderProvider (rarely needed), use NewHeaderInformationProvider() instead.

Usage

/create-status-provider — Interactive: prompts for all details
/create-status-provider "My Feature" — Pre-fills the provider name

Files

Just SKILL.md in .agents/skills/create-status-provider of DataDog/datadog-agent.

Open the folder on GitHubat commit 20eff25

Compare with similar skills

Create Status Provider 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.

Create Status Provider compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create Status Provider this skillDataDog/datadog-agent	3.8k	—	~685	Automated safety check: Notes	Apache-2.0	today
Apm IntegrationsDataDog/dd-trace-js	836	—	~3k	Automated safety check: Pass	Custom licence	today
Dd IdpDataDog/pup	1k	—	~2k	Automated safety check: Pass	Apache-2.0	yesterday
Datadog Data Source GeneratorDataDog/terraform-provider-datadog	468	—	~2.7k	Automated safety check: Pass	MPL-2.0	today
Apm IntegrationsDataDog/dd-trace-java	736	—	~3.7k	Automated safety check: Notes	Apache-2.0	today
Tool ConnectorZhixiangLuo/10xProductivity	478	—	~925	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Apm Integrations
DataDog/dd-trace-js
Official
A skill your agent uses when adding, debugging, fixing, or modifying instrumentation and plugins for third-party libraries in dd-trace-js.
836 GitHub stars~3k tokensUpdated today
DevOps & CloudAuto-check passed
Dd Idp
DataDog/pup
Official
Find, filter, count, and connect software, teams, engineering work and delivery, infrastructure, and operational or security records through Pup's read-only Datadog entity graph.
1k GitHub stars~2k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Datadog Data Source Generator
DataDog/terraform-provider-datadog
Official
Generates a Datadog Terraform provider data source from an OpenAPI operation with tfgen and opens a review-ready GitHub PR with a risk scan and testing guide.
468 GitHub stars~2.7k tokensUpdated today
DevOps & CloudAuto-check passed
Apm Integrations
DataDog/dd-trace-java
Official
Write a new library instrumentation end-to-end. An agent skill from DataDog/dd-trace-java.
736 GitHub stars~3.7k tokensUpdated today
DevOps & CloudAuto-check: notes
Tool Connector
ZhixiangLuo/10xProductivity
Connect any tool you use at work to your agent — including internal company tools, custom-built systems, deployment portals, incident trackers, internal knowledge bases, HR systems, and commercial…
478 GitHub stars~925 tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Redis Observability
redis/agent-skills
Official
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
165 GitHub starsUsed in 2 repos~911 tokens
DevOps & CloudAuto-check passed

More from DataDog/datadog-agent

All 35 skills in this repo

Triage CI Failure
DataDog/datadog-agent
Official
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
3.8k GitHub stars~2.3k tokensUpdated today
Auto-check passed
Elicit
DataDog/datadog-agent
Official
Run a structured discovery session to build an Allium specification through conversation.
3.8k GitHub starsUsed in 1 repo~3.7k tokens
Auto-check passed
Follow PR
DataDog/datadog-agent
Official
Monitor the current PR's GitLab pipeline to completion, then report success, auto-fix, or investigate a failure.
3.8k GitHub stars~3.2k tokensUpdated today
Auto-check passed
Create Epic Recap
DataDog/datadog-agent
Official
A skill your agent uses when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so…
3.8k GitHub stars~5k tokensUpdated today
Auto-check: notes
Explain Lading Config
DataDog/datadog-agent
Official
Explains a lading.yaml config file from the regression test suite, using the lading Rust source as ground truth for field meanings and defaults.
3.8k GitHub stars~1.2k tokensUpdated today
Auto-check passed
Distill
DataDog/datadog-agent
Official
Extract an Allium specification from an existing codebase. An agent skill from DataDog/datadog-agent.
3.8k GitHub starsUsed in 1 repo~7k tokens
Auto-check passed

Works with

Datadog

Questions about Create Status Provider

What does Create Status Provider do?

Add a new section to the agent status output (agent status command). Create Status Provider is an agent skill from DataDog/datadog-agent, published by the product's own GitHub organization.

When should I use Create Status Provider?

Create Status Provider fits situations like: devOps & Cloud work in your project.

How do I install Create Status Provider in Claude Code?

Run `npx skills add DataDog/datadog-agent --skill create-status-provider -a claude-code`. Or copy the skill folder (.agents/skills/create-status-provider in DataDog/datadog-agent) into .claude/skills/create-status-provider in your project. Claude Code loads it when a task matches its description.

How do I install Create Status Provider in Codex?

Run `npx skills add DataDog/datadog-agent --skill create-status-provider -a codex`. Or copy the skill folder (.agents/skills/create-status-provider in DataDog/datadog-agent) into .agents/skills/create-status-provider in your project. Codex loads it when a task matches its description.

Can I use Create Status Provider 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 DataDog/datadog-agent --skill create-status-provider -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-status-provider, .gemini/skills/create-status-provider, .github/skills/create-status-provider and .opencode/skills/create-status-provider in your project.

What does Create Status Provider need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Status Provider is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion.

Does Create Status Provider 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 Create Status Provider safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Create Status Provider use?

Create Status Provider is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Status Provider use?

About 685 tokens (SKILL.md is roughly 2.7k 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 Create Status Provider?

Skills that share tags, products or a category with Create Status Provider: Apm Integrations (DataDog/dd-trace-js, 836 stars), Dd Idp (DataDog/pup, 1k stars), Datadog Data Source Generator (DataDog/terraform-provider-datadog, 468 stars) and Apm Integrations (DataDog/dd-trace-java, 736 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Status Provider?

DataDog (a GitHub organization, an official publisher) maintains it in DataDog/datadog-agent, which has 3,757 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Create Status Provider

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Instructions

Step 1: Gather information from the user

Step 2: Read reference examples

Step 3: Implement the provider

Step 4: Register the provider

Step 5: Verify

Important Notes

Usage

Files

Compare with similar skills

Similar skills

More from DataDog/datadog-agent

Related

Questions about Create Status Provider