transaction-trace-analysis
Teaches evidence-based analysis of transaction logs and traces. Use when reconstructing transaction behavior from tables, TSV/CSV files, timestamps, counters, object histories, validation records, abort records, retries, partial logs, or when producing classified transaction outputs from trace evidence.
Best for data forensicsWorks with GitHubLow risk
⌘source
- author
@benchflow-ai- language
- PDDL
★1.1kstars
279forks
May 5, 2026
✦overview.md
Key Features
- ·Reconstruct transaction intent from logs
- ·Normalize columns into stable event vocabulary
- ·Join events using explicit fields
- ·Produce auditable classification outputs
- ·Per-key version timeline reconstruction
Use Cases
- →Investigate partial transaction logs to identify failures
- →Classify transaction outcomes from TSV/CSV trace files
- →Reconstruct object history from write/validation records
Best for
- ✓data forensics
- ✓post-mortem analysis
- ✓quality assurance teams
Not ideal for
- !real-time monitoring
- !stream processing without stored logs
FAQs
name
transaction-trace-analysis
description
Teaches evidence-based analysis of transaction logs and traces. Use when reconstructing transaction behavior from tables, TSV/CSV files, timestamps, counters, object histories, validation records, abort records, retries, partial logs, or when producing classified transaction outputs from trace evidence.
Transaction Trace Analysis
Use this skill when the task provides concrete logs, tables, counters, timestamps, or partial records and asks you to infer transaction behavior.
This skill is about reconstruction under partial evidence:
- normalize columns into a stable event vocabulary
- reconstruct per-transaction intent and per-object version timelines
- join them through explicit fields (not through row order guesses)
- produce a minimal, auditable classification for the required output
Quick Reference (pick the next file to read)
| If you need… | Read |
|---|---|
| Mapping weird columns into tx/key/op/timestamp/counter/status/reason | trace-schema-normalization.md |
| Grouping events per transaction and avoiding “attempt vs request” mixups | transaction-history-reconstruction.md |
| Reconstructing a per-key version timeline from writes/validation | object-version-history.md |
| Interpreting timestamp/counter semantics and scope correctly | timestamp-and-ordering-fields.md |
$install
1-click copynpx skills add benchflow-ai/skillsbench --skill transaction-trace-analysisSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.