Agent skill

Linear Channel for NanoClaw

by nanocoai in nanocoai/nanoclaw

Lets a NanoClaw agent answer every comment on Linear issues, using an OAuth application identity or a personal API key and the Chat SDK bridge.

MITAuto-check: notesProductivity & Automation

Install Linear Channel for NanoClaw

skills CLI
$ npx skills add nanocoai/nanoclaw --skill add-linear -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nanocoai/nanoclaw add-linear --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-linear .claude/skills/add-linear && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-linear
GitHub stars
31k
Token cost
~2.6k tokens
SKILL.md length
1,184 words
Files
3
Skills in repo
59
Repo updated
First seen
Licence
MIT

At a glance

Lets a NanoClaw agent answer every comment on Linear issues, using an OAuth application identity or a personal API key and the Chat SDK bridge.

  • Works in 6 steps: Copy the adapter and its registration test → Register the adapter → Install the adapter package → …
  • Having an agent respond in Linear issue comment threads
  • SKILL.md covers Prerequisites, Apply, Credentials and Wiring, plus 3 more sections
  • Calls pnpm; reaches github.com; needs LINEAR_API_KEY and LINEAR_TEAM_KEY

What it does

Every comment on a Linear issue triggers the agent, with no @-mention needed, so issue threads become conversations. The recommended setup is a Linear OAuth application with client credentials enabled, which lets the agent post under an app identity and stops the adapter from filtering your own comments as self-messages. A personal API key in `LINEAR_API_KEY` is the simpler alternative, but the agent then posts as you and your own comments are filtered out.

Because an OAuth app cannot be mentioned, the channel is set to respond to plain comments. Installation copies the Linear adapter and its registration test from the `channels` branch, appends the import to the channel barrel, installs `@chat-adapter/linear` at a pinned version, then builds and runs the test.

When your agent uses it

  • Having an agent respond in Linear issue comment threads
  • Choosing between an OAuth app identity and a personal API key for the bot
  • Adding the Linear adapter to an existing NanoClaw install

Example prompts

  • “Add the Linear channel to NanoClaw using an OAuth application for the bot identity.”
  • “Set up Linear with my personal API key instead, and explain how my own comments are handled.”
  • “Run the Linear registration test and confirm the adapter is registered.”

Requirements

  • A NanoClaw installation with pnpm
  • A Linear OAuth application or a personal API key

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Copy the adapter and its registration test
  2. Register the adapter
  3. Install the adapter package
  4. Build and validate
  5. Set up a webhook
  6. Store the credentials

What it can do on your machine

Read from SKILL.md and the folder at commit 66f0823. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    Also links to:

    • linear.app

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LINEAR_API_KEY
    • LINEAR_TEAM_KEY
    • LINEAR_WEBHOOK_SECRET
    • TEAM_KEY
    • LINEAR_CLIENT_SECRET

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linear Channel for NanoClaw loads about 2.6k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 1,184 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:105
    directive consumes it. Here they go to `.env`
  • NoteMentions a .env fileSKILL.md:111
    in `.env` by hand (commented in the template below). `LINEAR_BOT_USERNAME` is the
  • NoteMentions a .env fileSKILL.md:139
    ersonal API key route, add this line to `.env` instead of the
  • NoteMentions a .env fileSKILL.md:202
    uth prompts and set `LINEAR_API_KEY` in `.env` by hand.
  • NoteMentions a .env fileSKILL.md:208
    ice (see Next Steps) so the adapter and `.env` values are live.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nanocoai/nanoclaw at commit 66f0823, republished under its MIT licence (© nanocoai). 1,184 words, ~2,553 tokens.

Download SKILL.mdSave it as .claude/skills/add-linear/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
add-linear
description
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.

Add Linear Channel

Adds Linear support via the Chat SDK bridge. The agent participates in issue comment threads. Every comment on a Linear issue triggers the agent — no @-mention needed. NanoClaw doesn't ship channels in trunk — this skill copies the Linear adapter in from the channels branch.

The mechanical steps under Apply carry nc: directive fences: an agent reads the prose and applies them, and a parser can apply them deterministically from the same document. Every directive is idempotent, so the whole skill is safe to re-run; anything a parser can't apply falls back to the prose beside it.

Prerequisites

