---

name: linear-inbox-triage description: "Review a team's Linear issues, update one triage decision, and document the rationale."

Linear Inbox Triage

Review a team's Linear issues, update one triage decision, and document the rationale.

Required Aident Actions

• <action-tag>composio:linear_tools:linear_list_issues_by_team_id</action-tag> (required inputs: team_id): Tool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than...
• <action-tag>composio:linear_tools:linear_update_issue</action-tag> (required inputs: issueId): Updates an existing Linear issue using its issue_id; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.) must be valid UUIDs - only issueId...
• <action-tag>composio:linear_tools:linear_create_linear_comment</action-tag> (required iAction · List Issues By Team Idis action modifies shared workspace data and is not reversible - confirm the target issue and comment content before executing.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration Action · Update Issuerun Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance Action · Create Linear Commentlan. Resolve ambiguity before invoking an Action.
2. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
3. Inspect the current schema and prepare the minimum valid input for each selected Action.
4. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
5. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Apply explicit severity, ownership, and duplicate rules to a bounded issue set.
• Confirm the chosen issue and field changes, then post a concise rationale comment.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.