sergekostenchuk/ui-ux-agent-skill-system

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.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill omnichannel-comms-builder

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

bash
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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
sergekostenchuk
コミュニティ

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日
sergekostenchuk
コミュニティ

editorial-quality-gate

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

1時間の導入数
1
GitHub Stars
35
更新日
9月13日