Status
npx machina-cli add skill Speedy0000007/claude-tandem/status --openclawTandem Status
Run the status script and output the result. No preamble, no follow-up — just the script output.
CLAUDE_PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}" "${CLAUDE_PLUGIN_ROOT}/scripts/status.sh" "$(pwd)"
If rules files are missing, offer to re-provision by deleting ~/.tandem/.provisioned and restarting a session (ask first — user may have intentionally disabled a feature).
Source
git clone https://github.com/Speedy0000007/claude-tandem/blob/main/plugins/tandem/skills/status/SKILL.mdView on GitHub Overview
Tandem Status runs the status script to reveal installed features, verify that hooks are configured correctly, and display profile and memory stats. It outputs the results with no preamble or follow-up. If rules files are missing, it can prompt you to re-provision by deleting ~/.tandem/.provisioned and restarting a session (ask first).
How This Skill Works
It invokes the status.sh script from the plugin root using CLAUDE_PLUGIN_ROOT as the base. The output is the script result with no extra preamble. If rules files are missing, it may prompt for re-provision by removing ~/.tandem/.provisioned and restarting a session (with user confirmation).
When to Use It
- To check installed features
- To verify hooks are configured correctly
- To see profile and memory stats
- After installation or update to confirm setup
- During troubleshooting when provisioning rules appear missing
Quick Start
- Step 1: CLAUDE_PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}" "${CLAUDE_PLUGIN_ROOT}/scripts/status.sh" "$(pwd)"
- Step 2: Review the script output for features, hooks, profile, and memory stats
- Step 3: If rules files are missing, ask to re-provision by deleting ~/.tandem/.provisioned and restarting a session
Best Practices
- Run the status script from the plugin root using CLAUDE_PLUGIN_ROOT to ensure correct paths
- Read the output to confirm installed features, hooks, profile, and memory stats
- If rules files are missing, offer re-provision by deleting ~/.tandem/.provisioned and restarting a session after user confirmation
- Expect only the script output with no preamble or follow-up
- Use after changes to the plugin to verify the environment is healthy
Example Use Cases
- User asks which Tandem features are installed; status lists them
- Developer troubleshoots by verifying hooks are configured correctly via status
- Admin reviews a user's profile and memory statistics using status
- New installation run status to confirm provisioning and feature availability
- Status indicates missing rules and prompts for re-provisioning
