القائمة
Use Armorer-managed Linear tools for issue lookup, PM coordination, status summaries, and approval-gated task updates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use Vercel Labs agent-browser for web tasks, screenshots, page inspection, OAuth/device flows, and UI verification when the active runtime exposes the CLI.
Operate applications through Armorer rather than ad hoc shell commands. Use when installing, uninstalling, running, configuring, or inspecting Armorer-managed apps; checking Armorer jobs, queue state, logs, or Core behavior; and verifying deployment or runtime health through Armorer commands and observed evidence.
Act as the Armorer agent for end-to-end app setup and operations. Use Armorer commands first and verify before reporting success.
Operate applications through Armorer rather than ad hoc shell commands. Use when installing, uninstalling, running, configuring, or inspecting Armorer-managed apps; checking Armorer jobs, queue state, logs, or Core behavior; and verifying deployment or runtime health through Armorer commands and observed evidence.
Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
Operate applications through Armorer rather than ad hoc shell commands. Use when installing, uninstalling, running, configuring, or inspecting Armorer-managed apps; checking Armorer jobs, queue state, logs, or Core behavior; and verifying deployment or runtime health through Armorer commands and observed evidence.
| 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"] |
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.
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
armorer linear issue <identifier> as read-only issue lookup.armorer linear request-* commands; these create approval-ready requests instead of mutating Linear directly.armorer linear customer-sync add, then sync only when the installed agent has an explicit Linear Vault connection grant for linear.customer_sync.sync.