Menu
Use pup to query Datadog metrics and logs -- search, query, aggregate, list, and analyze observability data from the command line.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Compact the current conversation into a handoff document for another agent to pick up.
Generate Archetype Tim Henson X preset files from AI-supplied parameter overrides using a template copy workflow.
Use acli to manage Jira tickets -- search, view, create, edit, transition, assign, comment, and more from the command line.
Create or update Excalidraw diagrams in the Obsidian vault as .md files compatible with the obsidian-excalidraw-plugin.
Manage tmux sessions, windows, and panes via the tmux CLI. Use when the user asks to run background processes, set up multi-pane layouts, monitor commands, or work with tmux in any way.
Use tsq to extract structured code information with tree-sitter queries, symbols, outlines, and references across languages.
| name | pup |
| description | Use pup to query Datadog metrics and logs -- search, query, aggregate, list, and analyze observability data from the command line. |
Use this skill when you need to query Datadog for observability data: searching logs, querying time-series metrics, aggregating log statistics, listing available metrics, or inspecting metric metadata. pup is a CLI wrapper around Datadog APIs.
pup metrics query: Query time-series metric data with aggregation, filtering, and grouping. Primary command for metric analysis.pup metrics search: Same query syntax as query but uses the simpler v1 API. Use when you don't need v2 timeseries formula semantics.pup metrics list: Discover available metric names. Use with --filter to narrow by pattern.pup metrics metadata get: Read metadata (description, unit, type) for a specific metric.pup metrics tags list: List available tags for a specific metric.pup logs query: Query logs using the v2 API (recommended). Supports timezone and flexible sorting.pup logs search: Search logs using the v1 API. Simpler but less capable than query.pup logs list: List logs with basic filtering. Lightest-weight log retrieval.pup logs aggregate: Statistical analysis on logs -- count, avg, percentile, cardinality, grouped by field.-o table for human-readable output, -o json for machine-readable. Default is json.--from and --to accept relative values (1h, 30m, 7d, 1w, 1M) or absolute unix timestamps. --to defaults to now.<aggregation>:<metric_name>{<filter>} [by {<group>}]
avg, sum, min, max, count{env:prod}, {host:web-*}, or {*} for allby {service}, by {host,env}status:error, service:web-app, host:i-*@http.status_code:500, @user.id:12345AND, OR, NOT, negation with -status:info"exact phrase"host:i-*pup metrics list --filter="<pattern>" to find relevant metric names.pup metrics metadata get <metric> to understand unit and type.pup metrics tags list <metric> to see available dimensions.pup metrics query --query="avg:<metric>{<filter>} by {<group>}" --from="1h"pup logs search --query="status:error" --from="1h" --limit=10 to see recent errors.service:X AND @http.status_code:500.pup logs aggregate --query="status:error" --from="1h" --compute="count" --group-by="service" to find which services are failing.pup logs query --query="service:failing-svc AND status:error" --from="1h" --limit=100 for full log details.-o json when processing output programmatically; use -o table when presenting to users.--limit defaults to 50 (max 1000 for search, configurable for query/list).series field of the JSON output.--compute supports: count, avg(@field), sum(@field), min(@field), max(@field), cardinality(@field), percentile(@field, N).--group-by with aggregate to break down results by any log field or attribute.1h means "1 hour ago to now", 7d means "7 days ago to now".