trace-codes
From the author
Turn free-form notes from reading agent traces into trace codes: named, yes/no failure or quality patterns with definitions, examples and counts. Use this skill whenever someone has annotated traces or review notes and asks to "cluster my notes", "create trace codes", "find the failure modes", "do error analysis on these annotations", "what patterns are in these traces", or "what should we fix first". Also use to merge new notes into an existing set of codes. Output is a trace codes file, a labeling sheet for human review, and proposed rubric updates.
Install
npx skills add Calibre-Labs/reforge-ai-evals --skill trace-codes -a claude-code
Installs to .claude/skills/trace-codes/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- trace-review-appCalibre-Labs/reforge-ai-evalsDesign and build a custom trace review app for one AI product: a single-page tool where the team reads traces, writes notes, labels pass or fail, tags trace codes and exports the results for other skills. Built around that product's own trace shape, rubric and failure modes, and set up so reviewing becomes a habit (a queue, progress, streaks, quick keys). Use this skill whenever someone asks to "build a trace viewer", "make an annotation tool", "set up a review page for our traces", "make trace review less painful", "build a labeling app", or says the team isn't reading traces because the tool is clunky.Engineering★ 85
- taste-code-reviewmadebymustafa/design-tasteStructured review of agent-generated code: a fixed pass order (behavior → structure → taste → security → performance → accessibility), severity-ranked findings, diff discipline, and a review checklist that stops "it works" from being the bar. Use when auditing any generated or changed code. Stack on the design-taste core skill.Engineering★ 196
- review-codetobihagemann/turboReview code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps and low-value tests by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argument. Use when the user asks to "review my code", "full code review", "review my changes", "check for bugs", "scan for bugs", "review correctness", "security audit", "find vulnerabilities", "review security", "check API usage", "verify against docs", "check for cross-file duplication", "review consistency", "check for code reuse", "review simplicity", "find untested code", "find redundant tests", or "review test coverage".Engineering★ 416
- trace-debugtonone-ai/tononeDebug AI system behavior using traces — prompt reconstruction, output comparison, failure attribution. Use when asked "why did the model output this", "debug this LLM failure", or "reconstruct the prompt".Engineering★ 76
- refactoring-patternswondelai/skillsApply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation fits a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code-quality foundations, see clean-code. For managing complexity, see software-design-philosophy.Engineering★ 2.5K
- make-traceAIScientists-Dev/FlowtraceTurn any source that describes how a kind of task gets done (a SKILL.md, a chat log, a runbook, plain prose) into a runnable Morph trace. Lift it into a DAG, write a contract per step, place inputs, and drive the full run lifecycle to verify it. Use whenever someone wants to make a trace from a source.Legal★ 484
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in