linear

name	linear
description	Use Armorer-managed Linear tools for issue lookup, PM coordination, status summaries, and approval-gated task updates.
runtime	armorer-linear
capabilities	["linear.issue.read","linear.issue.lookup","linear.issue.comment.request","linear.issue.update.request","linear.customer_sync.queue","linear.customer_sync.sync"]

linear

Use Armorer's Linear tools when work requires reading project tasks, checking issue state, preparing PM coordination notes, or drafting tracker updates.

The PM agent should use this skill as its default Linear path. In the current company-agent set, Atlas may use this skill as the PM/coordinator agent when no dedicated pm install exists.

Commands

Use the Armorer CLI surface instead of direct Linear credentials:

armorer linear status
armorer linear issue ARM-184
armorer linear instructions atlas
armorer linear request-comment --issue ARM-184 --body "Draft update..."
armorer linear request-update --issue ARM-184 --field state --value "In Review"
armorer linear customer-sync list
armorer linear customer-sync add --agent scout-native --json '{"customer":{"name":"Example Co","domains":["example.com"],"external_id":"scout:example.com"},"issue":{"team_id":"TEAM_ID","title":"Design partner signal: Example Co"},"need":{"body":"Qualified product signal with source evidence.","attachment_url":"https://example.com/source"}}'
armorer linear customer-sync run --agent scout-native --row <row-id>

For longer request bodies, pass the body over stdin:

printf '%s\n' "Draft update..." | armorer linear request-comment --issue ARM-184

Behavior

• Treat armorer linear issue <identifier> as read-only issue lookup.
• Use Linear reads to ground PM summaries, ownership questions, acceptance criteria, and follow-up planning.
• Stage comments or issue changes with armorer linear request-* commands; these create approval-ready requests instead of mutating Linear directly.
• For qualified CRM/customer signals, queue first with armorer linear customer-sync add, then sync only when the installed agent has an explicit Linear Vault connection grant for linear.customer_sync.sync.
• A successful customer sync marks the local row with Linear customer, issue, customer-need, and comment ids when those objects are created.
• Keep user-facing status exact: include the issue identifier, title, current state, and link when available.
• If Linear credentials are missing, report the missing Armorer secret rather than asking for raw credentials in chat.

Safety

• Do not close issues, change assignees, create public comments, change priority, or edit customer-impacting task state without explicit human approval.
• Do not expose Linear API keys or token values.
• Do not use installed-agent raw Linear credentials to bypass Armorer Vault connection grants.
• Do not mirror private issue content to Telegram unless the human explicitly asks for a summary there.
• Redact credentials, access tokens, passwords, and secret-looking values in comments, summaries, and logs.