.claude/skills/chrome-linear/SKILL.md
# CHROME-LINEAR-TRIAGE SKILL **Skill Name**: chrome-linear-triage **Version**: 1.0.0 **Trigger**: `/chrome-linear`, "triage linear in browser", "open linear", "check linear board" **Description**: Open Linear in Chrome, screenshot current board state, triage issues, and update statuses without leaving the browser. --- ## SKILL PURPOSE Navigate to the Linear workspace in Chrome, capture the board, triage backlog issues visually, and mark issues Done/In Progress directly through the browser wh
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/chrome-linearInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Skill Name: chrome-linear-triage
Version: 1.0.0
Trigger: /chrome-linear, "triage linear in browser", "open linear", "check linear board"
Description: Open Linear in Chrome, screenshot current board state, triage issues, and update statuses without leaving the browser.
Navigate to the Linear workspace in Chrome, capture the board, triage backlog issues visually, and mark issues Done/In Progress directly through the browser when the Linear MCP is unavailable or when visual confirmation is needed.
Trigger phrases:
/chrome-linearmcp__Claude_in_Chrome__navigate: https://linear.app
Take a screenshot to confirm login state:
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
If redirected to login page → stop and tell user they need to be logged into Linear in Chrome.
mcp__Claude_in_Chrome__get_page_text
Find the CCW / Unite workspace and navigate to the active cycle or backlog view.
mcp__Claude_in_Chrome__find: { selector: "[data-testid='sidebar-team']" }
Take a full-page screenshot of the current board state.
mcp__Claude_in_Chrome__get_page_text
Extract all visible issues: ID, title, status, assignee, priority. Present a structured table to the user:
| ID | Title | Status | Priority |
|----------|-------------------------------|-----------|----------|
| UNI-XXXX | ... | Backlog | High |
For each issue to update:
mcp__Claude_in_Chrome__computer: { action: "click", coordinate: [x, y] }
After all updates:
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
Report: issues triaged, final states, any failures.
User: "Open linear and show me what's in backlog"
Response:
Opening Linear in Chrome...
[screenshot of board]
Current Backlog (7 issues):
| ID | Title | Priority |
|----------|------------------------------|----------|
| UNI-1751 | Upload YouTube demo videos | High |
| UNI-1752 | ElevenLabs audio regen | Medium |
...
Which would you like to update?
After any status change, confirm:
https://linear.app fresh and retry.Version: 1.0
Created: April 2026
Tools: mcp__Claude_in_Chrome__*
content-media
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
data-ai
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
tools
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
development
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)