Recommended: Create a Linear OAuth application so the agent posts as an app identity, not as you. This prevents the adapter from filtering your own comments as self-messages.

  1. Go to Linear Settings > API > OAuth Applications
  2. Create an app (e.g. "NanoClaw Bot")
    • Developer URL: your repo URL (e.g. https://github.com/your-org/nanoclaw)
    • Callback URL: http://localhost
  3. After creating, click the app and enable Client credentials under grant types
  4. Copy the Client ID and Client Secret

Alternative: Use a Personal API Key (LINEAR_API_KEY) for simpler setup. The agent will post as you, and your own comments will be filtered (other team members' comments still work).

Apply

Linear OAuth apps post and read comments under an app identity that can't be @-mentioned; the adapter's declared channel defaults therefore respond to plain comments rather than mention-only, and the wiring below sets that same pattern mode explicitly.

1. Copy the adapter and its registration test

Fetch the channels branch and copy the Linear adapter and its registration test into src/channels/ (overwrite — the branch is canonical):

nccopy
src/channels/linear.ts
src/channels/linear-registration.test.ts
2. Register the adapter

Append the self-registration import to the channel barrel (skipped if the line is already present). This one line is the skill's only reach-in into the channel registry:

ncappend
import './linear.js';
3. Install the adapter package

Pinned to an exact version — the supply-chain policy rejects ranges and latest:

ncdep
@chat-adapter/linear@4.29.0
4. Build and validate

Build first: it guards the typed createChatSdkBridge(...) core call and proves the dependency is installed. Then run the one integration test.

ncrun
pnpm run build
ncrun
pnpm exec vitest run src/channels/linear-registration.test.ts

Both must be clean before proceeding. linear-registration.test.ts imports the real channel barrel and asserts the registry contains linear. It goes red if the import './linear.js'; line is deleted or drifts, if the barrel fails to evaluate, or if @chat-adapter/linear isn't installed (the import throws) — so it also covers the dependency from step 3. End-to-end message delivery against a real Linear workspace is verified manually once the service is running — see Wiring and Next Steps.

Credentials

Linear app and webhook setup is human and interactive — these steps are prose (no parser can click through the Linear UI), except the final env write.

1. Set up a webhook
  1. Go to Linear Settings > API > Webhooks > New webhook
  2. Label: NanoClaw
  3. URL: https://your-domain/webhook/linear (the shared webhook server, default port 3000)
  4. Team: select the team you want to monitor
  5. Events: check Comment
  6. Save — copy the signing secret

Note: Linear webhook delivery may be delayed 1-5 minutes for new webhooks. This is normal.

2. Store the credentials

Capture the values, then write them. prompt only asks and binds the answer to a name; a separate directive consumes it. Here they go to .env (set-if-absent — a value you've already filled in is never overwritten) and sync to the container.

Use either the OAuth app credentials (recommended) or a Personal API key. For the API-key path, paste none at the OAuth prompts and set LINEAR_API_KEY in .env by hand (commented in the template below). LINEAR_BOT_USERNAME is the display name for the bot, used for self-message detection when using a Personal API Key. LINEAR_TEAM_KEY is the Linear team key (e.g. ENG, NAN) — find it in Linear under Settings > Teams; all issues in this team route to one messaging group.

ncprompt
Paste the OAuth Client ID — Linear Settings > API > OAuth Applications. Paste `none` if using a Personal API key instead.
ncprompt
Paste the OAuth Client Secret. Paste `none` if using a Personal API key instead.
ncprompt
Paste the webhook signing secret from the webhook you just created.
ncprompt
Enter the Linear team key (e.g. `ENG`, `NAN`) — Settings > Teams.
ncprompt
Enter the bot display name (e.g. `NanoClaw Bot`).
ncenv-set
LINEAR_CLIENT_ID={{linear_client_id}}
LINEAR_CLIENT_SECRET={{linear_client_secret}}
LINEAR_WEBHOOK_SECRET={{linear_webhook_secret}}
LINEAR_TEAM_KEY={{linear_team_key}}
LINEAR_BOT_USERNAME={{linear_bot_username}}

If you went the Personal API key route, add this line to .env instead of the OAuth pair (agent posts as you, your own comments are filtered):

bash
LINEAR_API_KEY=lin_api_...
Show full SKILL.md (529 more words)Show less

Wiring

Linear is team-routed: the assistant watches one team and answers every comment on its issues (it can't be @-mentioned). Wire the team you set up to an agent — pick which one should answer (ncl groups list shows their folders). The host service must be running — ncl connects to it over a Unix socket.

The sender policy depends on the workspace: a private workspace can use public (only workspace members can comment anyway); a public workspace should use strict so only registered members may talk to the agent.

ncprompt
Which agent should answer Linear comments? Enter its folder (run `ncl groups list`).
ncprompt
Is this a private or public Linear workspace? Enter `public` for a private workspace (only members can comment) or `strict` for a public workspace (only registered members may talk to the agent).
ncrun
ncl messaging-groups create --channel-type linear --platform-id linear:{{linear_team_key}} --is-group 1 --unknown-sender-policy {{linear_sender_policy}} --name {{linear_team_key}}
ncl wirings create --channel-type linear --platform-id linear:{{linear_team_key}} --agent-group {{agent_folder}} --engage-mode pattern --engage-pattern . --session-mode per-thread

The explicit pattern engage mode with pattern . matches the Linear adapter's declared channel defaults — Linear can't be @-mentioned, so the agent answers every comment. Each issue thread becomes its own conversation. There's no welcome — Linear has no direct message, so the assistant greets people when it first answers a comment. If you chose strict, register the people who may talk to the agent (see the GitHub skill for adding members).

Next Steps

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

Otherwise, restart the service to pick up the new channel.

Run from your NanoClaw project root:

bash
source setup/lib/install-slug.sh
launchctl kickstart -k gui/$(id -u)/$(launchd_label)  # macOS
systemctl --user restart $(systemd_unit)              # Linux

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 linear:<TEAM_KEY> (e.g. linear:ENG). Find your team key in Linear under Settings > Teams. Each issue becomes its own thread automatically.
  • supports-threads: yes (issue comment threads are native conversations)
  • typical-use: Webhook-driven — the agent receives all issue comment events and responds automatically. No @-mention needed (Linear OAuth apps can't be @-mentioned).
  • default-isolation: Use per-thread session mode. Each issue comment thread gets its own isolated agent session.

Troubleshooting

Comments never reach the agent. New Linear webhooks can lag 1–5 minutes, so wait before digging. Then check the webhook in Linear Settings → API → Webhooks: the URL must be your public host at /webhook/linear (shared webhook server, port 3000), the right team selected, and the Comment event checked. A mismatch between the webhook's signing secret and LINEAR_WEBHOOK_SECRET makes deliveries fail signature verification silently — re-copy the secret from the webhook page.

OAuth credentials rejected. The Client ID and Secret come from Linear Settings → API → OAuth Applications, and the app must have Client credentials enabled under grant types after creation — without that toggle the token exchange 401s. If you meant to use a Personal API key instead, answer none at both OAuth prompts and set LINEAR_API_KEY in .env by hand.

The agent ignores your own comments. That's Personal-API-key mode working as designed: comments from the key's account are filtered as self-messages so the bot doesn't answer itself. Other members' comments still trigger it; if it must answer you too, switch to the OAuth app identity.

Sender-policy answer rejected, or issues route nowhere. The policy must be exactly public or strict (lowercase), and LINEAR_TEAM_KEY must be the short team key (e.g. ENG) from Settings → Teams — all issues in that one team route to the messaging group.

Wired but dead. Run pnpm exec vitest run src/channels/linear-registration.test.ts — red means the barrel import or the @chat-adapter/linear install drifted, so re-run the Apply steps. If green, restart the service (see Next Steps) so the adapter and .env values are live.

© nanocoai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .claude/skills/add-linear of nanocoai/nanoclaw.

  • SKILL.md
  • REMOVE.md
  • apply-fixtures.json

Open the folder on GitHubat commit 66f0823

Compare with similar skills

Linear Channel for NanoClaw next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linear Channel for NanoClaw compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Channel for NanoClaw this skillnanocoai/nanoclaw31k—~2.6kAutomated safety check: NotesMIT
Linear Tickets via Orcastablyai/orca87k—~558Automated safety check: PassMIT
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0
Linear Automationdavila7/claude-code-templates32k8 repos~1.5kAutomated safety check: PassMIT
OpenWork Slack Setupdifferent-ai/openwork24k—~1.2kAutomated safety check: PassCustom licence
Superset Integration Toolssuperset-sh/superset15k—~1.6kAutomated safety check: WarnCustom licence

Similar skills

  • Linear ticket work through Orca's CLI. Use when working from a linked Linear issue, finishing work with a PR/MR link and a completion comment, moving a ticket…

    87k GitHub stars~558 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 14 days ago
    Productivity & AutomationAuto-check passed
  • Linear Automation

    davila7/claude-code-templates

    Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels.

    32k GitHub starsUsed in 8 repos~1.5k tokens
    Productivity & AutomationAuto-check passed
  • OpenWork Slack Setup

    different-ai/openwork

    Configures and verifies the OpenWork Slack assistant for an approved private-alpha organization, merging manifest changes into its existing Slack app.

    24k GitHub stars~1.2k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Superset Integration Tools

    superset-sh/superset

    Lists and calls the tools of connected integrations such as Linear, GitHub, Sentry or Notion through the superset mcp command, without storing a token on the machine.

    15k GitHub stars~1.6k tokensUpdated yesterday
    Agent WorkflowsAuto-check: warnings
  • Telegram Automation

    davepoon/buildwithclaude

    Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands.

    3.6k GitHub starsUsed in 7 repos~2.1k tokens
    Productivity & AutomationAuto-check passed

More from nanocoai/nanoclaw

All 59 skills in this repo
  • Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.

    31k GitHub stars~4.6k tokensUpdated yesterday
    Auto-check: notes
  • Agent Browser

    nanocoai/nanoclaw

    Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.

    31k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed
  • Installs or refreshes OneCLI as the gateway provider for NanoClaw, copying the adapter files, registering the provider and running the setup script.

    31k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes
  • Guides a conversational migration from an OpenClaw install to NanoClaw v2, carrying over identity, channel credentials, scheduled tasks and workspace files.

    31k GitHub stars~6k tokensUpdated yesterday
    Auto-check: notes
  • Wires up an additional phone number onto an already-installed Dial channel, so one NanoClaw install answers SMS and AI voice calls on more than one line.

    31k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • NanoClaw LLM Wiki Setup

    nanocoai/nanoclaw

    Adds a persistent wiki knowledge base to a NanoClaw group following Karpathy's LLM Wiki pattern, with folders, a tailored container skill and a CLAUDE.md section.

    31k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

Works with

Questions about Linear Channel for NanoClaw

What does Linear Channel for NanoClaw do?

Lets a NanoClaw agent answer every comment on Linear issues, using an OAuth application identity or a personal API key and the Chat SDK bridge. Every comment on a Linear issue triggers the agent, with no @-mention needed, so issue threads become conversations. The recommended setup is a Linear OAuth application with client credentials enabled, which lets the agent post under an app identity and stops the adapter from filtering your own comments as self-messages.

When should I use Linear Channel for NanoClaw?

Linear Channel for NanoClaw fits situations like: having an agent respond in Linear issue comment threads; choosing between an OAuth app identity and a personal API key for the bot; adding the Linear adapter to an existing NanoClaw install.

How do I install Linear Channel for NanoClaw in Claude Code?

Run `npx skills add nanocoai/nanoclaw --skill add-linear -a claude-code`. Or copy the skill folder (.claude/skills/add-linear in nanocoai/nanoclaw) into .claude/skills/add-linear in your project. Claude Code loads it when a task matches its description.

How do I install Linear Channel for NanoClaw in Codex?

Run `npx skills add nanocoai/nanoclaw --skill add-linear -a codex`. Or copy the skill folder (.claude/skills/add-linear in nanocoai/nanoclaw) into .agents/skills/add-linear in your project. Codex loads it when a task matches its description.

Can I use Linear Channel for NanoClaw in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nanocoai/nanoclaw --skill add-linear -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-linear, .gemini/skills/add-linear, .github/skills/add-linear and .opencode/skills/add-linear in your project.

What does Linear Channel for NanoClaw need to run?

Going by SKILL.md and its folder, Linear Channel for NanoClaw needs the command-line tools its instructions call (pnpm) and credentials named LINEAR_API_KEY, LINEAR_TEAM_KEY, LINEAR_WEBHOOK_SECRET and TEAM_KEY. Our summary lists: A NanoClaw installation with pnpm; A Linear OAuth application or a personal API key.

Does Linear Channel for NanoClaw access the network?

SKILL.md names 2 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: linear.app. This is read from the text; nothing was executed.

Is Linear Channel for NanoClaw safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Linear Channel for NanoClaw use?

Linear Channel for NanoClaw is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linear Channel for NanoClaw use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Linear Channel for NanoClaw?

Skills that share tags, products or a category with Linear Channel for NanoClaw: Linear Tickets via Orca (stablyai/orca, 87k stars), Openloomi Connectors (melandlabs/openloomi, 1k stars), Linear Automation (davila7/claude-code-templates, 32k stars) and OpenWork Slack Setup (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Channel for NanoClaw?

nanocoai (a GitHub organization) maintains it in nanocoai/nanoclaw, which has 30,883 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on October 6, 2026.

Source: nanocoai/nanoclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.