1. Habit
  2. Skills
  3. Logfire Instrumentation skill
pydantic · 2K installs

Logfire Instrumentation skill
Runs by itself, next service to instrument.

One more service sending real traces.

Install the Logfire Instrumentation skill and make it a habit: follow https://gethabit.dev/skills/pydantic/logfire-instrumentation.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

2K installs144 starsMIT licenceSource on GitHub ↗

Logfire Instrumentation

by pydantic · 2K installs

The skill

The logfire instrumentation skill helps developers add Pydantic Logfire traces, logs, metrics and AI agent spans to Python, JavaScript and Rust apps, and verify real data arrived.

Only when you ask.

The habit

One more service sending real traces.

↻ Runs by itselfnext service to instrument

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

next service to instrument. Runs in Claude Code routine.

  • ↻ next service to instrument
  • run when you pick the next service from the board

02

It checks its work

fresh data queried in Logfire. If a check fails, it tries again.

  • ✓whoami reports the intended project
  • ✓projects status --json shows fresh data for the service
  • ✓service.name is not unknown_service
  • ✓no LOGFIRE_TOKEN or write token appears in client-side code

03

It remembers

services to instrument. The next run reads it first: services already verified and the next one to do.

loops/logfire-coverage-loop/board.md

One run, step by step.
Then it stops.

Stop ruleStops after one verified service per run, with at most 2 fix rounds.

  1. 01

    Authenticate

    Run the target-aware whoami check first; browser sign-in may need you.

  2. 02

    Detect stack

    Read pyproject.toml, package.json or Cargo.toml and pick one representative service.

  3. 03

    Instrument

    Install logfire with the matching extras and call configure() before any instrument_*() call.

  4. 04

    Set metadata

    Set service.name, service.version and deployment.environment.name.

  5. 05

    Verify

    Run a real request and query projects status --json for fresh data, then audit nesting and names.

  6. 06

    Report and ask

    Report the project URL and real values, then ask whether to do the next service.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Logfire Instrumentation skill helps.

Use it when

  • ✓ You add tracing to an app
  • ✓ You instrument an AI agent framework
  • ✓ Traces are not showing up

Skip it when

  • – You only monitor hosts or containers
  • – You evaluate agents against test datasets

Questions

Logfire Instrumentation skill, answered.

Why one service at a time?

The skill asks to verify first data for one service before touching another.

Does it cover hosts and databases?

No. Infrastructure metrics belong to the logfire-infrastructure skill.

How do I install the Logfire Instrumentation skill?

Copy the prompt at the top into your agent. It installs the skill from pydantic/skills and sets up the habit. Or run npx skills add pydantic/skills --skill logfire-instrumentation.

Is the Logfire Instrumentation skill free?

Yes. It is published under MIT. Habit is free too.

Logfire Instrumentation. Now as a habit.

Install the Logfire Instrumentation skill and make it a habit: follow https://gethabit.dev/skills/pydantic/logfire-instrumentation.md

  • Free
  • No account
  • Undo in one line

All pydantic skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by pydantic, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.