AI agent skills that install Autter Runtime — open-source error tracking and usage telemetry — into any codebase, regardless of language or framework.
Drop these into Claude Code, Cursor, Codex, or any editor that supports the Agent Skills standard and start using them immediately.
npx skills add Autter-dev/autter-skills --allThen tell your agent: "use the skills to install Autter Runtime in this
project." It runs autter-runtime-setup, which inventories your repo and
routes each service to the right style skill automatically — you don't need
to pick one yourself.
Want just one skill? npx skills add Autter-dev/autter-skills --skill otel-node-style
| Skill | Covers |
|---|---|
autter-runtime-setup |
Start here. Inventories the repo, gets an ingest key, routes each service to the right style skill below, verifies telemetry actually arrives. |
otel-node-style |
Node.js (Express, Fastify, Koa, NestJS) and Next.js, via @autter/runtime-node / @autter/runtime-next. |
otel-browser-style |
Browser apps — React, Vue, Svelte, Angular, vanilla SPA, static sites — via @autter/runtime-browser. |
otel-python-style |
FastAPI, Flask, Django, plain WSGI/ASGI, via the standard OpenTelemetry Python SDK. |
otel-go-rust-style |
Go and Rust backends, via each language's official OTel SDK. |
otel-generic-style |
Everything else — Java, .NET, PHP, Ruby, Elixir, Kotlin, … — via standard OTLP/HTTP + OTel env vars. |
Autter Runtime's ingester is just two credentials and three HTTP endpoints:
| Credential | Lives in | Can |
|---|---|---|
Server key autter_rt_… |
backend env vars | send OTLP traces/metrics, relay browser events |
Client key autter_rtc_… |
frontend bundles (publishable) | send browser events only, origin-restricted |
| Endpoint | Format |
|---|---|
POST /v1/traces, POST /v1/metrics |
OTLP/HTTP — protobuf or JSON |
POST /v1/browser |
compact JSON (@autter/runtime-browser payload) |
Any language with an OpenTelemetry SDK can send server telemetry — that's
every mainstream language. Only Node.js and the browser get dedicated
first-party npm packages (@autter/runtime-node, @autter/runtime-browser,
@autter/runtime-next); everything else is a thin style guide over the
standard OTel SDK for that language, which otel-generic-style covers even
when no dedicated skill exists yet.
Create one on your Autter dashboard: Settings → Access Tokens → Runtime ingest keys → Create key. Pick the repository, then choose:
- Server — secret, for backends and relays. Keep it in env vars, never commit it.
- Client — publishable, for browser-only apps with no backend. Scoped to the exact origins you register it for.
Full docs: github.com/Autter-dev/autter-runtime.
MIT