debug-live-issue
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
Configure and troubleshoot CCAM Remote Data Sources that collect Claude Code and Codex history over SSH. Use when adding, editing, testing, syncing, or removing a remote machine, verifying provider paths, or deciding whether to retain or purge imported sessions.
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill remote-collection --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/remote-collectionContext preview
The summary Claude sees to decide when to auto-load this skill.
Configure and troubleshoot CCAM Remote Data Sources that collect Claude Code and Codex history over SSH. Use when adding, editing, testing, syncing, or removing a remote machine, verifying provider paths, or deciding whether to retain or purge imported sessions.
name: remote-collection description: > Configure and troubleshoot CCAM Remote Data Sources that collect Claude Code and Codex history over SSH. Use when adding, editing, testing, syncing, or removing a remote machine, verifying provider paths, or deciding whether to retain or purge imported sessions.
1. List current sources with `ccam remote-sources`. 2. Validate the host through the user's existing SSH configuration. CCAM stores no passwords or private keys. 3. Add a source with `remote_home` and `remote_codex_home` only when they differ from the provider defaults. 4. Test before syncing: `ccam remote-sources test <id>`. 5. Sync one source or all sources with `ccam remote-sources sync [id]`. 6. Use `ccam remote-sources update <id> --file patch.json --yes` for edits. 7. Removal retains imported sessions by default. Purging them requires:
ccam remote-sources rm <id> --purge \ --confirm PURGE_REMOTE_SOURCE_DATA
Always state whether imported data will be kept or deleted before removal.
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.
Repo: hoangsonww/Claude-Code-Agent-Monitor
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored…
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or…
Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is…
Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and…