@windyroad/connect 0.2.0 → 0.2.1-preview.38

package/README.md

@@ -37,9 +37,9 @@ Run the interactive setup skill:
 /wr-connect:setup
 ```
 
-This walks you through:
-1. Creating a Discord bot
-2. Configuring environment variables (bot token, channel ID, session name)
+This is an interactive walkthrough that guides you through:
+1. Creating a Discord bot (`wr-connect`)
+2. Storing credentials (`.env` file, 1Password, or shell profile)
 3. Installing the Discord channel plugin
 4. Configuring the security allowlist
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/connect",
-  "version": "0.2.0",
+  "version": "0.2.1-preview.38",
   "description": "Connect Claude Code sessions across repos via Discord (experimental)",
   "bin": {
     "windyroad-connect": "./bin/install.mjs"

package/skills/setup/SKILL.md

@@ -12,9 +12,12 @@ allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
 This skill configures Discord as a collaboration channel so Claude Code sessions
 across different repos can communicate with zero idle token cost.
 
+**This is an interactive walkthrough.** Use AskUserQuestion at each step to confirm
+progress and gather details. Do NOT skip ahead — wait for the user at each checkpoint.
+
 ## Steps
 
-### 1. Explain what this does
+### 1. Explain and opt-in
 
 Tell the user:
 
@@ -29,65 +32,121 @@ Tell the user:
 > - A Discord bot (created in the next step)
 > - A private Discord server or channel
 
-### 2. Opt-out checkpoint
+Use AskUserQuestion:
+- "Would you like to proceed with setting up cross-repo collaboration via Discord?"
+- Options: "Yes, let's set it up" / "No, skip for now"
 
-Use AskUserQuestion to ask the user:
+If no:
+> Setup skipped. The connect plugin is inactive until configured.
+> Run `/wr-connect:setup` any time to start again.
 
-> Would you like to proceed with setting up cross-repo collaboration via Discord?
-> This will require creating a Discord bot and configuring environment variables.
-> No files will be written to your project.
->
-> Reply **yes** to continue or **no** to skip.
+Stop — do not proceed.
 
-If the user says no, respond with:
+### 2. Check for existing Discord server
 
-> Setup skipped. The connect plugin is inactive until configured.
-> Run `/wr-connect:setup` any time to start again.
+Use AskUserQuestion:
+- "Do you already have a Discord server you'd like to use, or do you need to create one?"
+- Options: "I have a server" / "I need to create one"
 
-Then stop — do not proceed to any further steps.
+If they need to create one, guide them:
+1. Open Discord and click the **+** button in the server list
+2. Choose **Create My Own** > **For me and my friends**
+3. Name it something like `dev-agents` or `wr-connect`
 
 ### 3. Create a Discord bot
 
-Guide the user through these steps:
-
-1. Go to https://discord.com/developers/applications
-2. Click **New Application** — name it something like `claude-connect`
-3. Go to **Bot** > click **Add Bot** > confirm
-4. Under **Token**, click **Reset Token** and copy it — they will need it in step 5
-5. Under **Privileged Gateway Intents**, enable **Message Content Intent**
-6. Go to **OAuth2 > URL Generator**:
+Tell the user to go to https://discord.com/developers/applications, then guide
+them step by step. Use AskUserQuestion after giving the instructions:
+
+**Instructions:**
+1. Click **New Application** — name it `wr-connect`
+2. Go to **Bot** > click **Add Bot** > confirm
+3. Under **Token**, click **Reset Token** and copy the token
+4. Under **Privileged Gateway Intents**, enable:
+   - **Message Content Intent** (to read message text)
+   - **Server Members Intent** (optional — for member awareness)
+5. Go to **OAuth2 > URL Generator**:
    - Scopes: `bot`
-   - Bot permissions: `Send Messages`, `Read Messages/View Channels`
-7. Copy the generated URL, open it in a browser, and add the bot to their server
+   - Bot permissions: `Send Messages`, `Read Messages/View Channels`, `Add Reactions`, `Read Message History`
+6. Copy the generated URL, open it in a browser, and add the bot to your server
 
-### 4. Get the channel ID
+Use AskUserQuestion:
+- "Have you created the bot and copied the token?"
+- Options: "Yes, I have the token" / "I need help with a step"
+
+If they need help, ask which step is unclear and provide more detail.
 
-Guide the user:
+### 4. Get the channel ID
 
+Tell the user:
 1. In Discord, go to **User Settings > Advanced** and enable **Developer Mode**
-2. Right-click the channel to use for collaboration and click **Copy Channel ID**
+2. Create a channel (e.g., `#agent-collab`) or pick an existing one
+3. Right-click the channel and click **Copy Channel ID**
+
+Use AskUserQuestion:
+- "Have you copied the channel ID?"
+- Options: "Yes, I have the channel ID" / "I need help"
 
-### 5. Configure environment variables
+### 5. Store credentials
 
-Guide the user to add these to their shell profile (`~/.zshrc`, `~/.bashrc`) or a
-`.env` file that is already in `.gitignore`:
+Use AskUserQuestion:
+- "Where would you like to store the bot token and channel ID?"
+- Options:
+  - ".env file (recommended)" — "Store in a .env file in the project root. The file must be in .gitignore."
+  - "1Password CLI" — "Use `op` CLI to store secrets in 1Password and reference them via `op://`"
+  - "Shell profile" — "Add exports to ~/.zshrc or ~/.bashrc"
 
+**If .env file:**
+
+Check that `.env` is in `.gitignore`:
 ```bash
-export WR_CONNECT_BOT_TOKEN="<the bot token from step 3>"
-export WR_CONNECT_CHANNEL_ID="<the channel ID from step 4>"
-export WR_CONNECT_SESSION_NAME="<a name for this session, e.g. repo-b>"
+grep -q '\.env' .gitignore 2>/dev/null && echo ".env is in .gitignore" || echo "WARNING: .env is NOT in .gitignore"
 ```
 
