Agent Skills › QuixiAI/Hexis › integration-connector-setup

integration-connector-setup

GitHub

用于配置和验证 Slack、Telegram、Signal 等通信连接器，管理历史数据回填任务。

skills/installed/integration-connector-setup/SKILL.md QuixiAI/Hexis

Trigger Scenarios

连接 Slack/Telegram/Signal 检查可用连接器导入历史消息

Install

npx skills add QuixiAI/Hexis --skill integration-connector-setup -g -y

More Options

Non-standard path

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/integration-connector-setup -g -y

Use without installing

npx skills use QuixiAI/Hexis@integration-connector-setup

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill integration-connector-setup -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

SKILL.md

Frontmatter

{
    "name": "integration-connector-setup",
    "category": "communication",
    "contexts": [
        "chat"
    ],
    "requires": {
        "tools": [
            "integration_setup_status",
            "start_integration_setup",
            "configure_channel_integration",
            "verify_channel_integration"
        ]
    },
    "bound_tools": [
        "integration_setup_status",
        "start_integration_setup",
        "configure_channel_integration",
        "verify_channel_integration",
        "start_connector_backfill",
        "connector_backfill_status",
        "control_connector_backfill"
    ],
    "description": "Start, configure, verify, and inspect first-class non-Gmail communication connector setup for Slack, Telegram, and Signal, and manage historical backfill jobs"
}

Integration Connector Setup

Use this when the user asks to connect Slack, Telegram, Signal, or to inspect available communication connectors.

Principles

Treat setup as an in-conversation flow with exact next steps from the DB connector manifest.
Never ask the user to paste bot tokens, app tokens, passwords, or API secrets into chat. Token fields must be env var names.
Use connect_gmail from the Gmail connector skill for Gmail OAuth; this skill covers manual/pairing channel connectors.
Be explicit when a capability is planned rather than available for a given provider.
Historical backfill is local memory ingestion and needs explicit user approval, even when the provider access is read-only. Queue it only for a connected connector, after the user asks to import history.
After config is written or the user says env vars are set, call verify_channel_integration so the DB records the connection only when the channel worker's config truth resolves.

Flow

Call integration_setup_status for the requested connector or for all connectors if the user asks what can be connected.
Call start_integration_setup with the least capabilities matching the user's request.
If the user provides channel settings, call configure_channel_integration only with env var names for token fields and non-secret allowlists or URLs.
Call verify_channel_integration after the env/config values should be available.
Tell the user to start or restart hexis-channels only if verification succeeded and the adapter is not already running.
If the user asks to import history, call start_connector_backfill with the smallest useful scope — Slack needs a channel_id; Telegram, Signal, and Twitter/X take a local export/archive path (export_path/import_path).
Use connector_backfill_status for progress, and control_connector_backfill only when the user asks to pause, resume, or cancel a job.