Orca Linear Ticket Workflow
stablyai/orca
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…
Read or manage this repository's Linear issues, projects, cycles, plans, triage, and follow-up work through toolkit linear, including developer-experience friction reports.
GPL-3.0Auto-check passed
Install Linear Work Management
$ npx skills add shepherdjerred/monorepo --skill linear-work-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shepherdjerred/monorepo linear-work-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/linear-work-management .claude/skills/linear-work-management && rm -rf skills-srcUse ~/.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/
Install the "linear-work-management" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-management into .claude/skills/linear-work-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-work-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shepherdjerred/monorepo --skill linear-work-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shepherdjerred/monorepo linear-work-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/linear-work-management .agents/skills/linear-work-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linear-work-management" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-management into .agents/skills/linear-work-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-work-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shepherdjerred/monorepo --skill linear-work-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shepherdjerred/monorepo linear-work-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/linear-work-management .cursor/skills/linear-work-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linear-work-management" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-management into .cursor/skills/linear-work-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-work-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shepherdjerred/monorepo.git --path .agents/skills/linear-work-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shepherdjerred/monorepo --skill linear-work-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shepherdjerred/monorepo linear-work-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/linear-work-management .gemini/skills/linear-work-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linear-work-management" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-management into .gemini/skills/linear-work-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-work-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shepherdjerred/monorepo linear-work-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shepherdjerred/monorepo --skill linear-work-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/linear-work-management .github/skills/linear-work-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linear-work-management" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-management into .github/skills/linear-work-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-work-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shepherdjerred/monorepo --skill linear-work-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shepherdjerred/monorepo linear-work-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shepherdjerred/monorepo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/linear-work-management .opencode/skills/linear-work-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linear-work-management" agent skill from https://github.com/shepherdjerred/monorepo/tree/main/.agents/skills/linear-work-management into .opencode/skills/linear-work-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-work-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linear-work-management- GitHub stars
- 112
- Token cost
- ~955 tokens
- SKILL.md length
- 391 words
- Files
- 1
- Skills in repo
- 63
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Read or manage this repository's Linear issues, projects, cycles, plans, triage, and follow-up work through toolkit linear, including developer-experience friction reports.
- Work must be found
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Linked to a branch
- Broken tooling must be filed
What it does
Linear Work Management is an agent skill from shepherdjerred/monorepo. Read or manage this repository's Linear issues, projects, cycles, plans, triage, and follow-up work through toolkit linear, including developer-experience friction reports. Use when work must be found, recorded, updated, linked to a branch, or when broken tooling must be filed.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Linear. The repository describes itself as: Monorepo for all of my projects. The licence is GPL-3.0.
When your agent uses it
- Work must be found
- Linked to a branch
- Broken tooling must be filed
Example prompts
- “/linear-work-management”
What it can do on your machine
Read from SKILL.md and the folder at commit 46ddf2f. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linear Work Management loads about 955 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 391 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 shepherdjerred/monorepo at commit 46ddf2f, republished under its GPL-3.0 licence (© shepherdjerred). 391 words, ~955 tokens.
Download SKILL.mdSave it as
.claude/skills/linear-work-management/SKILL.md (or your agent's skills folder).- name
- linear-work-management
- description
- Read or manage this repository's Linear issues, projects, cycles, plans, triage, and follow-up work through toolkit linear, including developer-experience friction reports. Use when work must be found, recorded, updated, linked to a branch, or when broken tooling must be filed.
Linear work management
Linear owns plans, TODOs, review queues, and unfinished follow-ups. Repository documents must not become a parallel work-tracking system.
Start by checking the ambient identity and resolving existing work:
toolkit linear --version
toolkit linear auth whoami
toolkit linear issue id
toolkit linear issue view SJ-123
toolkit linear issue list --team <key>The configured workspace is sjerred (monorepo), which has separate AI
and SJ teams. Search the AI team before creating an issue. Create every
agent-generated issue in AI; do not assign a project unless the task names
one or the issue is a developer-experience report. Never create an issue in
SJ, which is reserved for human-created work. An agent may update an existing
SJ issue only when the task explicitly identifies it. Read the issue,
comments, relationships, project, and cycle before editing it.
For mutations, inspect the command or API schema, name the exact target, and change only fields required by the task. Keep issue state synchronized with observable work; do not mark complete merely because code exists locally.
Never print or paste the Linear token, use interactive login as the normal path, or copy private issue content into a public wiki. Link the issue in branch and PR metadata through the repository's Git-Spice workflow.
Show full SKILL.md (206 more words)Show less
Developer experience reports
Repository guidance directs systemic developer-experience friction here: broken tooling, a documented command that does not work, verification you cannot perform, or manual work you have now repeated. File the issue; do not rewrite repository guidance to route around the friction.
All agents share one Linear identity, so votes are session-attributed +1
comments, not reactions or labels. Search first, upvote a match, and file a new
issue only when there is no match:
toolkit linear issue query --team AI --search "<keywords>" \
--search-comments --all-states --include-archived --json
toolkit linear issue view <ID> # confirm the same root cause, then read commentsOn a match, check toolkit linear issue comment list <ID> --json for your own
session ID first, then post one vote per session:
toolkit linear issue comment add <ID> --body-file <path>Vote body, first line exactly +1 hit again:
+1 hit again
- Session: <shareable session link or ID, else `unknown`>
- Harness: <e.g. claude-code, muse-code, codex, cursor, unknown>
- Model: <model ID as reported by the harness, else `unknown`>
- Work: <one sentence: what task the friction blocked>
- Diff: <`same as reported`, or how your symptom/output differs>Use ambient harness values when exposed; never invent IDs, and keep tokens and
credential-bearing output out of the comment. Issue frequency is 1 (the report)
plus the number of +1 hit again comments.
Then file one issue per distinct problem:
toolkit linear issue create --no-interactive --team AI \
--project "Developer Experience" --label Improvement \
--title "<surface>: <what breaks>" --description-file <path>--no-interactive is required outside a terminal, and --description-file is
the supported path for a markdown body. That body states the symptom, the exact
command and its real output, what the friction blocked and how often, the
suspected owning path in this repository, and the session link. Report unproven
causes as suspicion, and keep tokens and credential-bearing output out of it.
© shepherdjerred, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/linear-work-management of shepherdjerred/monorepo.
Open the folder on GitHubat commit 46ddf2f
Compare with similar skills
Linear Work Management 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linear Work Management this skillshepherdjerred/monorepo | 112 | — | ~955 | Automated safety check: Pass | GPL-3.0 | |
| Orca Linear Ticket Workflowstablyai/orca | 87k | 1 repos | ~522 | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| Commitdinerojs/dinero.js | 6.8k | — | ~667 | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Linear Tickets via Orcastablyai/orca | 87k | — | ~558 | Automated safety check: Pass | MIT |
Similar skills
- Official
Review Triage Phase
prisma/orm
Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.
Commit
dinerojs/dinero.js
Create a git commit with optional automatic Linear issue linking.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
Linear Tickets via Orca
stablyai/orca
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…
Add Icon Mapping
lobehub/lobe-icons
Add or modify icon keyword mappings for providers, models, or agents in lobe-icons.
More from shepherdjerred/monorepo
All 63 skills in this repoBun Runtime Best Practices
shepherdjerred/monorepo
Bun runtime APIs and current operational patterns for files, processes, modules, networking, databases, tests, and deployment.
Bun Test Patterns
shepherdjerred/monorepo
Current Bun test runner guidance for discovery, isolation, parallelism, sharding, changed tests, mocks, timers, snapshots, coverage, DOM Testing Library, and integration teardown.
Bun Workspaces
shepherdjerred/monorepo
Current Bun workspace guidance for isolated and hoisted linkers, catalogs, filters, scripts, dependency classes, lockfiles, lifecycle trust, caches, publishing, TypeScript package exports, and…
Deep Research
shepherdjerred/monorepo
This skill should be used when the user asks to "deep research", "research this topic", "investigate thoroughly", "do a deep dive on", "comprehensive research on", "find everything about", "survey…
Figma Use
shepherdjerred/monorepo
This skill should be used when the user asks to "create a Figma design", "design in Figma", "make a Figma mockup", "create an app icon", "design UI", "render JSX to Figma", "export from Figma"…
Fish Helper
shepherdjerred/monorepo
Current Fish shell scripting, functions, abbreviations, completions, variables, events, configuration, plugins, testing, and safety guidance.
Related
Works with
Questions about Linear Work Management
What does Linear Work Management do?
Read or manage this repository's Linear issues, projects, cycles, plans, triage, and follow-up work through toolkit linear, including developer-experience friction reports. Linear Work Management is an agent skill from shepherdjerred/monorepo. Read or manage this repository's Linear issues, projects, cycles, plans, triage, and follow-up work through toolkit linear, including developer-experience friction reports.
When should I use Linear Work Management?
Linear Work Management fits situations like: work must be found; linked to a branch; broken tooling must be filed.
How do I install Linear Work Management in Claude Code?
Run `npx skills add shepherdjerred/monorepo --skill linear-work-management -a claude-code`. Or copy the skill folder (.agents/skills/linear-work-management in shepherdjerred/monorepo) into .claude/skills/linear-work-management in your project. Claude Code loads it when a task matches its description.
How do I install Linear Work Management in Codex?
Run `npx skills add shepherdjerred/monorepo --skill linear-work-management -a codex`. Or copy the skill folder (.agents/skills/linear-work-management in shepherdjerred/monorepo) into .agents/skills/linear-work-management in your project. Codex loads it when a task matches its description.
Can I use Linear Work Management 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 shepherdjerred/monorepo --skill linear-work-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-work-management, .gemini/skills/linear-work-management, .github/skills/linear-work-management and .opencode/skills/linear-work-management in your project.
What does Linear Work Management need to run?
SKILL.md names no scripts, command-line tools or credentials: Linear Work Management is instructions for the agent only.
Does Linear Work Management access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Linear Work Management safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Linear Work Management use?
Linear Work Management is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linear Work Management use?
About 955 tokens (SKILL.md is roughly 3.8k 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 Work Management?
Skills that share tags, products or a category with Linear Work Management: Orca Linear Ticket Workflow (stablyai/orca, 87k stars), Review Triage Phase (prisma/orm, 48k stars), Commit (dinerojs/dinero.js, 6.8k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linear Work Management?
shepherdjerred (a GitHub user) maintains it in shepherdjerred/monorepo, which has 112 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on October 7, 2026.
Source: shepherdjerred/monorepo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.