Tail the event log of a specific run. Run `smithers logs --help` for usage details.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add smithersai/smithers --skill smithers-logs --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Smithers Logs?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/smithersai-smithers-logs-smithers)More formats (shields.io, HTML) on the badges page.
---
name: smithers-logs
description: Tail the event log of a specific run. Run `smithers logs --help` for usage details.
requires_bin: smithers
command: smithers logs
---
# smithers logs
Tail the event log of a specific run.
## Arguments
| Name | Type | Required | Description |
|------|------|----------|-------------|
| `runId` | `string` | yes | Run ID to tail |
## Options
| Flag | Type | Default | Description |
|------|------|---------|-------------|
| `--follow` | `boolean` | `true` | Keep tailing (default true for active runs) |
| `--fromSeq` | `number` | | Start from event sequence number (exclusive) |
| `--since` | `number` | | Deprecated alias of --from-seq: an event SEQUENCE NUMBER, not a duration (`events --since` takes a duration window like 5m) |
| `--tail` | `number` | `50` | Show last N events first |
| `--followAncestry` | `boolean` | `false` | Include events from ancestor runs (continuation lineage) |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
