cyrus-setup-linear
Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.
Skill by cyrusagents
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/cyrusagents-cyrus-setup-linear
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: security, agent-building, identity-access
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/cyrus-setup-linear
What's inside
- Skill name
cyrus-setup-linear- Description
- Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.
- License
- Apache-2.0
- Instructions
- 239 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
**CRITICAL: Never use `Read`, `Edit`, or `Write` tools on `~/.cyrus/.env` or any file inside `~/.cyrus/`. Use only `Bash` commands (`grep`, `printf >>`, etc.) to interact with env files — secrets must never be read into the conversation context. Never scrape, extract, or read secret values from web pages — guide the user to copy them manually.**
# Setup Linear
Creates a Linear OAuth application and configures credentials so Cyrus can receive webhooks and respond to issues.
## Step 1: Check Existing Configuration
```bash
grep -E '^LINEAR_CLIENT_ID=' ~/.cyrus/.env 2>/dev/null
```
If `LINEAR_CLIENT_ID` is already set, check if OAuth is also complete:
```bash
grep -q '"workspaces"' ~/.cyrus/config.json 2>/dev/null && echo "configured" || echo "not configured"
```
If both are set, inform the user:
> Linear is already configured. Skipping this step.
> To reconfigure, remove `LINEAR_CLIENT_ID`, `LINEAR_CLIENT_SECRET`, and `LINEAR_WEBHOOK_SECRET` from `~/.cyrus/.env` and re-run.
Skip to completion.
## Step 2: Get CYRUS_BASE_URL
Read the base URL from the env file (set by `setup-endpoint`):
```bash
grep '^CYRUS_BASE_URL=' ~/.cyrus/.env | cut -d= -f2-
```
This is needed for the callback and webhook URLs.
## Step 3: Create Linear OAuth App From Manifest
Linear OAuth apps must be created from a manifest-backed setup URL. Do not create the app from scratch or fill each field manually. The manifest flow keeps the app configuration reproducible and avoids drift in callback, webhook, and event type settings.
### 3a. Build the manifest URL
Generate a JSON OAuth app manifest and encode it into Linear's `manifest` query parameter:
```bash
CYRUS_BASE_URL="<CYRUS_BASE_URL>" \
AGENT_NAME="<AGENT_NAME>" \
AGENT_DESCRIPTION="<AGENT_DESCRIPTION>" \
node <<'NODE'
const fs = require("node:fs");
const baseUrl = process.env.CYRUS_BASE_URL.replace(/\/+$/, "");
const agentName = process.env.AGENT_NAME || "Cyrus";
const agentDescription =
process.env.AGENT_DESCRIPTION || "AI coding agent for automated development";
const manifest = {
$schema: "https://linear.app/.well-known/oauth-app-manifest.schema.json",
schemaVersion: "1.0.0",
distribution: "private",
display: {
description: agentDescription,
},
developer: {
name: "Self-hosted",
},
oauth: {
client_name: agentName,
client_uri: "https://github.com/ceedaragents/cyrus",
redirect_uris: [`${baseUrl}/callback`],
grant_types: ["authorization_code"],
},
webhook: {
enabled: true,
url: `${baseUrl}/linear-webhook`,
resourceTypes: [
"AgentSessionEvent",
"AppUserNotification",
"PermissionChange",
"Issue",
],
},
};
const manifestJson = JSON.stringify(manifest, null, 2);
const manifestUrl = `https://linear.app/settings/api/applications/new?manifest=${encodeURIComponent(JSON.stringify(manifest))}`;
fs.writeFileSync("/tmp/cyrus-linear-oauth-app-manifest.json", `${manifestJson}\n`);
fs.writeFileSync("/tmp/cyrus-linear-oauth-app-url.txt", `${manifestUrl}\n`);
console.log(manifestJson);
console.log(`\n${manifestUrl}`);
NODE
LINEAR_MANIFEST_URL="$(cat /tmp/cyrus-linear-oauth-app-url.txt)"
```
The same URL is now stored in `LINEAR_MANIFEST_URL` for automation commands and in `/tmp/cyrus-linear-oauth-app-url.txt` for manual copy/paste. The JSON is stored in `/tmp/cyrus-linear-oauth-app-manifest.json` for review/debugging only; do not ask the user to fill the OAuth app form manually from it.
If `<AGENT_NAME>` contains the word "Linear" or a URL, choose a different OAuth application name before building the manifest. Linear rejects OAuth client names with those values.
Determine which browser automation mode to use (see orchestrator rules):
1. If `claude-in-chrome` MCP tools are available → use **Path A-1** (claude-in-chrome)
2. If `agent-browser` is installed (`which agent-browser`) and a Chrome debug session is connected → use **Path A-2** (agent-browser)
3. Otherwise → use **Path B** (manual)
### Path A-1: claude-in-chrome Automation
Use the `mcp__claude-in-chrome__*` tools to navigate and interact with the user's existing Chrome browser. The user is likely already signed in to Linear.
Navigate to `LINEAR_MANIFEST_URL`. The page should open with the manifest-applied OAuth app configuration already populated.
Review only non-secret fields:
- Application name matches `<AGENT_NAME>`
- Developer name is `Self-hosted`
- Developer URL is `https://github.com/ceedaragents/cyrus`
- Redirect callback URLs contains `<CYRUS_BASE_URL>/callback`
- Webhook is enabled with URL `<CYRUS_BASE_URL>/linear-webhook`From cyrusagents/cyrus, Apache-2.0.
More from cyrusagents/cyrus
- 0.817score
release-core-test
cyrusagents
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased…
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
verify-and-ship
cyrusagents
Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
debug
cyrusagents
Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
cyrus-setup
cyrusagents
Set up Cyrus end-to-end — install prerequisites, configure authentication, create integrations (Linear, GitHub, Slack), add repositories, and launch.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
f1-test-drive
cyrusagents
Assess F1 applicability, then validate changed product workflows or the F1 harness end-to-end.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
summarize
cyrusagents
Format a final summary message for Linear.
SkillAFreshness: A★ 867Claude Code +9 - 0.812score
release
cyrusagents
Prepare, verify, publish, and finish a coordinated Cyrus CLI release.
SkillAFreshness: A★ 867Claude Code +9 - 0.810score
connect-cyrus
cyrusagents
Connect a personal Cyrus inbox and help the user deliberately subscribe to messages in a dot or Cloud Work chat.
SkillAFreshness: A★ 867Claude Code +9 - 0.810score
cyrus-setup-claude-auth
cyrusagents
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
SkillAFreshness: A★ 867Claude Code +9 - 0.810score
google
cyrusagents
Search the web for information.
SkillAFreshness: A★ 867Claude Code - 0.810score
investigate
cyrusagents
Research the codebase to answer questions.
SkillAFreshness: A★ 867Claude Code +9 - 0.810score
cyrus-setup-slack
cyrusagents
Configure Slack integration for Cyrus — create a Slack app from manifest, then guide the user to save credentials.
SkillAFreshness: A★ 867Claude Code +9
Compare and alternatives
Featured in
Signals
- Stars
- 867
- Forks
- 180
- Open issues
- 50
- Last commit (this folder)
- Jul 25, 2026 (3 months ago)
- Last release
- Sep 30, 2026 (26 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/cyrusagents/cyrus
- Website
- atcyrus.com
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from cyrusagents
- 0.817score
release-core-test
cyrusagents
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased…
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
verify-and-ship
cyrusagents
Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
summarize
cyrusagents
Format a final summary message for Linear.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
f1-test-drive
cyrusagents
Assess F1 applicability, then validate changed product workflows or the F1 harness end-to-end.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
debug
cyrusagents
Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.
SkillAFreshness: A★ 867Claude Code +9 - 0.813score
cyrus-setup
cyrusagents
Set up Cyrus end-to-end — install prerequisites, configure authentication, create integrations (Linear, GitHub, Slack), add repositories, and launch.
SkillAFreshness: A★ 867Claude Code +9
Cite this page
cyrus-setup-linear skill. Agent Mart. https://agentmart.dev/skills/cyrusagents-cyrus-setup-linear (last updated 2026-10-24)