Files

gavrielc 00fb1bee4a chore(skills): rename add-*-v2 → add-* and drop dead v1 channel skills

Renamed 13 skill folders to drop the -v2 suffix (the v2/v1 distinction
isn't load-bearing anymore — there is no v1 runtime). Deleted the four
v1 channel skills that occupied the rename target paths (add-discord,
add-slack, add-telegram, add-whatsapp); they targeted src/v1 which is
reference-only per CLAUDE.md.

Skill content still says "v2" in places — that's a follow-up commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-17 14:38:19 +03:00

2.6 KiB

Raw Blame History

name, description

name	description
add-linear-v2	Add Linear channel integration to NanoClaw v2 via Chat SDK. Issue comment threads as conversations.

Add Linear Channel

Adds Linear support to NanoClaw v2 using the Chat SDK bridge. The agent participates in issue comment threads.

Install

v2 trunk doesn't ship channels. This skill copies the Linear adapter in from the channels branch.

Pre-flight (idempotent)

Skip to Credentials if all of these are already in place:

src/channels/linear.ts exists
src/channels/index.ts contains import './linear.js';
@chat-adapter/linear is listed in package.json dependencies

Otherwise continue. Every step below is safe to re-run.

1. Fetch the channels branch

git fetch origin channels

2. Copy the adapter

git show origin/channels:src/channels/linear.ts > src/channels/linear.ts

3. Append the self-registration import

Append to src/channels/index.ts (skip if the line is already present):

import './linear.js';

4. Install the adapter package (pinned)

pnpm install @chat-adapter/linear@4.26.0

5. Build

pnpm run build

Credentials

Go to Linear Settings > API Keys

Create a Personal API Key (or use an OAuth application for team-wide access)

Copy the API key

Set up a webhook:

Go to Settings > API > Webhooks > New webhook

URL: https://your-domain/webhook/linear

Select events: Comment (created, updated)

Copy the signing secret

Configure environment

Add to .env:

LINEAR_API_KEY=lin_api_...
LINEAR_WEBHOOK_SECRET=your-webhook-secret

Sync to container: mkdir -p data/env && cp .env data/env/env

Next Steps

If you're in the middle of /setup, return to the setup flow now.

Otherwise, run /manage-channels to wire this channel to an agent group.

Channel Info

type: linear
terminology: Linear has "teams" containing "issues." Each issue's comment thread is a separate conversation.
how-to-find-id: The platform ID is your team key (e.g. ENG). Find it in Linear under Settings > Teams. Each issue becomes its own thread automatically.
supports-threads: yes (issue comment threads are native conversations)
typical-use: Webhook/notification — the agent receives issue comment events and responds in threads
default-isolation: Typically shares a session with a chat channel (e.g. Slack) so the agent can discuss issues in the same context as team chat. Use a separate agent group if the Linear team tracks sensitive work.

2.6 KiB Raw Blame History