Getting Started

Agent skills

Set up Monocle or audit an existing installation with your coding agent

Use the official Monocle skills with your coding agent to connect a service or check an existing installation. They cover AdonisJS, browser apps, Next.js, other Node.js frameworks, Go, Python, and Rust. For other languages, they guide the agent through the official OpenTelemetry SDK with OTLP over HTTP.

Install the skills

The setup prompt in Monocle installs onboarding-monocle if it is missing. To install the setup and audit skills yourself, run this from your application repository:

Terminal
npx skills add monocle-sh/skills

The installer requires Node.js 22.20 or later. Select onboarding-monocle and auditing-monocle, then choose your coding agent. Reload its skills or restart the agent if it does not discover them yet.

Set up a service

Use onboarding-monocle to install the SDKs, configure traces, logs, errors, user attribution, release tracking, and JavaScript source maps. It reads your repository and preserves existing telemetry configuration.

During onboarding, copy the prompt from Connect your app into your coding agent. To add services later, open Services and click Set up with your agent. The prompt uses the skill and the Monocle MCP to create or reuse your services and obtain their DSNs.

For a specific service, open its page and leave With your agent selected under SDK connection. That prompt sets up only the current service. Select Manually for the DSN and SDK instructions.

If you already have a service and DSN, ask:

Agent prompt
Use onboarding-monocle to connect this application to Monocle. Reuse the existing service and DSN configuration.

Your onboarding choices define which features the agent configures. Outside onboarding, or if you skipped those choices, the skill asks what to set up. Replay requires visitor consent and a masking review. The agent reports what it verified and what still needs your action, such as CI secrets or deployment. It does not deploy, commit, or push without separate authorization.

Audit an existing installation

Use auditing-monocle when telemetry is missing or you want to check an installation:

Agent prompt
Use auditing-monocle to check this installation. Explain missing signals and configuration problems without editing files or sending test telemetry.

The audit checks what your application emits and, when Monocle access is available, what Monocle stores. It distinguishes confirmed findings from checks it could not run. It changes nothing unless you ask for fixes.

Skills and MCP

Skills give your coding agent the setup and audit procedures. The MCP gives it access to your Monocle projects and telemetry. You can use the skills without MCP access when your application already has a DSN. Cloud verification remains unverified until the agent can check Monocle.

Search documentation

Search pages and sections of the Monocle documentation