@sentry/junior-linear 0.18.0

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,32 @@
+# @sentry/junior-linear
+
+`@sentry/junior-linear` adds Linear issue workflows to Junior through Linear's hosted MCP server.
+
+Install it alongside `@sentry/junior`:
+
+```bash
+pnpm add @sentry/junior @sentry/junior-linear
+```
+
+Then register the plugin package in `juniorNitro(...)`:
+
+```ts title="nitro.config.ts"
+juniorNitro({
+  pluginPackages: ["@sentry/junior-linear"],
+});
+```
+
+This package does not require a shared `LINEAR_API_KEY` or a custom OAuth app for the default setup. Each user connects their own Linear account the first time Junior calls a Linear MCP tool. Junior sends the authorization link privately and resumes the same Slack thread automatically after the user authorizes.
+
+The package is designed for ticket-centric work: finding issues, creating issues, updating fields, adding comments, and moving work through the normal Linear workflow without leaving Slack.
+
+Optional: set channel defaults when a Slack thread usually routes work to the same Linear destination:
+
+```bash
+jr-rpc config set linear.team Platform
+jr-rpc config set linear.project "Cross-team reliability"
+```
+
+These defaults are only fallbacks. If the user names a different team or project in the request, Junior should follow the explicit request instead.
+
+Full setup guide: https://junior.sentry.dev/extend/linear-plugin/

package/package.json

@@ -0,0 +1,13 @@
+{
+  "name": "@sentry/junior-linear",
+  "version": "0.18.0",
+  "private": false,
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "files": [
+    "plugin.yaml",
+    "skills"
+  ]
+}

package/plugin.yaml

@@ -0,0 +1,10 @@
+name: linear
+description: Linear issue tracking via hosted MCP server
+
+config-keys:
+  - team
+  - project
+
+mcp:
+  transport: http
+  url: https://mcp.linear.app/mcp

package/skills/linear/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: linear
+description: Manage Linear issues through Linear's hosted MCP server. Use when users ask to create a Linear ticket, update a Linear issue, add a Linear comment, move work between states, assign work, or look up Linear issue, team, or project details from Slack context.
+uses-config: linear.team linear.project
+---
+
+# Linear Operations
+
+Use this skill for Linear issue workflows in the harness.
+
+## Reference loading
+
+Load references conditionally based on the request:
+
+| Need                                             | Read                                                                                   |
+| ------------------------------------------------ | -------------------------------------------------------------------------------------- |
+| Any Linear operation                             | [references/api-surface.md](references/api-surface.md)                                 |
+| Create, update, comment, assign, or state change | [references/common-use-cases.md](references/common-use-cases.md), [references/issue-writing.md](references/issue-writing.md) |
+| Auth issues, ambiguity, or tool failures         | [references/troubleshooting-workarounds.md](references/troubleshooting-workarounds.md) |
+
+## Workflow
+
+1. Resolve the operation and target:
+
+- Determine whether the request is read-only inspection, issue creation, comment, field update, assignment, or state transition.
+- Prefer explicit issue identifiers, issue URLs, project names, team names, or assignees when the user provides them.
+- When the user did not specify a destination, treat `linear.team` and `linear.project` conversation config as optional defaults. Explicit user input always wins over config.
+- Only set or change `linear.team` and `linear.project` when the user explicitly asks to store a default for this conversation or channel.
+- For issue creation, resolve the target team before drafting because every Linear issue belongs to a single team.
+- If `linear.project` is configured, use it as the default project only when the request does not name a different project and the project fits the current task.
+- If the request refers to an existing Linear item indirectly, inspect the current thread context for the previously mentioned issue key or URL before asking the user to restate it.
+- Ask one concise follow-up only when a write is blocked after considering both explicit user input and any configured defaults, such as multiple plausible teams, no clear target issue, or no valid team for a new issue.
+
+2. Use the active Linear MCP tools:
+
+- `loadSkill` returns `available_tools` for this skill, including the exact `tool_name` values and input schemas exposed in this turn.
+- Call those exact tool names directly. Use `searchTools` only if you need to rediscover or filter the active Linear tools later in the turn.
+- Prefer a short read/search step before mutating when you need to confirm the existing issue, team, project, or workflow state.
+- For create/update operations, classify the work as a `bug`, `feature`, or `task` and shape the title/body accordingly.
+- For issue creation, ground the ticket in the actual engineering problem:
+  - summarize the problem, impact, and expected outcome from the Slack thread
+  - preserve relevant URLs already present in the conversation, such as Sentry, GitHub, docs, or reproduction links
+  - translate Slack-specific phrasing into product or engineering language
+  - remove usernames, channel names, slash commands, and session chatter unless the user explicitly wants them preserved
+- When setting optional fields, stay literal:
+  - use the team's actual workflow states instead of assuming generic names like `Todo` or `In Progress`
+  - use only Linear's standard priority levels: `low`, `medium`, `high`, `urgent`
+  - set project, labels, cycle, estimate, or assignee only when the user asked for them or the thread makes them clear
+- For updates, prefer partial changes over full rewrites. Fetch current issue state first if the mutation could overwrite structured fields or duplicate an existing comment.
+- Check for duplicates silently before creating a new issue when the request appears related to existing work.
+- When the thread clearly indicates the work originated in Slack, mention that succinctly in the Linear ticket or comment if it improves provenance, but do not paste large thread transcripts.
+
+3. Report the result:
+
+- Return the canonical Linear issue URL or key and summarize what changed.
+- Report issue type when you created a new issue and it materially clarifies the outcome.
+- Keep routine tool chatter silent. Do not narrate each MCP search or mutation step.
+
+## Guardrails
+
+- Reuse or update an existing Linear issue when it is clearly the same work instead of creating a duplicate.
+- Do not present guesses as facts. If the thread leaves an important detail uncertain, label it as an assumption in the Linear content.
+- Prefer concise, durable ticket text over verbatim Slack quotes or long transcript dumps.
+- Do not invent team-specific workflow names, labels, or estimate values without first confirming they exist.
+- If Linear authorization is required, let the MCP OAuth flow pause and resume the thread automatically instead of asking the user to handle credentials manually.

package/skills/linear/references/api-surface.md

@@ -0,0 +1,74 @@
+# API Surface
+
+Use this reference for any Linear operation.
+
+## Runtime contract
+
+- `loadSkill` returns `available_tools` for this skill, including the exact Linear MCP `tool_name` values exposed in the current turn.
+- Call those exact `tool_name` values directly.
+- Use `searchTools` only when you need to rediscover or filter the active Linear tools later in the same turn.
+- Do not hardcode raw Linear MCP tool names in advance. Tool discovery is part of the workflow.
+- Return the canonical Linear issue key or URL after successful writes.
+
+## Provider capabilities
+
+Linear's hosted MCP server is intended for authenticated remote MCP access to Linear data.
+The current public docs describe support for finding, creating, and updating objects such as issues, projects, and comments.
+
+## Linear issue model constraints
+
+- Every issue belongs to exactly one team.
+- A new issue requires a title and a status; all other properties are optional.
+- Workflow states are team-specific. The common default order is `Backlog > Todo > In Progress > Done > Canceled`, but teams can customize names and ordering.
+- Priority is optional and limited to `low`, `medium`, `high`, or `urgent`.
+- Labels can be workspace-scoped or team-scoped.
+- Estimates are optional and team-configured.
+
+## Operation patterns
+
+| Intent               | Minimum tool pattern                                                                                             |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| Inspect an issue     | Resolve the issue by key, URL, or search query, then fetch current state before answering.                       |
+| Create an issue      | Confirm the team first, then create the issue with grounded title/body content and only the optional fields you can justify. |
+| Update fields        | Fetch current issue state first, then mutate only the requested fields.                                          |
+| Add a comment        | Resolve the exact issue first, then add a concise comment with durable links and next steps.                     |
+| Move state or assign | Read the current issue and team workflow first when state, workflow, or assignee ambiguity could cause the wrong mutation. |
+| Check for duplicates | Search for an existing matching issue before opening a new one when the request appears related to ongoing work. |
+
+## Config helpers
+
+Use these commands only when the user explicitly asks to inspect or store Linear defaults for the current conversation/channel.
+
+Resolve team default:
+
+```bash
+jr-rpc config get linear.team
+```
+
+Set team default:
+
+```bash
+jr-rpc config set linear.team Platform
+```
+
+Resolve project default:
+
+```bash
+jr-rpc config get linear.project
+```
+
+Set project default:
+
+```bash
+jr-rpc config set linear.project "Cross-team reliability"
+```
+
+## Content expectations
+
+- Translate Slack-thread wording into stable product or engineering language.
+- Preserve material links already present in the conversation, such as Sentry, GitHub, docs, repro, or dashboard URLs.
+- If the active MCP tool exposes structured link attachments, prefer those over burying important URLs only inside the prose body.
+- Keep provenance concise. Mention Slack origin only when it helps future readers understand why the issue exists.
+- Treat team, status, labels, estimate, cycle, and project as structured properties, not prose-only body content, when the MCP tool exposes them and the values are actually known.
+- Prefer partial updates over full rewrites.
+- Label assumptions clearly when the thread leaves important details uncertain.

package/skills/linear/references/common-use-cases.md

@@ -0,0 +1,70 @@
+# Common Use Cases
+
+Use these patterns to shape concrete Linear requests.
+
+## 1. Create a bug from a Slack incident thread
+
+- Summarize the broken behavior, impact, and expected behavior.
+- Resolve the right team before creating because Linear issues cannot be created without one.
+- If the thread does not name a destination, use `linear.team` and `linear.project` channel defaults before asking a follow-up.
+- Preserve relevant Sentry, GitHub, replay, trace, or dashboard links from the thread.
+- Use a durable title that describes the engineering problem rather than the Slack conversation.
+
+## 2. Create a follow-up task from a debugging thread
+
+- Convert the thread into a scoped task when the work is cleanup, hardening, docs, or instrumentation rather than a production bug.
+- Keep the body focused on the desired outcome and concrete next step.
+- Set project, cycle, or assignee only when the destination is already clear from the thread.
+
+## 3. Search for an existing issue before opening a new one
+
+- Search by issue key when present.
+- Otherwise search by the core problem statement, feature name, or affected subsystem.
+- Reuse the existing issue when the work is clearly the same and add context there instead of creating a duplicate.
+
+## 4. Add a comment with new evidence
+
+- Attach fresh context such as a repro step, stack trace summary, rollout note, or supporting URL.
+- Avoid repeating the entire thread when a short comment plus links is enough.
+
+## 5. Move work through the workflow
+
+- Resolve the current issue first.
+- Read the team's actual workflow states first if the requested move uses category language like `started`, `done`, or `canceled` rather than an exact state name.
+- Update state only after confirming the target issue and intended transition.
+- Mention the reason for the transition when it is not obvious from the issue history.
+
+## 6. Reassign work or change ownership
+
+- Resolve the issue and confirm the target assignee when names are ambiguous.
+- Keep the mutation small. Do not rewrite unrelated fields.
+- Preserve the current project, labels, and workflow state unless the user asked to change them too.
+
+## 7. Tighten an existing issue description
+
+- Fetch the current issue before editing.
+- Preserve existing accepted context, then add missing impact, reproduction, or expected outcome details from the thread.
+- Avoid overwriting structured content unless the user explicitly asks for a rewrite.
+
+## 8. Create a ticket with Slack provenance but not Slack noise
+
+- Mention that the work originated from a Slack discussion only when that context helps future readers.
+- Strip usernames, channel references, slash commands, and conversational filler unless the user explicitly wants them preserved.
+
+## 9. Set priority, labels, or estimate from thread context
+
+- Use only Linear's standard priority levels: `low`, `medium`, `high`, `urgent`.
+- Reuse existing labels when the thread makes the intended label clear; do not invent lookalike labels casually.
+- Set an estimate only when the value is explicit or already established in the team context, since estimate scales are team-configured.
+
+## 10. Mark work as a duplicate
+
+- Search for the canonical destination issue first.
+- If the MCP tool supports duplicate relationships directly, use that instead of only posting a comment.
+- If the workflow exposes a dedicated duplicate status, prefer it; otherwise expect duplicate handling to land in the team's canceled category.
+
+## 11. When a user asks to set channel defaults for a Linear-heavy Slack thread
+
+- Use `jr-rpc config set linear.team <team name or key>` when the user explicitly asks to store a team default and the channel consistently routes new work to the same team.
+- Use `jr-rpc config set linear.project <project name>` when the user explicitly asks to store a project default and the channel mostly tracks one project.
+- Treat both defaults as optional. Explicit user input wins whenever a request names a different team or project.

package/skills/linear/references/issue-writing.md

@@ -0,0 +1,46 @@
+# Issue Writing
+
+Use this reference when creating a new Linear issue or substantially improving an existing one.
+
+## Classify the work item
+
+Infer the issue shape before drafting:
+
+| Type | Use when | Default structure |
+| ---- | -------- | ----------------- |
+| `bug` | Broken behavior, regressions, failures, incidents, or user-visible defects | Summary, impact, reproduction or evidence, expected behavior |
+| `feature` | Net-new capability, product expansion, or workflow improvement | Summary, current gap, desired outcome, tradeoffs or recommendation |
+| `task` | Cleanup, instrumentation, docs, maintenance, follow-up, or operational work | Summary, background, scope, next step |
+
+Default to `task` when the request does not clearly describe a defect or a net-new capability.
+
+## Drafting rules
+
+- Use a durable title that describes the engineering or product problem, not the Slack conversation.
+- Keep the opening summary short and information-dense.
+- Generalize Slack context: remove usernames, channel names, slash commands, and session chatter unless the user explicitly wants them preserved.
+- Preserve material evidence already present in the thread, especially Sentry, GitHub, replay, trace, dashboard, or docs URLs.
+- Include code snippets, stack traces, or exact commands only when they materially improve the future implementer's understanding.
+- Keep body structure problem-specific. Use headings like `Current behavior`, `Impact`, `Reproduction`, `Expected behavior`, `Scope`, or `Recommendation` only when they help.
+
+## Linear-specific field guidance
+
+- Every new issue must belong to a single team. Resolve that before creating the issue.
+- If the request clearly maps to a known team template and the active MCP tools expose template-based creation, prefer the template so the team's default properties are applied consistently.
+- Set optional fields such as project, priority, labels, cycle, estimate, assignee, or status only when the user asked for them, the thread gives clear evidence, or the team's workflow makes the choice obvious.
+- Do not invent a custom status name. If you need a non-default status, read the team's actual workflow states first.
+- Priority should stay within Linear's standard levels: `low`, `medium`, `high`, `urgent`.
+- Estimates are team-configured. Only set one when the thread provides a clear value or the team context already makes the estimate scale unambiguous.
+- Labels may be workspace- or team-scoped. Reuse an existing matching label when possible instead of introducing near-duplicates.
+- If the tool exposes structured link attachments, attach the important URLs there and keep the prose body focused on interpretation rather than raw link dumping.
+
+## Duplicate handling
+
+- Search silently before creating a new issue when the request appears related to existing work.
+- If a clear duplicate exists, prefer updating or commenting on the existing issue instead of creating a new one.
+- If the user explicitly wants a separate tracking issue anyway, state the relationship clearly in the new issue.
+
+## Result reporting
+
+- Report only the final, durable result: issue key, canonical URL, and what changed.
+- Keep routine drafting, search, and mutation steps silent unless they materially affect the outcome.

package/skills/linear/references/troubleshooting-workarounds.md

@@ -0,0 +1,19 @@
+# Troubleshooting and Workarounds
+
+Use this reference when Linear MCP work fails or the request is ambiguous.
+
+| Symptom                                                   | Likely cause                                                                    | Response                                                                                                                                  |
+| --------------------------------------------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| No Linear tools are available after loading the skill     | The skill was not loaded or the provider tools were not activated for the turn  | Load the skill first and use the returned `available_tools`; use `searchTools` only if you need to rediscover them later in the turn.     |
+| Linear asks for authorization                             | The user has not connected Linear MCP access yet                                | Let the MCP OAuth flow pause and resume automatically; do not ask the user to paste credentials manually.                                 |
+| Authorization completes but the write still fails         | The connected Linear account lacks access to the target team, project, or issue | Retry only after confirming the target is visible to the user; otherwise explain the concrete access blocker.                             |
+| Creating a new issue is blocked                           | No team was resolved for the issue                                              | Ask for the team only when it is not already clear from the thread, project context, or existing issue references.                        |
+| Search returns too many matches                           | The request lacks a specific issue key, team, project, or title phrase          | Narrow the search with the most specific identifier present in the thread, then ask one concise follow-up only if ambiguity remains.      |
+| The request might create a duplicate issue                | Similar work already exists in Linear                                           | Search before creating; if a clear match exists, update or comment on that issue instead of opening a new one.                            |
+| A mutation could overwrite good structured content        | The request asks for broad edits without showing current issue state            | Fetch the current issue first and prefer partial updates over full body rewrites.                                                         |
+| A requested status name does not exist                    | Workflow states are team-specific                                               | Read the team's actual states and map the user's intent to a real state instead of inventing one.                                         |
+| Priority or estimate is unclear                           | Linear uses constrained priorities and team-configured estimate scales          | Use only `low`, `medium`, `high`, or `urgent`; avoid setting an estimate unless the value is explicit or the team scale is already known. |
+| The draft issue reads like Slack chat instead of a ticket | The content copied conversational phrasing directly from the thread             | Rewrite into product or engineering language, preserve only material links, and remove usernames, channel names, and slash-command noise. |
+| A comment or update repeats existing context              | The thread already includes the same evidence in the issue history              | Fetch current issue state first, then add only the new evidence or decision.                                                              |
+| The team or project is unclear                            | The Slack request does not say where the issue belongs                          | Inspect thread context for earlier mentions, then ask one direct question only if the write is still blocked.                             |
+| The result lacks a durable handoff                        | The reply reports success without the canonical issue reference                 | Return the Linear issue key or URL and summarize the exact change that was made.                                                          |