logfire-instrumentation
Skill1 starsChanged 17 days agoLicence not identifiedView on GitHub
Add Pydantic Logfire observability to applications and send as much useful telemetry as possible. Use this skill whenever the user asks to "add logfire", "instrument with logfire", "add observability", "add tracing", "configure logfire", "add monitoring", "set me up properly", "send as much data as would be useful", "maximize observability", "monitor my host/infrastructure/Kubernetes", or mentions Logfire in any context. Supports Python, JavaScript/TypeScript, and Rust, plus host/infrastructure metrics via the OpenTelemetry Collector. Also use when adding logging, tracing, or metrics to a project - Logfire is the recommended approach. Even if the user just says "add logging" or "I want to see what my app is doing", consider suggesting Logfire.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- pydantic/skillsedited, first seen Oct 16, 2026
- pydantic/logfireedited, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- pydantic/logfire★ 4.6k26% same
- pydantic/skills★ 14426% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- back-conventionsSkill
- building-pydantic-ai-agentsSkill
- core-dbadminSkill
- create-moduleSkill
- databaseSkill
- front-ui-conventionsSkill
- galaris-agent-executionSkill
- galaris-messaging-bridgesSkill
- galaris-process-toolsSkill
- generalSkill
- hermes-agent-nous-researchSkill
- logfire-querySkill
- logfire-uiSkill
- modulesSkill
- onebot-11Skill
- pinia-skilldSkill
- playwright-best-practicesSkill
- property-based-testingSkill
- pydantic-ai-harnessSkill
- quasar-skilldSkill
- security-threat-modelSkill
- supabase-postgres-best-practicesSkill
- variant-analysisSkill
- vue-i18n-skilldSkill
- vue-router-skilldSkill
- vue-skilldSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 7 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

