Telemetry reporting for agents within a Grove run environment.

Install

mkdir -p .claude/skills/grove-status && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17182" && unzip -o skill.zip -d .claude/skills/grove-status && rm skill.zip

Installs to .claude/skills/grove-status

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Emit runtime status onto the Grove bus while working as a gardener (or head-gardener) in a Grove run — so the maintainer's dashboard shows who is working, on what, and who is blocked. Use at role start, at every state transition (working/blocked/awaiting-gate/done/failed), when issuing a verdict, when parking a question, and poll for commands at step seams.
359 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • →Emit status when a role starts
  • →Report state transitions during a step
  • →Signal when blocked on a question
  • →Indicate waiting on a human gate
  • →Issue a gate or review verdict
  • →Poll for commands addressed to the agent

How it works

The skill executes `node ./emit.ts` with specific subcommands and arguments to send telemetry data to the Grove bus, reporting agent status and activity.

Inputs & outputs

You give it
subcommand, run ID, agent role, and activity/state details
You get back
status updates, questions, verdicts, or command acknowledgments on the Grove bus

When to use grove-status

  • →Emit status updates
  • →Report agent activity
  • →Track blocked tasks

About grove-status

Reports state changes, activity, and progress to a telemetry bus. Provides visibility into agent status without replacing artifact-based truth.

Emit runtime status onto the Grove bus while working as a gardener (or head-gardener) in a Grove run — so the maintainer's dashboard shows who is working, on what, and who is blocked. Use at role start, at every state transition (working/blocked/awaiting-gate/done/failed), when issuing a verdict, wh

When not to use it

  • →When artifact state is the source of truth
  • →When reporting progress not actually made
  • →When emitting fails due to a broken environment

Prerequisites

wisp installnode

Limitations

  • →The bus is telemetry, not truth
  • →Does not replace artifact state as the source of truth
  • →Requires a vendored wisp install

How it compares

This skill provides real-time visibility into agent activity and state via a telemetry bus, which is distinct from relying solely on artifact-based truth.

Compared to similar skills

grove-status side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
grove-status (this skill)03moReviewBeginner
system-info18moReviewBeginner
it-operations19moNo flagsAdvanced
pagerduty-automation07moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry