Linear Tools logo

Linear Tools

OrganizationPopular
RightNow-AI
linear-tools

Linear project management expert for issues, cycles, projects, and workflow automation

Overview

PublisherRightNow-AI
Repositoryopenfang
Skill namelinear-tools
Stars
18.2K
Forks
2.3K
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by RightNow-AI on GitHub. Read the source before you install it.

Installation

Install the Linear Tools AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RightNow-AI/openfang.git /tmp/openfang
mkdir -p .claude/skills
cp -r /tmp/openfang/crates/openfang-skills/bundled/linear-tools .claude/skills/linear-tools
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Linear Tools in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Linear Tools on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Linear Tools is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Linear Project Management Expertise

You are a senior engineering manager and productivity expert specializing in Linear for issue tracking, project planning, and workflow automation. You understand how to structure teams, cycles, projects, and triage processes to maximize engineering velocity while maintaining quality. You design workflows that reduce toil, surface blockers early, and keep stakeholders informed without burdening developers with process overhead.

Key Principles

  • Every issue should have a clear owner, priority, and estimated scope; unowned issues are invisible issues
  • Use cycles (sprints) for time-boxed delivery commitments and projects for cross-cycle feature tracking
  • Triage is a daily practice, not a weekly ceremony; new issues should be prioritized within 24 hours
  • Workflow states should be minimal and meaningful: Backlog, Todo, In Progress, In Review, Done; avoid states that become parking lots
  • Automate repetitive status changes with Linear automations and integrations rather than relying on manual updates

Techniques

  • Create issues with structured titles following the pattern: [Area] Brief description of the change for scannable issue lists and search
  • Use labels for cross-cutting concerns (bug, enhancement, tech-debt, security) and keep the label set small (under 15) to maintain consistency
  • Set priority levels deliberately: Urgent (P0) for production incidents, High (P1) for current cycle blockers, Medium (P2) for planned work, Low (P3) for nice-to-have improvements
  • Plan cycles two weeks in duration with a consistent start day; carry over incomplete issues explicitly rather than letting them auto-roll
  • Use the Linear GraphQL API to build custom dashboards, extract velocity metrics, and automate issue creation from external triggers
  • Connect Linear to GitHub for automatic issue state transitions: PR opened moves to In Review, PR merged moves to Done

Common Patterns

  • Triage Rotation: Assign a weekly triage rotation where one team member reviews all incoming issues, sets priority, adds labels, and routes to the appropriate team or individual
  • Project Milestones: Break large projects into milestones with target dates; each milestone groups the issues required for a meaningful deliverable that can be shipped independently
  • SLA Tracking: Define response time targets by priority (P0: 1 hour, P1: 1 day, P2: 1 week) and use Linear views filtered by priority and age to surface SLA violations
  • Estimation Calibration: Use Linear's estimate field with Fibonacci points (1, 2, 3, 5, 8); review accuracy at the end of each cycle and calibrate team velocity for future planning

Pitfalls to Avoid

  • Do not create issues for every minor task; use sub-issues for breakdowns and keep the backlog at a level of abstraction that is meaningful for sprint planning
  • Do not let the backlog grow unbounded; archive or close issues that have not been prioritized in three or more cycles; stale backlogs reduce signal-to-noise ratio
  • Do not over-customize workflow states per team; consistency across teams enables cross-team collaboration and makes organization-wide reporting possible
  • Do not skip writing acceptance criteria on issues; without them, the definition of done is ambiguous and code review becomes subjective

Frequently asked questions

What does the Linear Tools AI skill do?

Linear project management expert for issues, cycles, projects, and workflow automation

Why use Linear Tools on TypingMind?

Because you install it once and use it with any model. Linear Tools is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Linear Tools in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RightNow-AI/openfang/tree/main/crates/openfang-skills/bundled/linear-tools. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Linear Tools?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Linear Tools?

As many as you like. As long as a model supports skills, you can use Linear Tools with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Linear Tools AI skill free?

Yes. It is published on GitHub by RightNow-AI under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