Omnichannel Comms Builder
Use when a site needs communication workflow planning: forms, inboxes, chat, booking, email/SMS/Telegram/CRM handoffs, operator queues, routing, templates, consent, and escalation. Workflow design only; never send real messages or mutate CRM channels without explicit approval.
Install
$ agentstack add skill-sergekostenchuk-ui-ux-agent-skill-system-omnichannel-comms-builder ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sergekostenchuk-ui-ux-agent-skill-system-omnichannel-comms-builder) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- Read [references/comms-safety-contract.md](references/comms-safety-contract.md).
- Use [assets/comms-workflow.template.md](assets/comms-workflow.template.md).
- Confirm channels, personal-data handling, and approval status.
- Mark all real sends and CRM mutations as
Planneduntil 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/nullSource & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sergekostenchuk
- Source: sergekostenchuk/ui-ux-agent-skill-system
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.