twitter-voice-setup

twitter-voice-setup

This skill turns the bundled setup guide into an actionable agent workflow. The posting runtime is still planned; what ships now is the onboarding path.

What exists today

• Human-facing setup guide: ../../twitter-voice-setup.html
• Agent-facing setup workflow: this skill
• Local verifier: scripts/check_env_keys.py

Use this skill for

• creating a fresh X account for an agent
• applying for X Developer access
• creating the Project/App and choosing the right permissions
• deciding whether Free tier is enough
• writing or checking the required ~/.env keys
• explaining first-week rhythm and what the plugin will refuse to do

Core rules

• Write secrets only to ~/.env, never to a repo-local .env.
• Treat ~/.env as the source of truth and keep its mode at 600.
• Do not commit, paste, or echo secrets into logs unless the user explicitly asks to inspect a specific value.
• The required keys are:

TWITTER_CONSUMER_KEY=
TWITTER_CONSUMER_SECRET=
TWITTER_ACCESS_TOKEN=
TWITTER_ACCESS_TOKEN_SECRET=

First action — open the visual guide

When this skill is triggered, immediately open the setup guide in the user's browser before doing anything else:

open plugins/twitter-voice/twitter-voice-setup.html

The guide is a self-contained Neon Rhymes-themed HTML page covering the full onboarding flow with interactive navigation. Let the human read it — then assist with whatever step they need help on.

Workflow

1. Open the visual guide (see above).
2. Decide whether the user needs:
   • full onboarding from zero
   • env verification only
   • troubleshooting of an existing setup
3. For full onboarding, read references/portal-setup.md.
4. For local key placement and runtime constraints, read references/runtime-contract.md.
5. Use scripts/check_env_keys.py to inspect ~/.env before claiming setup is complete.

Decision defaults

• Prefer OAuth 1.0a with Read and Write permissions.
• Prefer the standard TWITTER_* variable names above.
• Prefer Free tier first. Escalate to Basic only after confirming that permissions and token regeneration were done correctly.
• Treat the account as an agent-owned account, not as a girl's account.

If something breaks

• Missing keys → run scripts/check_env_keys.py
• 403 Forbidden on write → re-check App permissions and regenerate Access Tokens after switching to Read and Write
• Free tier worries → compare actual write volume with the limits in references/runtime-contract.md
• Need the visual guide → open ../../twitter-voice-setup.html