OpenClaw

linear-browser-automation

Automate Linear.app workflows in the OpenClaw-managed browser profile using browser tool actions (open, navigate, snapshot, act). Use when users want UI-based Linear automation such as triage, issue updates, comments, filtering, bulk state changes, and visual verification in the managed OpenClaw browser.

hassam-powerhouse0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install hassam-powerhouse/lba

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Linear Browser Automation

Automate Linear workflows through UI interactions in the OpenClaw-managed browser.

Execution mode

Always use browser profile: openclaw
Always run actions against host browser control
Reuse an already-open, logged-in Linear tab in the managed browser whenever available.
Do not open a new Linear tab if an existing authenticated Linear tab can be reused.
Keep actions in one tab unless explicitly opening a new tab is required by user request.

Standard workflow

Ensure managed browser is running (profile="openclaw").
Check existing open tabs in managed browser and prefer a tab already on Linear.
If an existing Linear tab is found:
- focus and reuse that tab
- snapshot and detect auth state
If no Linear tab exists, open/navigate to https://linear.app/.
If on public landing page / unauthenticated state:
- automatically navigate to /login
- show a browser alert asking the user to log in to continue
- wait for authenticated dashboard/workspace state
After login is complete and dashboard is visible, continue automatically from the same task context and same tab.
Resolve references from the snapshot.
Execute deterministic actions (click/type/select/press).
Re-snapshot and verify expected state before finishing.

Required-input policy (hard rule)

For all Linear actions, always collect and confirm required details in chat before executing.

1) Create issue

Required fields:

Team (or project context that implies team)
Title

Optional fields (prompt if missing): description, priority, assignee, labels, due date.

Before submission, always present a summary block and ask:

Proceed? (yes/no)

Only proceed on explicit yes. Any other response (no/cancel/edit/silence) means do not submit.

2) Edit issue and comment on issue

Required fields:

Team name
Issue number/identifier (e.g., POW-123)

Hard rule:

Do not run these automations when either team nam...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/hassam-powerhouse/lba
Version: —
Commit: b687eea927afdfaad73032a19eb6679b7a6c5a75
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Linear Browser Automation

Automate Linear workflows through UI interactions in the OpenClaw-managed browser.

## Execution mode

- Always use browser profile: `openclaw`
- Always run actions against host browser control
- Reuse an already-open, logged-in Linear tab in the managed browser whenever available.
- Do not open a new Linear tab if an existing authenticated Linear tab can be reused.
- Keep actions in one tab unless explicitly opening a new tab is required by user request.

## Standard workflow

1. Ensure managed browser is running (`profile="openclaw"`).
2. Check existing open tabs in managed browser and prefer a tab already on Linear.
3. If an existing Linear tab is found:
- focus and reuse that tab
- snapshot and detect auth state
4. If no Linear tab exists, open/navigate to `https://linear.app/`.
5. If on public landing page / unauthenticated state:
- automatically navigate to `/login`
- show a browser alert asking the user to log in to continue
- wait for authenticated dashboard/workspace state
6. After login is complete and dashboard is visible, continue automatically from the same task context and same tab.
7. Resolve references from the snapshot.
8. Execute deterministic actions (click/type/select/press).
9. Re-snapshot and verify expected state before finishing.

## Required-input policy (hard rule)

For all Linear actions, always collect and confirm required details in chat before executing.

### 1) Create issue

Required fields:
1. Team (or project context that implies team)
2. Title

Optional fields (prompt if missing): description, priority, assignee, labels, due date.

Before submission, always present a summary block and ask:
- **`Proceed? (yes/no)`**

Only proceed on explicit **yes**.
Any other response (no/cancel/edit/silence) means do not submit.

### 2) Edit issue and comment on issue

Required fields:
1. Team name
2. Issue number/identifier (e.g., `POW-123`)

Hard rule:
- Do not run these automations when either team nam...

搜索