Show enriched node details for debugging retries, tool calls, and output. Run `smithers node --help` for usage details.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add smithersai/smithers --skill smithers-node --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Smithers Node?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/smithersai-smithers-node)More formats (shields.io, HTML) on the badges page.
---
name: smithers-node
description: Show enriched node details for debugging retries, tool calls, and output. Run `smithers node --help` for usage details.
requires_bin: smithers
command: smithers node
---
# smithers node
Show enriched node details for debugging retries, tool calls, and output.
## Arguments
| Name | Type | Required | Description |
|------|------|----------|-------------|
| `nodeId` | `string` | yes | Node ID to inspect |
## Options
| Flag | Type | Default | Description |
|------|------|---------|-------------|
| `--runId` | `string` | | Run ID containing the node |
| `--iteration` | `number` | | Loop iteration number (default: latest iteration) |
| `--attempts` | `boolean` | `false` | Expand all attempts in human output |
| `--tools` | `boolean` | `false` | Expand tool input/output payloads in human output |
| `--watch` | `boolean` | `false` | Watch mode: refresh output continuously |
| `--interval` | `number` | `2` | Watch refresh interval in seconds |
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', ...
