build-event-log
Turn data a user already has into an event log for process mining - a CSV of case, activity and timestamp rows that pmx reads with no flags - from Salesforce history, Jira or Linear changelogs, GitHub pull requests, Claude Code sessions, or a spreadsheet of status dates, then check it can be mined. Use when someone wants to see how their deals, tickets, orders or PRs actually flow but has no event log yet. Not for mining an existing log - that is pmx-process-mining.
- Compatibility
- Requires python3 for the readiness check, and access to the source system - a connector, an authenticated CLI such as gh, or an export from the user.
Pinned to revision fa8aea04a9d6, so it is the text this page describes rather than whatever the author pushed since.
Pre-approved tools experimental
Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.
- Bash(python3:*)
- Bash(gh:*)
- Read
- Write
- Glob
Files
- skills/build-event-log/SKILL.md
- skills/build-event-log/references/sources.md
- skills/build-event-log/scripts/check_log.py
Every link opens the file at its source, pinned to the revision this page describes.