About datadog-app
A workflow skill for developers building Datadog Apps with TypeScript and React. It routes common app development, publishing, querying, CI/CD, and troubleshooting tasks to focused references, while excluding Datadog platform package development.
Key features
- 01Guided Datadog Apps development
- 02Reference routing by task
- 03Build, upload, and publish guidance
- 04CI/CD deployment guidance
- 05Querying and authentication troubleshooting
Use cases
- 01Scaffolding or running a Datadog App locally
- 02Publishing an app or configuring its Datadog site
- 03Adding GitHub Actions deployment
- 04Investigating app authentication or backend failures
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/datadog-appin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/build-upload-publish.mdcicd.mdgetting-started.mdtroubleshooting.mdupgrading.mdworkflow-http-trigger.mdreferences/querying-data/connections.mdgetting-started.mdreferences/querying-data/ddsql/datastores.mdDetails
From the project READMEDatadog Apps
Use this skill when a developer is building a Datadog Apps project with TypeScript, React, published packages, and the normal production Datadog site. If the user is modifying Datadog platform packages or testing package source changes, use a platform-engineer-oriented workflow instead.
Overview
Datadog Apps are locally developed web apps built with React and TypeScript or JavaScript. Use Apps when a project needs source control, code review, CI/CD, multi-engineer collaboration, AI-assisted local development, custom UI or logic, or backend code that integrates with services beyond low-code App Builder. Apps share App Builder's permissions model and can be embedded in Datadog surfaces such as dashboards and the Internal Developer Portal.
Reference Routing
Read only the reference needed for the user's task:
| User task | Read |
|---|---|
| Create, scaffold, configure prerequisites, or run locally | references/getting-started.md |
| Build, upload, publish, upload without publishing, add upload-no-publish script, configure Datadog site, or understand upload output | references/build-upload-publish.md |
| Add or update GitHub Actions deployment | references/cicd.md |
| Trigger or poll Workflow Automation from a backend function | references/workflow-http-trigger.md |
| Get started querying data from a Datadog App | references/querying-data/getting-started.md |
| Understand or configure Action Catalog connections | references/querying-data/connections.md |
| Query Datadog App datastores with DDSQL | references/querying-data/ddsql/datastores.md |
| Upgrade Datadog Apps dependencies or compare with a freshly scaffolded app | references/upgrading.md |
| Diagnose OAuth, API/application key auth, upload, Node, site, or backend function failures | references/troubleshooting.md |
Boundaries
- After scaffolding or when working inside an existing app, read the app project's
AGENTS.mdbefore making changes. - For backend function implementation details, rely on the generated app project's
AGENTS.md; this skill only covers local development auth choices and troubleshooting. - Preserve the app project's existing package manager, scripts, Datadog site, and repository conventions.
- Do not cover Datadog package/platform development in this skill.
- Low-code App Builder to Datadog Apps migration guidance is future work. Do not invent a migration process yet.