smithers-events

Query run event history with filters, grouping, and NDJSON output. Run `smithers events --help` for usage details.

Repositorio: smithersai/smithers
Última actividad en el origen: 13 de julio de 2026 a las 04:41
Idioma detectado de SKILL.md: inglés
Estrellas: 404
Forks: 50

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/smithersai/smithers --skill smithers-events

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

smithers

Drive Smithers, a durable control plane for long-running coding agents, from Claude Code. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work ('orchestrate agents', 'run a workflow', 'implement this and review it', 'keep iterating until tests pass', 'plan then build') or anything needing retries, approvals, replay, or evals across multiple AI steps. YOU (Claude) run Smithers on the user's behalf; it is not a GUI the human clicks. HARD RULE 0, if `SMITHERS_INSIDE_RUN` is set in your environment you are ALREADY a worker agent inside a Smithers node, so never invoke the Smithers CLI or MCP tools to launch or steer a run, just do the node's task directly with your ordinary tools; every rule below applies only when it is unset. HARD RULE 1, right-size the route FIRST, handle ANY clear single-goal ask directly, even a large repo-wide one, and reserve a full workflow for work that genuinely needs ordered stages, durability, approvals, loops, or reuse; never author a multi-no

2026-08-27

smithers

Drive Smithers, a durable control plane for long-running coding agents, from Codex. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work ("orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build") or anything needing retries, approvals, replay, or evals across multiple AI steps. YOU (Codex) run Smithers on the user's behalf; it is not a GUI the human clicks. HARD RULE 0: if `SMITHERS_INSIDE_RUN` is set in your environment you are ALREADY a worker agent inside a Smithers node — never invoke the Smithers CLI or MCP tools to launch or steer a run, just do the node's task directly with your ordinary tools; every rule below applies only when it is unset. HARD RULE 1: right-size the route FIRST, handle a clear well-scoped single-goal task directly, and reserve a full workflow for work that genuinely needs ordered stages, durability, approvals, loops, or reuse. A workflow that runs long, fans out, or pauses on

2026-08-27

smithers

Drive Smithers, a durable control plane for long-running coding agents. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work: "orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build", or anything that needs retries, approvals, replay, or evals across multiple AI steps. YOU (the agent) run Smithers on the user's behalf; it is not a GUI the human clicks. HARD RULE 0: if `SMITHERS_INSIDE_RUN` is set in your environment you are ALREADY a worker agent inside a Smithers node, so never invoke the Smithers CLI or MCP tools to launch or steer a run; do the node's task directly with your ordinary tools. Everything below applies only when it is unset. You are otherwise an ORCHESTRATOR: run long-running, multi-step, or background work *through* Smithers, not through your own ad-hoc subagents; spend your time observing the run and reporting. Also governs DELIVERABLE SHAPE even when no workflow is involved: a user

2026-08-27

Ver todos los de este repositorio

name	smithers-events
description	Query run event history with filters, grouping, and NDJSON output. Run `smithers events --help` for usage details.
requires_bin	smithers
command	smithers events

smithers events

Query run event history with filters, grouping, and NDJSON output.

Arguments

Name	Type	Required	Description
`runId`	`string`	yes	Run ID to query

Options

Flag	Type	Default	Description
`--node`	`string`		Filter events by node ID
`--type`	`string`		Filter by event category (agent, approval, frame, memory, node, openapi, output, revert, run, sandbox, scorer, snapshot, supervisor, timer, token, tool-call, workflow)
`--since`	`string`		Filter to a recent duration window (e.g. 5m, 2h; a bare number is milliseconds, and `logs --since` is an event sequence number instead)
`--limit`	`number`		Maximum events to display (default 1000, max 100000)
`--json`	`boolean`	`false`	Output NDJSON for piping
`--groupBy`	`string`		Group output by "node" or "attempt"
`--watch`	`boolean`	`false`	Watch mode: append new events as they arrive
`--interval`	`number`	`2`	Watch poll interval in seconds

smithers-events

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

smithers events

Arguments

Options

smithers events

Arguments

Options