Improve Prompt
AgentX-ai/AgentX-Trace-Eval
Propose an improved version of a prompt registered in a self-hosted AgentX (AgentX-trace-eval) instance, using real low-rated evaluation results as evidence, then publish it as a new version once…
Entry point for Pydantic Logfire — an observability, monitoring, and evals platform.
Install Logfire Setup
$ npx skills add pydantic/skills --skill logfire-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pydantic/skills logfire-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pydantic/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/logfire-setup .claude/skills/logfire-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "logfire-setup" agent skill from https://github.com/pydantic/skills/tree/main/skills/logfire-setup into .claude/skills/logfire-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logfire-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pydantic/skills/tree/main/skills/logfire-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pydantic/skills --skill logfire-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pydantic/skills logfire-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/logfire-setup .agents/skills/logfire-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "logfire-setup" agent skill from https://github.com/pydantic/skills/tree/main/skills/logfire-setup into .agents/skills/logfire-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logfire-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pydantic/skills --skill logfire-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pydantic/skills logfire-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/logfire-setup .cursor/skills/logfire-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "logfire-setup" agent skill from https://github.com/pydantic/skills/tree/main/skills/logfire-setup into .cursor/skills/logfire-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logfire-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pydantic/skills.git --path skills/logfire-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pydantic/skills --skill logfire-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pydantic/skills logfire-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/logfire-setup .gemini/skills/logfire-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "logfire-setup" agent skill from https://github.com/pydantic/skills/tree/main/skills/logfire-setup into .gemini/skills/logfire-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logfire-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pydantic/skills logfire-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pydantic/skills --skill logfire-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pydantic/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/logfire-setup .github/skills/logfire-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "logfire-setup" agent skill from https://github.com/pydantic/skills/tree/main/skills/logfire-setup into .github/skills/logfire-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logfire-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pydantic/skills --skill logfire-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pydantic/skills logfire-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pydantic/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/logfire-setup .opencode/skills/logfire-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "logfire-setup" agent skill from https://github.com/pydantic/skills/tree/main/skills/logfire-setup into .opencode/skills/logfire-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logfire-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
logfire-setup- GitHub stars
- 140
- Token cost
- ~1.5k tokens
- SKILL.md length
- 676 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Entry point for Pydantic Logfire — an observability, monitoring, and evals platform.
- Works in 3 steps: Authenticate and Select the Exact Project → Understand the Repo → Fetch the Right Skill(s)
- The user asks to set up Logfire
- SKILL.md covers Step 1: Authenticate and…, Step 2: Understand the Repo and Step 3: Fetch the Right Skill(s)
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Logfire Setup is an agent skill from pydantic/skills, published by the product's own GitHub organization. Entry point for Pydantic Logfire — an observability, monitoring, and evals platform. Use this skill when the user asks to "set up Logfire", "add Logfire to my project", "get me set up properly with Logfire", "send as much data as would be useful", mentions Logfire without a specific scope, or their request spans more than one of instrumenting application code / monitoring infrastructure / evaluating AI behavior. If the request is clearly scoped to exactly one of those, fetch that specific skill directly instead…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Observability and LLM evaluation. It works with Pydantic. The licence is MIT.
When your agent uses it
- The user asks to set up Logfire
- Add Logfire to my project
- Get me set up properly with Logfire
- Send as much data as would be useful
Example prompts
- “set up Logfire”
- “add Logfire to my project”
- “get me set up properly with Logfire”
- “/logfire-setup”
Requirements
- Python 3
- Node.js
- Docker
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 238d971. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
pydantic.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Logfire Setup loads about 1.5k tokens when it runs. Until then it costs about 151 tokens; SKILL.md has 676 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pydantic/skills at commit 238d971, republished under its MIT licence (© pydantic). 676 words, ~1,519 tokens.
Download SKILL.mdSave it as
.claude/skills/logfire-setup/SKILL.md (or your agent's skills folder).- name
- logfire-setup
- description
- Entry point for Pydantic Logfire — an observability, monitoring, and evals platform. Use this skill when the user asks to "set up Logfire", "add Logfire to my project", "get me set up properly with Logfire", "send as much data as would be useful", mentions Logfire without a specific scope, or their request spans more than one of instrumenting application code / monitoring infrastructure / evaluating AI behavior. If the request is clearly scoped to exactly one of those, fetch that specific skill directly instead of this one — this skill exists to route, not to duplicate their content.
Set Up Logfire
Logfire is an observability platform built on OpenTelemetry, with several distinct product surfaces. This skill authenticates, orients, and routes you to the specific skill for the surface you actually need — don't try to cover install/instrument/verify detail from within this file.
Keep the user informed with short updates, but proceed through ordinary, reversible setup without asking approval — no clean tree, branch, commits, or plan needed, and no commands the user could run only because you chose not to. Pause only for: browser auth, a genuinely ambiguous app/project after inspection, materially increasing production telemetry or cost, deploy/infra changes, or destructive/unrelated work — then ask one concrete question. Never report a check, a score, or a run as verified without having actually confirmed it in this session.
Step 1: Authenticate and Select the Exact Project
Auth comes first because everything after it depends on having a valid, confirmed connection to the exact right Logfire project: instrumenting or inspecting the repo before that is either wasted if the connection turns out wrong, or worse, ends up silently wired to the wrong project. Do not open, read, or run any project file until whoami confirms you're authenticated to the right project — nothing about this step requires knowing what's in the repo yet.
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 |
| 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 |
| AI Gateway | Spend caps, failover, and routing for model calls (logfire gateway) | no dedicated skill yet — see the product's own docs |
Show full SKILL.md (248 more words)Show less
- No specific scope given (e.g. "set up Logfire in this repo end to end")? Default to
logfire-instrumentationfor ordinary application code. Incidental Docker, Kubernetes, infrastructure, or eval files do not expand the initial setup: get one representative application service to verified first data, then offer the matching additional skill(s). If the repository is clearly infrastructure-only, route directly tologfire-infrastructureinstead. - 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)
Fetch the skill(s) identified in Step 2 now, for the actual install/instrument/verify steps. Each one's own authenticate step still runs its own whoami check first — that's what confirms it's the same project and region resolved here, not an assumption carried over — and only then skips the rest of its auth commands. They're independently fetchable on purpose, so this composes whether someone reaches a specific skill through this hub or on its own.
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.
© pydantic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/logfire-setup of pydantic/skills.
Open the folder on GitHubat commit 238d971
Compare with similar skills
Logfire Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Logfire Setup this skillpydantic/skills | 140 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Improve PromptAgentX-ai/AgentX-Trace-Eval | 106 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Inspectagentevals-dev/agentevals | 162 | — | ~534 | Automated safety check: Pass | Apache-2.0 | |
| Evevercel/vercel-plugin | 301 | 5 repos | ~1.2k | Automated safety check: Pass | Custom licence | |
| Secret Serializationgetsentry/skills | 1k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Agents Optimizeaws/agent-toolkit-for-aws | 2.8k | — | ~914 | Automated safety check: Notes | Apache-2.0 |
Similar skills
Inspect
agentevals-dev/agentevals
Inspect and debug live streaming agent sessions to understand what the agent did.
- Official
Eve
vercel/vercel-plugin
eve framework guidance for durable AI agents and agent-powered applications.
- Official
Secret Serialization
getsentry/skills
Finds secrets, tokens, passwords, and API keys that can leak through generated serialization: Python dataclass repr and asdict, attrs, pydantic modeldump, NamedTuple, JavaScript JSON.stringify and…
- Official
Agents Optimize
aws/agent-toolkit-for-aws
A skill your agent uses when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization.
Agent Observability Eval Bootstrap
datadog-labs/agent-skills
Bootstrap evaluators from production traces — by default propose online LLM-judge evaluators and, after you confirm, create them in Datadog as disabled drafts (never auto-enabled); on request emit…
More from pydantic/skills
All 9 skills in this repo- Official
Logfire Infrastructure
pydantic/skills
Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.
- Official
Logfire Query
pydantic/skills
Query and analyze Logfire telemetry data — traces, logs, spans, metrics, summaries, and SQL results.
- Official
Pydantic AI Harness
pydantic/skills
Extend Pydantic AI agents with batteries-included capabilities from pydantic-ai-harness -- Code Mode (collapse many tool calls into one sandboxed Python execution), a filesystem and shell…
- Official
Building Pydantic AI Agents
pydantic/skills
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns.
- Official
Logfire Evals
pydantic/skills
Run offline Python (pydanticevals) or Node.js (logfire/evals) evaluations and review them in Logfire.
- Official
Logfire Instrumentation
pydantic/skills
Add Pydantic Logfire observability to application code — traces, logs, metrics, and AI/agent spans.
Related
Works with
Categories
Questions about Logfire Setup
What does Logfire Setup do?
Entry point for Pydantic Logfire — an observability, monitoring, and evals platform. Logfire Setup is an agent skill from pydantic/skills, published by the product's own GitHub organization. Entry point for Pydantic Logfire — an observability, monitoring, and evals platform.
When should I use Logfire Setup?
Logfire Setup fits situations like: the user asks to set up Logfire; add Logfire to my project; get me set up properly with Logfire; send as much data as would be useful.
How do I install Logfire Setup in Claude Code?
Run `npx skills add pydantic/skills --skill logfire-setup -a claude-code`. Or copy the skill folder (skills/logfire-setup in pydantic/skills) into .claude/skills/logfire-setup in your project. Claude Code loads it when a task matches its description.
How do I install Logfire Setup in Codex?
Run `npx skills add pydantic/skills --skill logfire-setup -a codex`. Or copy the skill folder (skills/logfire-setup in pydantic/skills) into .agents/skills/logfire-setup in your project. Codex loads it when a task matches its description.
Can I use Logfire Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pydantic/skills --skill logfire-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logfire-setup, .gemini/skills/logfire-setup, .github/skills/logfire-setup and .opencode/skills/logfire-setup in your project.
What does Logfire Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Logfire Setup is instructions for the agent only. Our summary lists: Python 3; Node.js; Docker.
Does Logfire Setup access the network?
SKILL.md names 1 domain. As links in the text: pydantic.dev. This is read from the text; nothing was executed.
Is Logfire Setup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Logfire Setup use?
Logfire Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Logfire Setup use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Logfire Setup?
Skills that share tags, products or a category with Logfire Setup: Improve Prompt (AgentX-ai/AgentX-Trace-Eval, 106 stars), Inspect (agentevals-dev/agentevals, 162 stars), Eve (vercel/vercel-plugin, 301 stars) and Secret Serialization (getsentry/skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Logfire Setup?
pydantic (a GitHub organization, an official publisher) maintains it in pydantic/skills, which has 140 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.
Source: pydantic/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.