Menu
Covers observability integration including metrics, traces, and logs following OpenTelemetry conventions. Use when instrumenting services for monitoring and debugging.
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
Covers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.
Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.
Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.
Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.
| name | capability-telemetry |
| description | Covers observability integration including metrics, traces, and logs following OpenTelemetry conventions. Use when instrumenting services for monitoring and debugging. |
This skill covers telemetry integration for Datum Cloud services.
Telemetry enables services to emit observability data. The telemetry system handles:
All telemetry follows OpenTelemetry conventions.
Numeric measurements with dimensions:
// Counter - monotonically increasing
requests := meter.Int64Counter("myresource.requests.total")
requests.Add(ctx, 1, attribute.String("method", "create"))
// Gauge - point-in-time value
activeResources := meter.Int64UpDownCounter("myresource.active")
activeResources.Add(ctx, 1)
// Histogram - distribution of values
latency := meter.Float64Histogram("myresource.request.duration_seconds")
latency.Record(ctx, duration.Seconds())
Request flow across services:
ctx, span := tracer.Start(ctx, "CreateMyResource")
defer span.End()
span.SetAttributes(
attribute.String("resource.name", name),
attribute.String("resource.namespace", namespace),
)
if err != nil {
span.RecordError(err)
span.SetStatus(codes.Error, err.Error())
}
Structured event records:
logger.Info("resource created",
"name", resource.Name,
"namespace", resource.Namespace,
"spec", resource.Spec,
)
logger.Error(err, "failed to create resource",
"name", name,
)
Pattern: {service}.{resource}.{measurement}[.{unit}]
| Example | Description |
|---|---|
compute.vm.requests.total | Total VM API requests |
compute.vm.active | Currently active VMs |
compute.vm.cpu.utilization.percent | VM CPU utilization |
compute.vm.request.duration.seconds | Request latency |
Pattern: {Operation}{Resource}
| Example | Description |
|---|---|
CreateVirtualMachine | Creating a VM |
ReconcileVirtualMachine | Reconciling a VM |
ValidateVirtualMachine | Validating a VM |
Standard fields:
resource.name — Resource nameresource.namespace — Resource namespaceresource.apiVersion — API versionresource.kind — Resource kindoperation — What was attemptederror — Error if failedRead implementation.md for:
Run scripts/validate-metrics.sh to verify:
implementation.md — Integration guidescripts/validate-metrics.sh — Validation scriptscripts/scaffold-telemetry.sh — Scaffolding script