hooman-channels

Stars14

Forks0

UpdatedJuly 17, 2026 at 04:43

Add and configure Hooman channel MCP servers for cron, Slack, Telegram, WhatsApp, and Jira in ~/.hooman/mcp.json. Use when the user asks for scheduled or recurring prompts, cron jobs, messaging-app or chatbot integration, inbound webhooks, daemon automation, or connecting any event-driven channel to a Hooman agent or daemon. For ordinary (non-channel) MCP server edits use hooman-mcp.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

vaibhavpandeyvpz

vaibhavpandeyvpz/hooman

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

2 files

SKILL.md

readonly

name	hooman-channels
description	Add and configure Hooman channel MCP servers for cron, Slack, Telegram, WhatsApp, and Jira in ~/.hooman/mcp.json. Use when the user asks for scheduled or recurring prompts, cron jobs, messaging-app or chatbot integration, inbound webhooks, daemon automation, or connecting any event-driven channel to a Hooman agent or daemon. For ordinary (non-channel) MCP server edits use hooman-mcp.

Hooman Channels

Use this skill when the user asks to add channel-driven MCP integrations to Hooman. Channel servers are normal MCP stdio servers in ~/.hooman/mcp.json that are started with the package's own --channels arg, advertise hooman/channel, and emit notifications/hooman/channel into hooman daemon.

Source Of Truth

MCP servers live in ~/.hooman/mcp.json under top-level mcpServers (minimal shape: {"mcpServers": {}}).
Restart the running Hooman session or daemon after changing mcp.json.
Run the long-lived listener with hooman daemon — it always subscribes to every configured server that advertises hooman/channel; there is no opt-out flag. Use --yolo only when the user explicitly accepts automatic tool approval risk. On an interactive terminal it renders a live kanban dashboard of session activity instead of a log stream; pass --no-dashboard for plain logs.

Reference File

Read channels.md (next to this SKILL.md) for the exact mcpServers JSON entry, requirements, configure steps, allowlists, metadata shape, and webhook/credential details of each channel before adding or troubleshooting it. Supported channels and packages:

cron — cronmcp (scheduler)
slack — slackxmcp
telegram — tgfmcp
whatsapp — wappmcp
jira — jiraxmcp (webhooks; credentials via server env)

Operating Rules

Read ~/.hooman/mcp.json before editing. If it is missing, create it only with a valid Hooman shape.
Preserve unrelated MCP servers, credentials, and allowlists. JSON comments are not supported.
Add each channel as a stdio server using command: "npx" and package args with -y.
Include the package's own --channels arg when the user wants inbound events, daemon automation, permission relay, webhooks, or scheduled prompts.
Do not print secrets from config files or environment maps. Use placeholders in explanations.
Prefer stable server names: cron, slack, telegram, whatsapp, and jira.
For Slack, Telegram, and WhatsApp, run each package's configure command first when local credentials or allowlists are not already configured.
For Jira, place credentials in the server env map or ensure the daemon's shell environment provides them.

Verification

After setup:

Confirm ~/.hooman/mcp.json contains the requested stdio server entries.
Restart Hooman and run hooman daemon.
Trigger one inbound event: a cron tick, Slack message, Telegram message, WhatsApp message, or Jira webhook.
If no event arrives, check the package-specific local config, allowlists, credentials, webhook reachability, and whether the MCP server was started with its own --channels arg.

Notes

chat and exec can use connected MCP tools on demand, but inbound channel events are processed by hooman daemon.
Slack, Telegram, and WhatsApp support remote channel permission relay. Jira and cron do not advertise permission relay in their README contracts.
These packages use stdio and are meant to be launched by Hooman, not browsed directly in a terminal.

More from this repository

same repository

hooman-config

vaibhavpandeyvpz/hooman

Read and update Hooman's own ~/.hooman/config.json and instructions.md. Use when the user asks about Hooman's config, custom instructions, agent name, model providers, LLMs/models, API keys, reasoning options, global reasoning display, web search settings, tool or prompt toggles, compaction, `hooman daemon` session/mcproxy limits, or first-run setup (`hooman setup`). Not for MCP servers (use hooman-mcp), channel integrations (hooman-channels), or installed skills (hooman-skills).

2026-07-1614

hooman-coding

vaibhavpandeyvpz/hooman

