---

name: linear-issue-export description: "Export a complete, scoped Linear issue inventory with project identifiers."

Linear Issue Export

Export a complete, scoped Linear issue inventory with project identifiers.

Required Aident Actions

• <action-tag>composio:linear_tools:linear_list_linear_projects</action-tag> (required inputs: inspect the current schema): Retrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use LINEAR_RUN_QUERY_OR_MUTATION for progress, state, issues, or team linkage. No server-side...
• <action-tag>composio:linear_tools:linear_list_linear_issues</action-tag> (required inputs: inspect the current schema): Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. Can filter by assignee_id. Only project_id and assignee_id server-side filters are supported; label,...

Use Aident Loadout to read the cuAction · List Linear Projectstion connection in Aident Vault. If an Action is billable or mutating, run 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, deAction · List Linear Issuessource-derived guidance below to create a concrete plan. 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

• Resolve the project ID, paginate every result set, and preserve stable issue identifiers.
• Return CSV, Markdown, or JSON in the user's requested shape without claiming fields the Actions omit.

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.