-**Security warning:** The bot token gives anyone who has it the ability to send
-messages to your Claude Code session. Never commit it to source control. Use
-environment variables or a `.env` file that is in `.gitignore`.
+If not in `.gitignore`, warn the user and offer to add it.
+
+Use AskUserQuestion to get the values:
+- "Paste your bot token (from step 3):"
+- "Paste your channel ID (from step 4):"
+- "What should this session be called? (e.g., `windyroad-plugins`, `repo-a`)"
+
+Write the `.env` file (or append to it if it exists):
+```
+WR_CONNECT_BOT_TOKEN=<token>
+WR_CONNECT_CHANNEL_ID=<channel-id>
+WR_CONNECT_SESSION_NAME=<session-name>
+```
 
-If the user chooses a `.env` file, verify `.env` is in `.gitignore`:
+**If 1Password CLI:**
+
+Check if `op` is available:
+```bash
+command -v op && echo "1Password CLI available" || echo "1Password CLI not found"
+```
+
+Guide the user to create a vault item and reference it:
+```bash
+op item create --category=API\ Credential --title="wr-connect" \
+  'bot_token=<token>' \
+  'channel_id=<channel-id>' \
+  'session_name=<session-name>'
+```
 
+Then add to shell profile:
 ```bash
-grep -q '\.env' .gitignore 2>/dev/null && echo ".env is in .gitignore" || echo "WARNING: .env is NOT in .gitignore — add it now"
+export WR_CONNECT_BOT_TOKEN="$(op read 'op://Private/wr-connect/bot_token')"
+export WR_CONNECT_CHANNEL_ID="$(op read 'op://Private/wr-connect/channel_id')"
+export WR_CONNECT_SESSION_NAME="$(op read 'op://Private/wr-connect/session_name')"
 ```
 
+**If shell profile:**
+
+Use AskUserQuestion to get the values (same as .env), then tell the user to add
+the exports to their `~/.zshrc` or `~/.bashrc` and run `source ~/.zshrc`.
+
+**Security warning:** The bot token gives anyone who has it the ability to send
+messages to your Claude Code session. Never commit it to source control.
+
 ### 6. Verify environment variables
 
 Check the env vars are set in the current shell:
@@ -98,42 +157,58 @@ Check the env vars are set in the current shell:
 [ -n "$WR_CONNECT_SESSION_NAME" ] && echo "SESSION_NAME: set" || echo "SESSION_NAME: NOT SET"
 ```
 
-If any are not set, remind the user to `source ~/.zshrc` (or their profile) or
-restart their terminal before continuing.
-
-### 7. Install the Discord channel plugin
+If any are not set:
+- For .env: remind the user to run `source .env` or check the file
+- For 1Password: remind the user to run `eval $(op signin)` first
+- For shell profile: remind the user to `source ~/.zshrc`
 
-```bash
-claude plugin install discord@claude-plugins-official
-```
+Use AskUserQuestion:
+- "Are all three variables showing as set?"
+- Options: "Yes, all set" / "No, some are missing"
 
-### 8. Restart with channels active
+If missing, help troubleshoot.
 
-Tell the user to restart Claude Code with:
+### 7. Install the Discord channel plugin
 
 ```bash
-claude --channels plugin:discord@claude-plugins-official
+claude plugin install discord@claude-plugins-official
 ```
 
-Claude will send a pairing code. Follow the prompts to pair the Discord account.
-
-### 9. Configure the Discord allowlist (security)
+### 8. Configure the Discord allowlist (security)
 
 This is critical. Without the allowlist, anyone who can message the bot can send
 instructions to the Claude Code session.
 
+Tell the user:
+
+> To find your Discord user ID: In Discord with Developer Mode enabled,
+> click your username at the bottom left, then click **Copy User ID**.
+
 Guide the user to configure the allowlist so only their own Discord user ID can
 send messages. The exact command depends on the Discord channel plugin's interface —
 check its documentation for the allowlist or access policy setting.
 
+Use AskUserQuestion:
+- "Have you configured the Discord allowlist with your user ID?"
+- Options: "Yes, allowlist configured" / "I need help finding my user ID" / "I'll do this later"
+
+### 9. Restart with channels active
+
 Tell the user:
 
-> To find your Discord user ID: In Discord with Developer Mode enabled,
-> click your username at the bottom left, then click **Copy User ID**.
+> To activate, restart Claude Code with:
+> ```
+> claude --channels plugin:discord@claude-plugins-official
+> ```
+> Claude will send a pairing code. Follow the prompts to pair your Discord account.
 
 ### 10. Test the setup
 
-Ask the user if they would like to send a test message. If yes, tell them to use:
+Use AskUserQuestion:
+- "Would you like to send a test message to verify the setup?"
+- Options: "Yes, send a test" / "No, I'll test later"
+
+If yes, tell them to use:
 
 ```
 /wr-connect:send test message from setup
@@ -148,8 +223,6 @@ curl -s -X POST "https://discord.com/api/v10/channels/$WR_CONNECT_CHANNEL_ID/mes
   -d '{"content": "[wr-connect] from: test | setup verification"}'
 ```
 
-If the session with `--channels` active receives the message, setup is complete.
-
 ### 11. Explain collaboration behaviour
 
 Tell the user:
@@ -164,5 +237,6 @@ Tell the user:
 >   is relevant to its work.
 > - Your session name is whatever you set in `WR_CONNECT_SESSION_NAME`. Other
 >   sessions will use `@your-name` to get your attention.
+> - Agents can react to messages for lightweight acknowledgement.
 
 $ARGUMENTS