This is the second skill in the X bookmark workflow.
The capture skill stays deterministic: fetch bookmarks, dedupe locally, create raw Linear Triage issues.
This skill handles the next step: read those raw Linear issues, prepare them for an agent review pass, and apply the agent's decisions back to Linear with an audit trail.
What it does
- Finds Linear issues created by
x-bookmark-capture-sync. - Exports review candidates as JSON for Hermes, Codex, or another agent runner.
- Generates a review prompt that asks the agent to use Shape Up thinking.
- Accepts a decisions JSON file from the agent.
- Adds a Linear comment explaining the decision.
- Rewrites the issue title and description for converted or question-needed tasks.
- Tracks processed issue IDs in local JSON state.
Install
Use the install command on this page to copy the public skill files into your local skills directory.
For OpenClaw-style repositories, keep the same folder shape and point the tool at the installed SKILL.md.
Configure
Set these environment variables:
Optional:
Fetch candidates
Fetch raw captures from Linear:
The script looks for issues in your team whose description contains:
The output is intentionally JSON so another agent can score and decide what to do.
Generate the prompt for Hermes, Codex, or another runner:
Agent decision shape
Ask Hermes, Codex, or your runner to read review-prompt.md and write:
Allowed actions:
convert: turn the capture into a real task with a better title/description.question: leave clarifying questions as a comment.park: mark it reviewed but intentionally leave it as a parked capture.
Allowed work types:
blog_postsmall_experimentimplementation_taskresearch_note
Every decision includes Shape Up fields: problem, appetite, pitch, rabbit holes, no-gos, and next action. The point is not to skip Linear. Everything remains a Linear task; Shape Up decides how the task should be handled.
Apply decisions
Preview first:
Then apply:
V1 does not change status, assignee, labels, or priority. It only comments, optionally rewrites title/description, and records processed issue IDs locally.
Cron or heartbeat
The intended heartbeat has two stages:
That keeps the script deterministic and leaves the reasoning step to an agent that can explain its decisions.