Run any Skill in Manus with one click

datadog-pup

Stars17

Forks2

UpdatedJuly 25, 2026 at 12:16

Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

l-lin

l-lin/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

3 files

SKILL.md

readonly

name	datadog-pup
description	Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

Scope first. Confirm the org and team before broad queries or lists.
- If results look wrong, run pup auth status. If needed, use pup auth login --org monolith or add --org monolith.
- On p3c, filter shared resources before listing. Use monitor tags like team:p3c and log queries like team:p3c service:<service>.
Prove it. For incidents, read the source of truth, narrow the time window, then inspect traces or metrics.
- For latency or SLO work, follow references/LATENCY-SLO-TRIAGE.md.
- Remember the unit trap: APM span durations are nanoseconds, APM metrics are seconds, and trace.* metrics may need base_service: instead of service:.
Mutate safely. Search or list before acting, then get, then export JSON before create, update, or delete.
- Prefer --agent when you need structured output.
- Use -y only when automation truly needs a non-interactive delete.
Reach for the right reference.
- Use references/COMMANDS.md for command patterns across traces, metrics, monitors, logs, synthetics, notebooks, SLOs, dashboards, incidents, and discovery.
- Treat missing JVM or runtime metrics as a blind spot, not proof that nothing happened.

More from this repository

same repository

kibana-elasticsearch

l-lin/dotfiles

Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.

2026-07-2517

devils-advocate

l-lin/dotfiles

Use when pressure-testing a plan, architecture, code change, or AI-generated proposal before committing, especially when hidden assumptions, production risks, or failure modes may be underexplored.

2026-07-2517

crafting-skills

l-lin/dotfiles

Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.

2026-07-2517

code-simplifier

l-lin/dotfiles

Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".

2026-07-2517

ingest-url

l-lin/dotfiles

Ingest a URL into the patient account wiki. Use when the user provides a URL (Atlassian/Confluence, web articles, documentation) and wants to add it to their research wiki. Handles fetching, markdown conversion, asset extraction, and runs the full wiki ingest workflow. Triggers on "ingest <url>", "add this to the wiki", or when user shares a URL in the context of wiki research.

2026-07-2417

journal

l-lin/dotfiles

Use at session start, after context compaction, and before session end. Owns session journals in `.sandbox/journals/`: when to create one, what prior context to read, what to log, and how to leave a resumable handoff

2026-07-1117

name	datadog-pup
description	Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

Scope first. Confirm the org and team before broad queries or lists.
- If results look wrong, run pup auth status. If needed, use pup auth login --org monolith or add --org monolith.
- On p3c, filter shared resources before listing. Use monitor tags like team:p3c and log queries like team:p3c service:<service>.
Prove it. For incidents, read the source of truth, narrow the time window, then inspect traces or metrics.
- For latency or SLO work, follow references/LATENCY-SLO-TRIAGE.md.
- Remember the unit trap: APM span durations are nanoseconds, APM metrics are seconds, and trace.* metrics may need base_service: instead of service:.
Mutate safely. Search or list before acting, then get, then export JSON before create, update, or delete.
- Prefer --agent when you need structured output.
- Use -y only when automation truly needs a non-interactive delete.
Reach for the right reference.
- Use references/COMMANDS.md for command patterns across traces, metrics, monitors, logs, synthetics, notebooks, SLOs, dashboards, incidents, and discovery.
- Treat missing JVM or runtime metrics as a blind spot, not proof that nothing happened.