Linear Browser Automation
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a coherent Linear browser-automation skill, but it can use your logged-in Linear session to create, edit, comment on, and bulk-update issues.
Install this only if you are comfortable letting an agent operate your logged-in Linear workspace through the managed browser. For bulk changes or comments, require the agent to show the exact target issues and planned text/status before you confirm.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If installed and invoked, the skill can perform Linear actions as the logged-in user in the managed browser profile.
The skill is designed to operate through an authenticated Linear browser session, so it can act with the user's Linear account permissions.
Always use browser profile: `openclaw` ... Reuse an already-open, logged-in Linear tab in the managed browser whenever available.
Use it only with the intended Linear workspace/account, review the visible target issue or filter scope before actions, and log out of Linear in the managed browser if you do not want this access available.
Mistaken instructions or misunderstood targets could create or change Linear issues, comments, or states.
The skill authorizes browser actions that can mutate Linear workspace data; this is purpose-aligned and includes confirmation rules, but users should recognize the impact.
Supported automations ... Create new issue ... Edit issue fields ... Move issue state ... Add comments ... Bulk triage (limited batch with confirmation)
Before approving actions, verify the team, issue identifier, state, comment text, and any bulk filter scope shown by the agent.
A broad or incorrect filter could update several Linear issues before the mistake is noticed.
Bulk triage can affect multiple issues if a filter is too broad; the workflow requires verification and confirmation, which keeps this purpose-aligned but still noteworthy.
Apply filters ... Announce planned bulk action and ask for confirmation. Execute updates in small batches. Re-snapshot and report changed items.
Ask the agent to list the affected issues and keep batches small before confirming any bulk update.
Users have less external context for who maintains the skill or where its canonical source is hosted.
The artifact provides no upstream source or homepage for provenance review, although there is also no install script or code payload.
Source: unknown; Homepage: none
Prefer installing skills from publishers or repositories you trust, especially for skills that can act in logged-in business tools.