Catalog
pydantic/logfire-setup

pydantic

logfire-setup

Route broad requests to set up Pydantic Logfire across application instrumentation, infrastructure, evals, frontend observability, Gateway, or coding agents. Use for "set up Logfire", "add Logfire to my project", "get me set up properly with Logfire", "send as much data as would be useful", mentions of Logfire without specific scope, or multi-surface requests; use the matching specialist directly for an already scoped request.

NewUpdated Oct 17, 2026

Set Up Logfire

Route each explicitly requested surface to its specialist below; leave installation and verification to those specialists. Do not expand an otherwise scoped request.

Proceed through ordinary, reversible setup with short updates without asking approval; no clean tree, branch, commits, or plan is required. Pause for browser auth, unresolved app/project ambiguity, material production cost or telemetry increases, deploy/infra changes, or destructive/unrelated work, then ask one concrete question. Report only verification observed in this session.

Step 1: Authenticate and Select the Exact Project

If the request is already scoped to frontend observability, application Gateway, coding-agent setup, querying, or opening the UI, load that specialist from the table below first. Its credential requirements differ from ordinary SDK instrumentation; do not create a project write token merely to route the request.

For ordinary SDK instrumentation, confirm the exact project with whoami before inspecting or running application files.

Use Authenticate and Select the Exact Project to derive the CLI target from the supplied Logfire URL and run its target-aware whoami check with a verified CLI path — for JS/TS projects without uv, use the external-prefix npm fallback instead of plain npx, which can execute a repository-local binary. Skip to Step 2 if that already reports the right project and resolved --region or --base-url target; otherwise, continue through the full authentication and project-selection sequence there.

Step 2: Understand the Repo

Read AGENTS.md/CLAUDE.md/README.md and skim the language, runtime, and package manager. Then match what you find against the table below to decide what to fetch next:

Surface Covers Skill
App instrumentation Traces, logs, metrics, and AI/agent spans from application code — Python, JavaScript/TypeScript, Rust, or any OpenTelemetry language logfire-instrumentation
Frontend observability Browser errors, RUM, Web Vitals, and session replays logfire-frontend
Infrastructure monitoring Hosts, Docker, Kubernetes, database/queue/cache servers, cloud-provider metrics — no application code logfire-infrastructure
Evals Set up and run AI/agent evaluations against test-case datasets in Python or Node.js logfire-evals
Querying telemetry Search traces/logs/spans/metrics, summarize errors, find root cause logfire-query
Live UI Open project pages, the live view, trace links, or the Explore page in a browser logfire-ui
Feature flags Runtime-managed variables (logfire.var(), logfire.template_var()) no dedicated skill yet — see the product's own docs
Application Gateway Route an application's model calls through Pydantic AI Gateway logfire-gateway
Coding agents Record Claude/Codex sessions or configure coding-agent Gateway routing logfire-coding-agents
  • With no specific scope, get one representative application service to verified first data. Incidental Docker/eval files do not expand the task. Route infrastructure-only repositories to logfire-infrastructure.
  • A request already scoped to one surface ("monitor my Postgres server", "set up evals for this agent") → fetch that skill directly, skipping the rest of this table.
  • Genuinely ambiguous between two adjacent surfaces (e.g. "watch my Postgres" could mean Collector-level infrastructure metrics or app-level query instrumentation)? Ask one clarifying question rather than guessing — loading the wrong skill wastes the user's time reading instructions for a job they didn't ask for.

Step 3: Fetch the Right Skill(s)

Load the selected skill and follow its credential workflow. SDK specialists verify the project with whoami; CLI specialists preserve prepared handoffs, and query/UI skills can use existing native MCP access. Do not force one authentication method across all surfaces.

Never print, log, hard-code, commit, or echo a token, in any of these skills, at any point. The one exception — reading .logfire/logfire_credentials.json's token key programmatically to hand a non-native-SDK application its write token, never to display it — is in auth.md.

Files1
1 files · 1.1 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

82

Quality

85

Clarity

88

Completeness

76

Summary

This skill is a router that directs users to specialized Logfire setup skills based on their request scope. It handles authentication, project selection, and skill-matching logic without performing direct instrumentation—delegating app tracing, frontend observability, infrastructure, evals, querying, UI, and Gateway/coding-agent setup to seven specialized downstream skills.

Static Analysis Findings

1 finding

Patterns detected by deterministic static analysis before AI scoring. Hover over any finding code for detailed information and remediation guidance.

Credential Exposure
SEC-022SSH/Credentials File AccessMax: B

SSH key or credentials file access

SKILL.mdcredentials.json

Detected Capabilities

file read (AGENTS.md, CLAUDE.md, README.md)credential workflow coordination (token reading from .logfire/logfire_credentials.json)subprocess execution (CLI whoami checks)external skill routing (references to pydantic.dev specialist skills)

Trigger Keywords

Phrases that agents use to match this skill to user intent.

set up logfireadd logfire to projectlogfire instrumentationconfigure observabilitylogfire routing

Risk Signals

WARNING

References reading credentials.json token key from .logfire/logfire_credentials.json programmatically

SKILL.md | Step 3 section
WARNING

Direct programmatic access to token field in credentials file for non-native-SDK app use

SKILL.md | auth.md reference and instructions

Referenced Domains

External domains referenced in skill content, detected by static analysis.

pydantic.dev

Use Cases

  • Route broad Logfire setup requests to the correct specialist skill
  • Authenticate users and verify the correct Logfire project before instrumentation
  • Help users decide which Logfire surface (app, frontend, infrastructure, evals, etc.) matches their use case
  • Preserve credential workflows specific to each Logfire surface (SDK vs. CLI vs. UI access)
  • Avoid forcing one authentication method across different instrumentation surfaces

Quality Notes

  • Excellent structure: clear routing table with explicit surface-to-skill mapping
  • Strong security posture: explicit prohibition on printing, logging, hard-coding, committing, or echoing tokens—with documented exception for programmatic credential passing
  • Thoughtful UX: asks clarifying questions for ambiguous requests rather than loading wrong specialist
  • Well-scoped: delegates all heavy lifting to specialist skills, avoiding scope creep (incidental files don't expand task)
  • Comprehensive table covers 9 Logfire surfaces with clear decision logic
  • Detailed authentication guidance defers to external reference (auth.md) for actual credential handling
  • Clear pause points documented (browser auth, unresolved ambiguity, production cost, deploy changes)
  • Verified domain reference (pydantic.dev) for skill URLs is consistent and external-link appropriate
Model: claude-haiku-4-5-20251001Analyzed: Oct 17, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.0

    Contract changed: description

    ✦ AIAdds frontend observability, Application Gateway, and coding-agent routing; simplifies activation scope and auth workflow.

    triggering2026-10-17

    LATEST
  2. v1.0

    2026-10-13

    View This VersionInitial version

Use pydantic/logfire-setup in your dev environment

Command Palette

Search for a command to run...