event-log-tracing SKILL.md skillA
event-log-tracing from baphuongna/pi-crew is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add baphuongna/pi-crew/event-log-tracing@git:20260911.c97bc57Pins git:20260911.c97bc57 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baphuongna/pi-crew
- Path
skills/event-log-tracing/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260911.c97bc57, committed Sep 11, 2026
- First version recorded
- May 14, 2026
- Size
- 11,433 bytes
- Repository stars
- 59
- License
- MIT
Structured event logging for worker lifecycle, live agents, crash recovery. When NOT to use: high-level metrics dashboards (use observability-reliability); for runtime state inspection (use runtime-state-reader).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# event-log-tracing
Every pi-crew run writes a persistent event log at `.crew/state/runs/<runId>/events.jsonl`. Events are the primary evidence for understanding what happened — especially when workers crash, agents get stuck, or runs become orphaned.
## Event Format
Every event is a JSON object on one line:
```json
{
"time": "2026-05-14T10:27:52.000Z",
"type": "worker.spawned",
"runId": "team_20260514092752_218fe358085d7115",
"taskId": "01_explore",
"message": "Worker spawned: pid 12345",
"data": { "pid": 12345, "role": "explorer" },
"metadata": {
"seq": 42,
"provenance": "team_runner",
"fingerprint": "a1b2c3d4e5f6g7h8"
}
}
```
**Required fields:** `time`, `type`, `runId`
**Optional fields:** `taskId`, `message`, `data`, `metadata`
**Metadata auto-populated:** `seq` (line number), `provenance` (who wrote it), `fingerprint` (for terminal events)
## Event Taxonomy
### Worker Lifecycle Events (from child-pi.ts via onLifecycleEvent callback)
| Event | When | Data |
|---|---|---|
| `worker.spawned` | Child process starts with a PID | `{pid, cwd}` |
…Read the whole file at its exact version.
How to install
mdr add baphuongna/pi-crew/event-log-tracing@sha256:c69af39dbce729b7The line at the top of this page pins the label git:20260911.c97bc57, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bcfrjz2z5zudjhgr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between May 14, 2026 and Sep 11, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.c97bc57 latest | 2026-09-11 | c97bc57 | 11,433 B | A | view · diff |
| git:20260603.fa30bc0 | 2026-06-03 | fa30bc0 | 11,291 B | A | view · diff |
| git:20260529.53de3c2 | 2026-05-29 | 53de3c2 | 11,275 B | A | view · diff |
| git:20260528.67ddbec | 2026-05-28 | 67ddbec | 11,348 B | A | view · diff |
| git:20260526.80df5e6 | 2026-05-26 | 80df5e6 | 10,777 B | A | view · diff |
| git:20260514.81c1e55 | 2026-05-14 | 81c1e55 | 10,708 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11433 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
baphuongna/pi-crew · 59 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bcfrjz2z5zudjhgr GET https://markdownregistry.com/api/v1/resolve?ref=baphuongna/pi-crew/event-log-tracing GET https://markdownregistry.com/api/v1/blob/c69af39dbce729b760965785bdd3229ceb2a1976b4701e22047f6c66c7c962de
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.