owner-communication

Route owner messages across TUI, email, and Jami with policy-driven channel selection.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/metric-space-ai/ctox --skill owner-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owner-communication
Source: https://github.com/metric-space-ai/ctox/tree/main/skills/system/communication/owner-communication
Command: npx skills add https://github.com/metric-space-ai/ctox --skill owner-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CTOX needs a robust, channel-aware way to communicate with the owner across TUI, email, and Jami while preserving thread continuity and enforcing routing policies.

Core Features & Use Cases

  • Route inbound owner messages to the most appropriate channel (TUI, email, or Jami) based on context and preferences.
  • Maintain a durable, cross-channel conversation thread by reusing subjects and referenced context.
  • Enforce authority and directive policies for owner, founder, and admin messages, and support proactive outbound coordination with proper channel selection.

Quick Start

Direct the agent to route an inbound owner message to the best channel and continue the current thread.

Frequently Asked Questions about owner-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route owner communications across email, TUI, and Jami while preserving thread continuity?

Route owner communications by applying configured preferences and thread history to select the correct channel. This maintains channel-appropriate, durable threads for both inbound messages and outbound follow-ups across TUI, email, and Jami.

How does channel-aware routing handle authority policies for owner, founder, and admin senders?

Channel-aware routing enforces policy-driven actions based on the sender's role. It tracks strategic directives and applies specific routing rules for owner, founder, and admin senders to maintain communication authority across channels.

What is the best way to manage outbound follow-ups with owners across multiple communication channels?

Manage outbound follow-ups by reusing subjects and referenced context to continue durable threads. The routing mechanism selects the appropriate channel based on configured preferences and prior thread history for proactive coordination.

Can I route inbound owner messages to a different channel than the one they were sent on?

Yes, inbound owner messages are routed to the most appropriate channel based on context and preferences. The system evaluates thread history and configured rules to redirect communications across TUI, email, or Jami.

When should I not use automated channel routing for owner communications?

Avoid automated channel routing when dedicated policy rules for owner, founder, or admin senders are absent. The mechanism relies on configured preferences, references for routing rules, and thread history to enforce authority and select channels correctly.

Does the owner-communication skill require specific messaging platforms to function?

The skill coordinates outreach specifically across TUI, email, and Jami. It requires these channels to be configured so it can apply routing rules, track directives, and maintain cross-channel conversation threads effectively.