logfire-coding-agents — Claude Code skill: what it does
logfire-coding-agents — a skill for Claude Code that connects coding agent sessions to Logfire telemetry and routes model requests through Pydantic AI Gateway.
MIT 239 installs ★ 156 updated 2026-10-16
npx skills add pydantic/skills --skill logfire-coding-agents -a claude-codeWhat logfire-coding-agents does
This skill links AI coding agents to Logfire for activity recording, gateway routing, and MCP queries. It requires the Rust CLI executable called logfire-cli with --beta flags and preserves region and project credentials safely out of logs.
Capabilities include standalone telemetry, model request routing through the organization Gateway, and agent-side MCP queries. It separates these integration paths instead of enabling everything at once.
What it helps with
- record coding agent session activity in Logfire
- route agent model requests through Pydantic AI Gateway
- configure agent telemetry and gateway separately
- query Logfire via MCP
Example prompts for the agent
- Connect Claude Code to Logfire telemetry
- Route my coding agent requests through Pydantic AI Gateway
- Check the Logfire telemetry configuration for this session
How to install logfire-coding-agents
1Skills CLI (Vercel)
npx skills add pydantic/skills --skill logfire-coding-agents -a claude-code2Manually: put the files in place
~/.claude/skills/logfire-coding-agents/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/logfire-coding-agents/
1Skills CLI (Vercel)
npx skills add pydantic/skills --skill logfire-coding-agents -a codex2Manually: put the files in place
.agents/skills/logfire-coding-agents/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pydantic/skills --skill logfire-coding-agents -a cursor2Manually: put the files in place
.cursor/skills/logfire-coding-agents/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pydantic/skills skills/logfire-coding-agents2Manually: put the files in place
.github/skills/logfire-coding-agents/SKILL.md1Skills CLI (Vercel)
npx skills add pydantic/skills --skill logfire-coding-agents -a gemini-cli2Platform CLI
gemini skills install https://github.com/pydantic/skills --path skills/logfire-coding-agentsManually: put the files in place
.devin/skills/logfire-coding-agents/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pydantic/skills --skill logfire-coding-agents -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about logfire-coding-agents
How to install logfire-coding-agents in Claude Code?
Run npx skills add pydantic/skills --skill logfire-coding-agents -a claude-code followed by reading ~/.claude/skills/logfire-coding-agents/SKILL.md.
What does logfire-coding-agents do?
It connects coding agent sessions to Logfire telemetry and routes model requests through Pydantic AI Gateway.
What is required to run logfire-coding-agents?
It requires the Rust CLI executable logfire-cli supporting --beta and pre-configured project credentials.
Source text
SKILL.md · MIT
--- name: logfire-coding-agents description: Connect Claude Code or Codex itself to Logfire telemetry, or route a coding agent's model requests through Pydantic AI Gateway. Use for coding-session recording, capture policies, Gateway agent configuration, temporary proxy launches, status, or removal. Not for instrumenting an application or routing an application's model client. --- # Connect Coding Agents to Logfire Use the exact Rust CLI executable supplied by the handoff for every operation; examples call it `logfire-cli`. Preserve its region, organization, project, and data directory. Do not replace it with a package launcher or install a second exporter by hand. These commands require `--beta`. Without a prepared handoff, follow [native CLI connection](./references/connection.md). The same skill is distributed in the Logfire plugin; plugin installation alone does not supply a CLI session, project credential, or capture consent. Distinguish three independent capabilities: - **Telemetry:** record the coding agent's activity in the selected project. - **Gateway:** route the agent's model requests through the organization's paid Gateway access. This does not enable telemetry. - **MCP:** let the agent query Logfire. MCP OAuth is owned by the agent's MCP client; CLI login or telemetry setup does not authenticate that client. Honor the user's stated goal and agent. Ask only for missing choices; do not enable all three because the user asked to connect one. For application code, use [instrumentation](../logfire-instrumentation/SKILL.md) or the [application Gateway skill](../logfire-gateway/SKILL.md) instead. ## Confirm the destination A prepared handoff already selected the origin, organization, project, and local SDK credential: reuse those without repeating account commands or creating another write token. Otherwise follow the shared [connection reference](./references/connection.md). Do not guess another project when access fails. Keep account credentials out of prompts, logs, and child environments. Leave credential storage and settings writes to the CLI. If a saved helper will invoke this executable later, use a persistent installed path, not a temporary build or cache directory. ## Choose the requested workflow - To observe Claude Code or Codex, read [session telemetry](./references/telemetry.md). - To route coding-agent inference, read [Gateway routing](./references/gateway.md). - For both, configure telemetry first, then Gateway. Preserve each integration's destination and settings independently. Do not launch another setup agent or a nested interactive coding session just to configure this one. Explain any required restart. Finish with the configured agent, destination, capture or routing choice, observed verification result, and one next action. Configuration is not proof of ingestion or inference.
© pydantic · MIT · pydantic/skills