agentleFS
Sign inStart free
drewid74drewid74/ai_skills/karpathy-trace-infrastructure/SKILL.md

karpathy-trace-infrastructure

Skill8 starsChanged 6 months agoNo licenceView on GitHub

Use this when: audit my agent observability, do I have enough logging for auto-improvement, trace infrastructure readiness, can a meta-agent read my agent's reasoning, agent trace audit, do I have full reasoning traces, tool call logging, decision point visibility, structured trace format, session reproducibility for agents, agent harness version control, baseline snapshots for optimization, failure classification in traces, cost and latency tracking per agent step, sandboxed execution environment, agent evaluation harness, LangSmith setup, Braintrust setup, Arize setup, am I logging enough for a meta-agent, what traces does auto-improvement need, agent observability gaps, trace infrastructure gaps, auto-improvement infrastructure readiness, meta-agent trace requirements, agent replay from logs, is my logging sufficient for optimization loop

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — 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 350,495 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free