with one click
channelhub
channelhub contains 10 collected skills from mahdi-awadi, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Run Playwright browser tests against the channelhub web dashboard. Use when validating UI changes (kebab menu, autopilot toggle, escalation card, settings panels) — the SPA has zero coverage from bun:test alone.
Snapshot a channelhub session's tmux pane PLUS its recent autopilot errors and registry state in one structured dump. Use when the user reports an autopilot/permission/spawn problem on a specific session, or when you need fast forensic context before forming a hypothesis.
Run an end-to-end autopilot test in a disposable /tmp project — spawn a Claude session, enable autopilot, fire a known prompt, capture the response, tear down. Use when validating an autopilot code change without disturbing the user's real sessions.
Fetch current documentation for libraries used in channelhub (Bun, grammy, MCP SDK, Playwright, bun:sqlite, etc.). Prefer Context7 when installed; fall back to WebFetch against the canonical doc site. Use when the user asks "how does X API work" or you're about to call an unfamiliar library method.
Restart the channelhub hub-daemon tmux session cleanly and verify it came back up. Use when the user asks to restart the daemon, when code changes need to take effect, or when sessions are showing as disconnected and you suspect the daemon is wedged.
Poll the Anthropic plugin marketplace manifest until "channelhub" appears, then notify the user. Use when waiting for the security review to land — the submission portal shows "Published" before the public manifest is updated.
Re-run the bun:test suite (and optionally the Playwright suite) on a loop, surfacing only failures. Use during long refactors or autopilot tuning where you want continuous green-light confirmation.
Set up autopilot mode for a channelhub project. Use when the user wants to configure how their project answers questions on their behalf — specifically which preferences the proxy should honor.
Manage hub access — view allowed users, add or remove Telegram user IDs from the allowlist. Use when the user asks about who can access the hub or wants to change access.
Set up the hub — save the bot token, web port, and configure access. Use when the user wants to configure the hub, set a Telegram token, or check channel status.