Linear (1)

**Quick judgment**: Solid, practical Linear CLI skill that covers most day-to-day issue and project workflows. It’s well-suited for teams wanting tight integration between Linear, Git, and GitHub, but it assumes you’re comfortable with environment variables, CLI usage, and giving the tool write access to your Linear workspace. **What it does well** - Streamlines common workflows: standup summaries, “my issues/todos,” urgent triage, project/issue lookup. - Supports full lifecycle actions: create issues, comment, change status, assign, and set priorities. - Provides a clear Git/GitHub workflow using Linear-derived branch names, aligning with Linear’s PR automation. - Uses a simple env-based setup (LINEAR_API_KEY, LINEAR_DEFAULT_TEAM) and offers cached team discovery. **Key risks / limitations** - Requires a Linear API key with write access; misconfiguration or compromised environment variables could expose your workspace. - No visible mention of granular safety rails (e.g., confirmations for destructive/large-scale changes, dry-run mode). - Functionality focuses on mainstream workflows; advanced Linear features (labels, cycles, roadmaps, complex filters) are not described. - Being a bash-based CLI, it’s naturally more at home in Unix-like environments and may be less friendly on non-Linux systems without adaptation. **Recommended scenarios** - Engineering teams that already use Linear and GitHub and want agents or scripts to participate in daily standups, triage, and issue housekeeping. - Developers who want fast CLI shortcuts for creating and managing issues from their terminal or chat-based automation. - Workflows where automated branch naming and PR-based status updates are important, and where keeping `main` clean via worktrees is a priority. - OpenClaw setups that need a reliable, opinionated interface to Linear for routine project-management automations rather than deep administrative control of Linear itself.