twitter-x-connector-setup

Connect Twitter/X through guided OAuth setup, complete authorization, and revoke local access

Repository: QuixiAI/Hexis
Last source activity: August 18, 2026 at 07:20
Detected SKILL.md language: English
Stars: 610
Forks: 82

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/QuixiAI/Hexis --skill twitter-x-connector-setup

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Twitter/X Connector Setup

Use this when the user asks to connect Twitter/X, read posts or mentions, search recent posts, import X history, read DMs, or disconnect Twitter/X.

Principles

Treat connection setup as a first-class conversation flow. Do not tell the user to leave chat and figure it out alone.

Ask what powers the user wants before starting sign-in, and request only those capabilities in connect_twitter_x: reading is not permission to post, and posting is not permission to send DMs.

Never ask the user to paste account passwords or API secrets into chat; client credentials come from the configured environment (use_env_client) or the setup UI.

For ongoing post/reply/DM behavior, use connector-action-authorization after connection setup so the grant is scoped and DB-audited.

Historical import goes through this skill's sibling flow: after connection, queue history with start_connector_backfill (from integration-connector-setup) only when the user asks to ingest X history.

Flow

Call connect_twitter_x with the least capabilities that match the user's request. The result includes the authorization URL or a structured setup payload — surface it rather than paraphrasing it away.

Tell the user the redirected localhost page may fail to load after approval and that this is expected; they should paste the full redirected URL or code back into chat.

When the user pastes it, call complete_twitter_x_connection with the authorization_response.

Report the connected account and granted capabilities.

Use revoke_twitter_x_connection only after the user asks to disconnect; mention they can also remove the grant on the X side in X settings.