mcpField
O
omnichannel-comms-builder

omnichannel-comms-builder

github.com/sergekostenchukOther3249 installsUpdated 18w ago
Repository

About omnichannel-comms-builder

omnichannel-comms-builder is a skill for designing communication flows between site users and operators. It plans channels, routing, templates, and consent requirements; real messages are not sent by default.

Key features

  1. 01Channel, routing, and ownership plans
  2. 02Message template drafting
  3. 03Inbox and queue UI handoff
  4. 04Consent, logging, and retention requirements
  5. 05Approval gates for sends and CRM changes

Use cases

  1. 01Plan support-channel routing and escalation
  2. 02Draft messages without sending them
  3. 03Define consent and opt-out requirements

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill omnichannel-comms-builder

After installing, type/omnichannel-comms-builderin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
assets/
comms-workflow.template.md
evals/
evals.json
references/
comms-safety-contract.md

Details

From the project README

Omnichannel Comms Builder

This skill designs communication flows between site users and operators. It does not send real messages by default.

Operating Modes

  • workflow-plan: define channels, routing, ownership, SLA, and escalation.
  • message-template: draft safe templates without sending.
  • operator-ui-handoff: specify inbox/queue UI needs.
  • consent-risk: define consent, logging, retention, and opt-out requirements.

Required Workflow

  1. Read references/comms-safety-contract.md.
  2. Use assets/comms-workflow.template.md.
  3. Confirm channels, personal-data handling, and approval status.
  4. Mark all real sends and CRM mutations as Planned until explicit approval.

Safety Rules

  • Do not send email, SMS, Telegram, chat, webhook, or CRM messages without approval.
  • Do not store private customer data, tokens, message exports, or cookies.
  • Templates must avoid false claims and must support opt-out and escalation when needed.

Validation

python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/omnichannel-comms-builder
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/omnichannel-comms-builder
python3 -m json.tool $CODEX_HOME/skills/omnichannel-comms-builder/evals/evals.json >/dev/null

Comments

Markdown supported