What does the status output include?

It prints the full cobrain daemon status, including version, processes, permissions, and recent activity, exactly as produced by the status.sh script.

What happens if status.sh is not found?

The command prints "status.sh not found" and exits with an error.

Can I customize or filter the output?

No; the skill shows the raw output exactly as the status.sh script outputs it.

status

npx machina-cli add skill cyrus-cai/claude-cobrain/status --openclaw

Files (1)

SKILL.md

756 B

status

Run the status script and show the output to the user. Do not reformat or summarize — just display the raw output.

if [[ -n "${CLAUDE_PLUGIN_ROOT:-}" && -f "${CLAUDE_PLUGIN_ROOT}/scripts/status.sh" ]]; then
  STATUS_SCRIPT="${CLAUDE_PLUGIN_ROOT}/scripts/status.sh"
elif [[ -f "./plugin/scripts/status.sh" ]]; then
  STATUS_SCRIPT="./plugin/scripts/status.sh"
else
  STATUS_SCRIPT="$(ls -dt "$HOME"/.claude/plugins/cache/*/claude-cobrain/*/scripts/status.sh 2>/dev/null | head -1)"
fi
[[ -n "${STATUS_SCRIPT:-}" && -f "$STATUS_SCRIPT" ]] || { echo "status.sh not found"; exit 1; }
bash "$STATUS_SCRIPT"

Source

git clone https://github.com/cyrus-cai/claude-cobrain/blob/main/plugin/skills/status/SKILL.mdView on GitHub

Overview

Shows the full cobrain daemon status, including version, running processes, permissions, and recent activity, by executing the status.sh script. The output is delivered as-is to support debugging and auditing.

How This Skill Works

The skill locates status.sh by checking CLAUDE_PLUGIN_ROOT/scripts/status.sh, then plugin/scripts/status.sh, or a cached path under the home plugins cache. It then runs the status script with bash and returns the exact raw output without reformatting.

When to Use It

You need a full snapshot of the cobrain daemon state for troubleshooting.
After a restart or deployment, to confirm the daemon is healthy and up.
Auditing file permissions and ownership of cobrain components.
Documenting recent daemon activity for incident reports.
Verifying which status.sh path was used when troubleshooting script location issues.

Quick Start

Step 1: Ensure status.sh is discoverable (CLAUDE_PLUGIN_ROOT/scripts/status.sh, ./plugin/scripts/status.sh, or a cached path).
Step 2: Trigger the status skill to execute the script.
Step 3: Read the raw, unmodified output exactly as produced.

Best Practices

Ensure status.sh is accessible by the plugin (check CLAUDE_PLUGIN_ROOT, the local plugin path, or the cached home path).
Do not modify or scrub the raw output; use it as evidence for debugging.
Run with sufficient permissions to view processes and file metadata.
Keep status scripts up to date as the cobrain plugin evolves.
Avoid sharing raw outputs publicly; handle sensitive information securely.

Example Use Cases

A developer verifies version and running processes after pulling a new cobrain plugin.
A sysadmin checks permissions following a deployment to ensure correct access.
QA captures the raw status output to reproduce a startup issue.
An operator confirms the daemon is active right after a restart.
An auditor collects the status to demonstrate system health during a compliance review.

Frequently Asked Questions

Add this skill to your agents