inspect-eval-log-analysis Skill
Guide for parsing and analyzing inspectai .eval log files. Use this when asked to interpret eval results, extract tool calls, find scores, or investigate agent behavior from .eval logs. Published by microsoft in ACESEvals.
Decision snapshot
Is this a fit?
Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is inspect-eval-log-analysis Skill?
Guide for parsing and analyzing inspectai .eval log files. Use this when asked to interpret eval results, extract tool calls, find scores, or investigate agent behavior from .eval logs. Published by microsoft in ACESEvals. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Declared skill metadata
- Source file: .github/skills/inspect-eval-log-analysis/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use inspect-eval-log-analysis Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/ACESEvals
- Skill file: .github/skills/inspect-eval-log-analysis/SKILL.md
What it does
Guide for parsing and analyzing inspectai .eval log files. Use this when asked to interpret eval results, extract tool calls, find scores, or investigate agent behavior from .eval logs.
Skill instructions
To parse and analyze inspectai .eval log files, follow this process: 1. Understanding the .eval File Format .eval files are ZIP archives (not plain text). They contain structured JSON: <hash.eval (ZIP) ├── header.json Eval metadata ├── journal/ │ ├── start.json Eval config, plan, model info │ └── summaries/ │ └── 1.json Per-epoch summary ├── samples/ │ └── <taskidepoch1.json Full sample data per task ├── summaries.json Aggregated score summaries └── reductions.json Score reduction results Never try to read .eval files as plain text. Always use zipfile: python import json, zipfile with zipfile.ZipFile("logs/<file.eval", "r") as zf: print(zf.namelist()) See all files inside 2. Extract Sample Data (Messages, Tool Calls, Scores) The richest data is in the samples/ JSON files. Each sample contains the full conversation: python import json, zipfile with zipfile.ZipFile("logs/<file.eval", "r") as zf: for name in zf.namelist(): if not name.startswith("samples/"): continue sample = json.loads(z
Verified compatibility and discovery
Frequently asked questions
What is inspect-eval-log-analysis?
inspect-eval-log-analysis is a open-source AI agent skill with Copy skill directory. Guide for parsing and analyzing inspectai .eval log files. Use this when asked to interpret eval results, extract tool calls, find scores, or investigate agent behavior from .eval logs.
Who is inspect-eval-log-analysis best for?
inspect-eval-log-analysis is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install inspect-eval-log-analysis?
Install or run inspect-eval-log-analysis using Copy skill directory. Check inspect-eval-log-analysis for the latest setup command.
Is inspect-eval-log-analysis actively maintained?
inspect-eval-log-analysis may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.