Required playbook for every programming task — load before the first implementation tool call whenever you will write or edit code, fix a bug, add or upgrade dependencies, scaffold a project, or run package/build/test commands, even for one-file scripts or spikes. Covers workflow, conventions, tests, verification, security, debugging/RCA, and greenfield setup. Skip only when purely reading or explaining code with no changes planned.

2026-07-1614

hooman-design

vaibhavpandeyvpz/hooman

Required playbook for design work — activate in design mode (or whenever producing HTML prototypes, dashboards, or decks). Covers the strict discovery→template→theme→build→preview→QA→human review→export workflow, DESIGN.md / directions, craft rules, artifact layout under .hooman/design, and delivery export (PDF/PPTX/screenshot-backed .fig/.deck/.sketch).

2026-07-1114

hooman-mcp

vaibhavpandeyvpz/hooman

Read and update Hooman's ~/.hooman/mcp.json. Use when the user asks to list, add, update, remove, or configure MCP servers for Hooman — stdio commands, streamable-http or SSE URLs, env vars, and auth headers. For event-driven channel servers (cron, Slack, Telegram, WhatsApp, Jira) use hooman-channels instead; for config.json settings use hooman-config.

2026-07-1114

bump-and-release

vaibhavpandeyvpz/hooman

Bump and release the Hooman repository by reviewing changes since the latest version tag, choosing a patch or minor bump, updating root and VS Code extension versions together, verifying clean builds, updating the VS Code changelog, formatting, committing, pushing, and tagging. Use when the user asks to prepare or perform a release for this repo.

2026-07-0814

hooman-skills

vaibhavpandeyvpz/hooman

Manage Hooman skills under ~/.hooman/skills. Use when the user asks to list, search, install, add, create, author, update, inspect, or remove Hooman skills or SKILL.md files. Not for activating or using a skill in the current task, and not for Hooman config or MCP server changes (use hooman-config or hooman-mcp).

2026-07-0414

name	hooman-channels
description	Add and configure Hooman channel MCP servers for cron, Slack, Telegram, WhatsApp, and Jira in ~/.hooman/mcp.json. Use when the user asks for scheduled or recurring prompts, cron jobs, messaging-app or chatbot integration, inbound webhooks, daemon automation, or connecting any event-driven channel to a Hooman agent or daemon. For ordinary (non-channel) MCP server edits use hooman-mcp.

Hooman Channels

Source Of Truth

MCP servers live in ~/.hooman/mcp.json under top-level mcpServers (minimal shape: {"mcpServers": {}}).
Restart the running Hooman session or daemon after changing mcp.json.
Run the long-lived listener with hooman daemon — it always subscribes to every configured server that advertises hooman/channel; there is no opt-out flag. Use --yolo only when the user explicitly accepts automatic tool approval risk. On an interactive terminal it renders a live kanban dashboard of session activity instead of a log stream; pass --no-dashboard for plain logs.

Reference File

cron — cronmcp (scheduler)
slack — slackxmcp
telegram — tgfmcp
whatsapp — wappmcp
jira — jiraxmcp (webhooks; credentials via server env)

Operating Rules

Read ~/.hooman/mcp.json before editing. If it is missing, create it only with a valid Hooman shape.
Preserve unrelated MCP servers, credentials, and allowlists. JSON comments are not supported.
Add each channel as a stdio server using command: "npx" and package args with -y.
Include the package's own --channels arg when the user wants inbound events, daemon automation, permission relay, webhooks, or scheduled prompts.
Do not print secrets from config files or environment maps. Use placeholders in explanations.
Prefer stable server names: cron, slack, telegram, whatsapp, and jira.
For Slack, Telegram, and WhatsApp, run each package's configure command first when local credentials or allowlists are not already configured.
For Jira, place credentials in the server env map or ensure the daemon's shell environment provides them.

Verification

After setup:

Confirm ~/.hooman/mcp.json contains the requested stdio server entries.
Restart Hooman and run hooman daemon.
Trigger one inbound event: a cron tick, Slack message, Telegram message, WhatsApp message, or Jira webhook.
If no event arrives, check the package-specific local config, allowlists, credentials, webhook reachability, and whether the MCP server was started with its own --channels arg.

Notes

chat and exec can use connected MCP tools on demand, but inbound channel events are processed by hooman daemon.
Slack, Telegram, and WhatsApp support remote channel permission relay. Jira and cron do not advertise permission relay in their README contracts.
These packages use stdio and are meant to be launched by Hooman, not browsed directly in a terminal.