Serverless Integrations Agent Skill

| Use when adding, modifying, debugging, or reviewing dd-trace-js serverless platform integrations that create serverless integration, function invocation root span, Lambda runtime, Azure Functions, GCP Functions, type = 'serverless', DD_LAMBDA_HANDLER, datadog-lambda-js, deployed serverless verification, manual serverless test.

4k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

830

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/DataDog/dd-trace-js --skill serverless-integrations

What comes with it

13 372 bytes besides the instruction

references/architecture.md

references/implementation-guide.md

references/reference-integrations.md

references/testing-guide.md

The instruction itself

6 sections, as written by the author

Serverless Integrations

Use this skill for platform-boundary instrumentation where dd-trace-js owns the function invocation lifecycle.

Use apm-integrations instead for ordinary library instrumentation that runs inside a serverless function.

Decision Gate

Classify the request before touching code:

| Request shape | Skill path | Span model |

| --- | --- | --- |

| Trace a third-party library call inside Lambda/Azure/GCP | apm-integrations | Child spans under the invocation |

| Trace the cloud function invocation itself | This skill | Root type = 'serverless' span |

| Trace an HTTP, queue, or event trigger | This skill plus trigger references | Root span plus context or links |

| Change AWS Lambda bootstrap or timeout behavior | This skill | Special-case runtime wrapper path |

Do not model ordinary library plugins after the Lambda bootstrap. Lambda is a compatibility/runtime wrapper path,

not the default architecture for new integrations.

Core Invariants

Serverless platform integrations represent the invocation as the primary unit of work.
Root plugins set static kind = 'server' and static type = 'serverless'.
Use TracingPlugin unless a more specific local pattern clearly applies. Do not default to ServerPlugin just

because the span kind is server.

The integration owns every completion path: success, thrown error, rejected promise, callback completion,

timeout, and runtime shutdown when the platform exposes it.

Flush behavior must be designed around the platform freezing or terminating the process.
Context extraction happens at the platform boundary: HTTP headers, event/message attributes, client context, or

batch span links.

Preserve diagnostic-channel subscriber behavior. AppSec, IAST, telemetry, and other subscribers may depend on

published events even when the tracing plugin is disabled.

Prefer Orchestrion for static module hooks. Use shimmer/runtime wrapping only when the platform's handler model

requires dynamic interception, and document why.

Workflow

Read references/architecture.md to confirm whether the work is serverless-root or ordinary APM.
Read references/reference-integrations.md and inspect at least one matching in-repo implementation.
For implementation work, follow references/implementation-guide.md.
For tests and deployed verification, follow references/testing-guide.md.

Implementation Checklist

Add or update instrumentation in packages/datadog-instrumentations/ when the runtime can be observed through

normal hooks.

Add or update the plugin under packages/datadog-plugin-<name>/ when spans are created from diagnostic-channel

events.

Register the plugin in packages/dd-trace/src/plugins/index.js.
Add service naming behavior under packages/dd-trace/src/service-naming/schemas/*/serverless.js.
Add docs, TypeScript config surface, and supported-integration metadata only when the user-facing configuration

surface changes.

For HTTP-triggered functions, reuse web helpers such as web.patch, web.startServerlessSpanWithInferredProxy,

and web.finishAll when they match the trigger model.

For batch/message triggers, extract upstream context per item when possible and use span links for multiple

upstream contexts.

Review Checklist

The invocation span starts before user handler execution and finishes exactly once.
Errors are tagged on the invocation span without crashing the user app.
Async, promise, callback, and synchronous handlers are all covered when the runtime supports them.
Timeout or near-shutdown behavior finishes or flushes trace data before the platform freezes execution.
Disabled instrumentation still leaves unrelated integrations intact.
Deployed/manual verification instructions confirm traces in Datadog, not only local unit behavior.

Other skills for the same job

different authors, same section of the catalogue

Azure Kubernetes Automatic Readiness

by microsoft

vendor ×3

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

How to use it

Copy the folder

Take datadog/serverless-integrations from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.