Clerk ObservabilitySAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: clerk-observability description: 'Implement monitoring, logging, and observability for Clerk authentication. Use when setting up monitoring, debugging auth issues in production, or implementing audit logging. Trigger with phrases like "clerk monitoring", "clerk logging", "clerk observability", "clerk metrics", "clerk audit log". ' allowed-tools: Read, Write, Edit, Bash(npm:*), Grep version: 1.15.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - clerk - monitoring - observability - debugging compatibility: Designed for Claude Code --- # Clerk Observability ## Overview Implement monitoring, logging, and observability for Clerk authentication. Covers structured auth logging, middleware performance tracking, webhook event monitoring, Sentry integration, and health check endpoints. ## Prerequisites - Clerk integration working - Monitoring platform (Sentry, DataDog, or Pino logger at minimum) - Logging infrastructure (structured JSON logs recommended) ## Instructions ### Step 1: Structured Authentication Event Logging ```typescript // lib/auth-logger.ts import pino from 'pino' const logger = pino({ level: process.env.LOG_LEVEL || 'info', transport: process.env.NODE_ENV === 'development' ? { target: 'pino-pretty' } : undefined, }) export function logAuthEvent(event: { type: 'sign_in' | 'sign_out' | 'sign_up' | 'permission_denied' | 'session_expired' userId?: string | null orgId?: string | null path: string metadata?: Record<string, any> }) { logger.info({ category: 'auth', ...event, timestamp: new Date().toISOString(), }) } export function logAuthError(error: Error, context: { userId?: string; path: string }) { logger.error({ category: 'auth', error: error.message, stack: error.stack, ...context, timestamp: new Date().toISOString(), }) } ``` ### Step 2: Middleware Performance Monitoring ```typescript // middleware.ts import { clerkMiddleware, createRouteMatcher } from '@clerk/nextjs/server' const isPublicRoute = createRouteMatcher(['/', '/sign-in(.*)', '/sign-up(.*)']) export default clerkMiddleware(async (auth, req) => { const start = Date.now() if (!isPublicRoute(req)) { await auth.protect() } const duration = Date.now() - start const { userId } = await auth() // Log slow auth checks if (duration > 100) { console.warn(`[Auth Perf] ${req.nextUrl.pathname} took ${duration}ms`, { userId: userId || 'anonymous', method: req.method, }) } // Add timing header for debugging const response = new Response(null, { status: 200 }) response.headers.set('X-Auth-Duration', `${duration}ms`) }) ``` ### Step 3: Webhook Event Tracking ```typescript // app/api/webhooks/clerk/route.ts import { logAuthEvent } from '@/lib/auth-logger' async function handleWebhookEvent(evt: WebhookEvent) { const startTime = Date.now() // Track webhook processing metrics const metrics = { eventType: evt.type, receivedAt: new Date().toISOString(), processingTimeMs: 0, } switch (evt.type) { case 'user.created': logAuthEvent({ type: 'sign_up', userId: evt.data.id, path: '/webhooks/clerk', metadata: { email: evt.data.email_addresses[0]?.email_address }, }) await db.user.create({ data: { clerkId: evt.data.id } }) break case 'session.created': logAuthEvent({ type: 'sign_in', userId: evt.data.user_id, path: '/webhooks/clerk', }) break case 'session.ended': logAuthEvent({ type: 'sign_out', userId: evt.data.user_id, path: '/webhooks/clerk', }) break } metrics.processingTimeMs = Date.now() - startTime // Alert on slow webhook processing if (metrics.processingTimeMs > 5000) { console.error('[Webhook] Slow processing:', metrics) } return Response.json({ received: true }) } ``` ### Step 4: Sentry Error Tracking Integration ```typescript // lib/sentry-clerk.ts import * as Sentry from '@sentry/nextjs' import { auth, currentUser } from '@clerk/nextjs/server' export async function initSentryUser() { const { userId, orgId } = await auth() if (userId) { const user = await currentUser() Sentry.setUser({ id: userId, email: user?.emailAddresses[0]?.emailAddress, username: user?.username || undefined, }) Sentry.setTag('org_id', orgId || 'personal') } } // Wrap API routes with Sentry + Clerk context export function withAuthSentry(handler: Function) { return async (...args: any[]) => { await initSentryUser() try { return await handler(...args) } catch (error) { Sentry.captureException(error) throw error } } } ``` ```typescript // sentry.server.config.ts import * as Sentry from '@sentry/nextjs' Sentry.init({ dsn: process.env.SENTRY_DSN, tracesSampleRate: 0.1, beforeSend(event) { // Scrub Clerk secret key if accidentally logged if (event.extra) { delete event.extra['CLERK_SECRET_KEY'] } return event }, }) ``` ### Step 5: Health Check Endpoint ```typescript // app/api/health/route.ts import { clerkClient } from '@clerk/nextjs/server' export async function GET() { const checks: Record<string, { status: string; latencyMs: number; detail?: string }> = {} // Check Clerk Backend API const clerkStart = Date.now() try { const client = await clerkClient() await client.users.getUserList({ limit: 1 }) checks.clerk = { status: 'healthy', latencyMs: Date.now() - clerkStart } } catch (err: any) { checks.clerk = { status: 'unhealthy', latencyMs: Date.now() - clerkStart, detail: err.message } } // Check database const dbStart = Date.now() try { await db.$queryRaw`SELECT 1` checks.database = { status: 'healthy', latencyMs: Date.now() - dbStart } } catch (err: any) { checks.database = { status: 'unhealthy', latencyMs: Date.now() - dbStart, detai
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__clerk-observability.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Clerk Observability skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Clerk Observability safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Clerk Observability access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Clerk Observability work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.