Install
$ agentstack add skill-zig999-siegard-code-orch-log ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
orch-log
Event log skill: append, read, and verify the orchestration JSONL log.
scripts/append.py
Emits an event to the append-only log with lock, hash chain, and schema validation.
Usage
python3 .claude/skills/orch-log/scripts/append.py \
--agent \
--event-type \
[--task-id ] \
[--attempt ] \
[--data '']
Parameters
| Parameter | Required | Description | |-----------|----------|-------------| | --agent | Yes | Agent identifier emitting the event | | --event-type | Yes | Event type (see valid types below) | | --task-id | No | Task ID (omit for phase/workflow events) | | --attempt | No | Attempt number, default 1 | | --data | No | JSON object payload, default {} |
Output
On success (exit 0): JSON object of the created event written to stdout.
On error (exit 1): JSON error envelope:
{"status": "error", "reason": "", "detail": ""}
Error reason codes:
invalid_json—--datais not valid JSON or not an objectunknown_event_type—--event-typenot in the 21-type enumvalidation_error— payload fails schema validationinternal_error— unexpected I/O or lock failure
Example
python3 .claude/skills/orch-log/scripts/append.py \
--agent orchestrator \
--event-type task_created \
--task-id t_001 \
--data '{"phase":"dev","tier":"standard","type":"impl","spec":"implement X","deps":[]}'
scripts/read.py
Reads events from the log with optional filters. Each matching event is printed as one JSON line to stdout.
Usage
python3 .claude/skills/orch-log/scripts/read.py \
[--from-seq N] \
[--tail N] \
[--task-id ] \
[--event-type ] \
[--phase ]
Parameters
| Parameter | Description | |-----------|-------------| | --from-seq N | Return events with seq >= N (default: 0 = all) | | --tail N | Return only the last N events (applied after other filters) | | --task-id | Filter by task ID | | --event-type | Filter by event type | | --phase | Filter by data.phase field |
Multiple filters are applied as AND. Output: one JSON object per line (empty output = no matches). Exit 0 on success, 1 on corrupted log.
Examples
# All events
python3 .claude/skills/orch-log/scripts/read.py
# Last 20 events
python3 .claude/skills/orch-log/scripts/read.py --tail 20
# All task_created events in phase dev
python3 .claude/skills/orch-log/scripts/read.py --event-type task_created --phase dev
scripts/verify.py
Verifies hash-chain integrity of the log. Output is a single JSON object.
Usage
python3 .claude/skills/orch-log/scripts/verify.py [--mode strict|audit]
Modes
| Mode | Behavior | Exit code | |------|----------|-----------| | strict (default) | Stops at first error | 0 ok, 1 error | | audit | Collects all errors, never modifies log | Always 0 |
Output schema
{
"ok": true,
"message": "...",
"mode": "strict",
"events_verified": 42,
"first_error_seq": null,
"error_details": []
}
Use audit for investigation; use strict at orchestrator startup (architecture rule R1).
Valid event types
Task lifecycle (8):
task_created task_claimed task_progress task_completed
task_failed task_scheduled_retry task_retried task_dlq
Phase lifecycle (7):
phase_declared phase_entered phase_exit_criterion_met
phase_exit_approved phase_transitioned phase_paused
phase_resumed
Management and operations (6):
circuit_breaker_tripped escalation human_response
snapshot log_recovered preflight_failed
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zig999
- Source: zig999/siegard-code
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.