AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Agent Status

skill-enbiyagoral-claude-agent-status · by enbiyagoral

>

No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-enbiyagoral-claude-agent-status

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-enbiyagoral-claude-agent-status)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Agent Status? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Agent status

Target agent: $ARGUMENTS

Step 1 — Validate

  • If no argument given → stop and ask: "Which agent? Run /list-agents to see available agents."
  • Glob .claude/agents// — if directory doesn't exist, stop and say agent not found.
  • This skill only works for Type B autonomous agents (folder structure). Type A subagents have no journal or outputs.

Step 2 — Read agent state

Read the following files in order:

  1. .claude/agents//AGENT.md — extract: Mission, Goals & KPIs table
  2. .claude/agents//MEMORY.md — extract: "What Works" and "Last Updated" sections
  3. .claude/agents//outputs/ — Glob for all files, sort by name (date-prefixed), take the 3 most recent
  4. journal/ — Glob for all files, sort by name, take the most recent entry that mentions this agent name

Step 3 — Summarize

Output:

===  status ===

Mission: 

KPI Progress:
  •  | KPI:  | Baseline:  | Target:  | Current: 

Last activity:
  • Journal:  — 
  • Last output:  ()

Memory (what's working):
  

Last updated: 

If journal/ is empty or has no entries mentioning this agent → print: "No journal entries found. Has the first cycle run yet?"

If outputs/ is empty → print: "No outputs generated yet."

Notes

  • Do NOT read all journal files — only the most recent one that mentions the agent name
  • Current KPI value comes from the most recent output file or journal entry — if not found, show "unknown"

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.