41 skills · sorted by relevance
Investigate production issues by searching Datadog logs, querying metrics, and following request traces across services. Compare error counts across time periods, inspect surrounding logs, and manage dashboards through a command-line tool.
Search and aggregate Datadog logs through the Composio CLI. Filter by service, environment, and time range, follow requests across services, and export structured JSON for incident analysis or scheduled daily digests.
Investigate Sentry alerts using Datadog logs and recent GitHub changes, then post an initial diagnosis with a severity assessment. Notify the on-call team when severity reaches the configured threshold or the investigation remains inconclusive, without changing monitored systems.
Draft incident postmortems by aligning channel updates, GitHub deploys and merges, and Datadog spikes. It opens a review PR with a correlated timeline, proposed causes, and candidate follow-up actions for humans to confirm.
Datadog provider for obz. Supports metrics (Datadog Query Language), logs (Datadog Log Query), and traces. Requires api-key and app-key configured under auth in config.yaml. Does not support metric labels, label-values, or series commands. This skill should be used when the user mentions "Datadog", "DD", "obz -p dd", Datadog Query Language, or needs to configure Datadog provider instances with regional endpoints.
The English summary is being prepared. Showing the original description.
Datadog is a hosted observability platform for infrastructure monitoring, application performance monitoring (APM), log management, and alerting. Use when a user needs to set up Datadog agents, create dashboards, configure monitors and alerts, integrate services, or query metrics and logs through Datadog's API.
The English summary is being prepared. Showing the original description.
Use when the user says "check Datadog", "查 Datadog", "查日志", "check logs", "crash logs", "查 crash", "gateway crash", "查告警", "check alerts", "check metrics", or needs to investigate production issues via Datadog Logs API.
The English summary is being prepared. Showing the original description.
Query and manage Datadog monitoring data — logs, metrics, monitors, dashboards, events, SLOs, traces, and incidents. Use this whenever the user wants to search logs, look at a metric, check which monitors are alerting, investigate a trace, pull SLO status, mute an alert, or ask "what's happening in Datadog" — even if they don't say "API". Also use it for any URL under *.datadoghq.com. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
The English summary is being prepared. Showing the original description.
Set up or review production error monitoring to capture unhandled errors, failed requests, and performance signals. Check event context, release labels, and alert routing so teams receive useful information when problems occur.
Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.
The English summary is being prepared. Showing the original description.
Datadog guidance — APM, logs, metrics, monitors, SLOs, dashboards, and cost control on the Datadog platform.
The English summary is being prepared. Showing the original description.
Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.
The English summary is being prepared. Showing the original description.
CLI do Datadog para buscar logs, consultar métricas, rastrear requisições e gerenciar dashboards. Use isso ao depurar problemas em produção ou trabalhar com observabilidade do Datadog.
The English summary is being prepared. Showing the original description.
Expert en Datadog (APM, logs, infrastructure, monitors, dashboards, SLOs)
The English summary is being prepared. Showing the original description.
Query and filter Datadog logs from the shell using the Composio CLI. Run scoped log searches, pivot across services/environments, and export structured JSON for downstream agents instead of click-driving the Datadog UI.
The English summary is being prepared. Showing the original description.
Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
Implement Datadog monitoring and APM for infrastructure and applications. Configure agents, create dashboards, set up alerts, and implement distributed tracing. Use when implementing enterprise monitoring, APM, or unified observability platforms.
The English summary is being prepared. Showing the original description.
Query and filter Datadog logs from the shell using the Composio CLI. Run scoped log searches, pivot across services/environments, and export structured JSON for incident investigation and diagnostics.
The English summary is being prepared. Showing the original description.
Implementing distributed tracing with W3C Trace Context — the byte-precise `traceparent` and `tracestate` header formats, OpenTelemetry's W3CTraceContextPropagator as the modern default (replacing X-B3-* and X-Datadog-*), head vs tail sampling, and HTTP→SQL trace propagation via sqlcommenter. Grounded in the W3C REC and OpenTelemetry specs. NOT for OTel metrics/logs pipelines, vendor backend setup (Datadog/Honeycomb/Jaeger/Tempo), or browser RUM tracing.
The English summary is being prepared. Showing the original description.
Export recorded AI usage costs and budgets as Prometheus metrics or JSON. Feed external dashboards with totals, model tier breakdowns, session costs, and budget utilization, or send the same data to a webhook endpoint.
Build a company research brief from public sources, covering executive statements, product strategy, organizational practices, and transformation initiatives. Use dated sources to prepare for interviews, understand competitors, assess potential partners, or explore market entry.
Makes a codebase propagate W3C baggage (the `baggage` header carrying `mirrord-session=<key>`) end to end, so mirrord HTTP filters, preview environments, and queue splitting can route a whole request chain to one developer's session. Detects existing OpenTelemetry, Datadog, or other tracing that can already propagate baggage and enables it; otherwise adds a small propagation layer. Covers inbound/outbound HTTP and gRPC, publishing to and consuming from Kafka, RabbitMQ, SQS/SNS, GCP Pub/Sub, Azure Service Bus, NATS, Redis Pub/Sub, BullMQ and Temporal, per-message context restore in consumers, and storage hand-offs such as a GCS signed URL upload that triggers Pub/Sub or an S3 presigned upload that triggers SQS. Ends with a report of every flow found and which ones still drop the header. Use when the user asks to propagate headers, baggage, tracestate, the mirrord session key, or trace context across services or queues, or when a mirrord filter matches the first service but not downstream services or queue consumers.
The English summary is being prepared. Showing the original description.
Operational arsenal for authorized external red-team and bug-bounty recon. Concrete probes, wordlists, regexes, dorks, curl one-liners for: subdomain enum, GraphQL/Swagger/REST discovery, identity fabric (Entra/Okta/ADFS/Google/SAML/M365 deep — Teams/SharePoint/OneDrive), cloud bucket enum (S3/GCS/Azure), CDN/WAF bypass, origin discovery, vendor fingerprinting (Citrix/F5/Pulse/Fortinet/PaloAlto/Cisco/VMware), CI/CD exposure, 48-pattern secret-scan catalog (AWS/GCP/GitHub/Stripe/Slack/Anthropic/OpenAI/Atlassian/DataDog/npm/PyPI), Postman workspaces, breach correlation (HudsonRock/HIBP/DeHashed/IntelX), TLS/JA3 audit, certificate transparency, JS endpoint extraction, package registry leaks, mobile/APK recon, sat imagery, sector-specific recon (healthcare DICOM, finance SWIFT, ICS/SCADA Modbus/BACnet). Detail content in 15 modular reference files, loaded on demand. Use for any authorized recon: scoping, asset discovery, attack-path mapping, secret triage, severity scoring.
The English summary is being prepared. Showing the original description.
Add OpenTelemetry tracing to a new flow or hot path, frontend or backend. Use when building a user-facing flow, a cross-service call, a queue or background job, or code on a latency-sensitive path; when adding spans, span attributes, or trace propagation; or when a trace in Tempo/Datadog is missing, disconnected, or opaque.
The English summary is being prepared. Showing the original description.