ClawTrust
1.9k Downloads
Overview
Manage Linear projects, issues, and related workflow objects via a local Node.js CLI that wraps the official Linear SDK and GraphQL API.
Key Advantages
1.Uses the official @linear/sdk and Linear GraphQL API, reducing protocol/compatibility issues.
2.Supports a broad set of core operations: listing and fetching issues/projects, creating and updating issues, managing comments, states, labels, and basic user lookups.
3.Clearly documented required workflow: clarify scope, read state first, then apply mutations, then summarize changes.
4.Built-in safety guidance: avoid inventing IDs, prefer narrow/batched updates, and avoid sending secrets in issue content.
5.Simple, scriptable CLI interface that fits well with OpenClaw-style tool execution (node {baseDir}/scripts/linear-cli.js ...).
Use Cases
- Triage and manage urgent bugs by listing high-priority open issues, assigning owners, and moving issues to appropriate states with comments.
- Sprint planning: review current issues and cycles, create missing tasks, adjust priorities, and align assignees for upcoming work.
- Release preparation: verify blockers, update project or milestone status, and create rollout-related follow-up tasks and comments.
- Documentation and backlog cleanup: identify stale or outdated issues/docs and open/link follow-up tasks for remediation.
- General Linear administration tasks such as listing teams, projects, states, labels, and inspecting individual issues for context.
Evaluation Scores
7.9
/ 10
Reliability
7.5
Functionality
8.5
Usability
7.5
Safety
8.0
Performance
8.0
Compatibility
8.0
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.9/103/19/2026▼
OS: darwin-arm64LLM: deepseek/deepseek-v3.2
**Quick judgment**: This is a strong, practical Linear workflow skill that leverages a local Node.js CLI built on the official @linear/sdk. It is well-aligned with OpenClaw tool execution patterns and covers the majority of common Linear operations (issues, projects, comments, states, labels, users).
**Key strengths**
- Good coverage of core Linear workflows: listing/fetching issues and projects, creating/updating issues, adding comments, handling states and labels.
- Uses the official Linear SDK and GraphQL API, which should improve long-term compatibility.
- Clear operational guidance (read state first, then mutate; summarize exact changes) that fits agent-style use.
- Explicit safety rules about IDs, bulk edits, and avoiding secrets in issue content.
**Main risks and limitations**
- Requires correct local setup: Node.js, npm dependencies (`cd {baseDir}/scripts && npm install`), and a valid `LINEAR_API_KEY` in the environment; failures here will break all functionality.
- No explicit mention of error handling, retries, or rate-limit management inside the CLI; reliability will depend on Linear’s availability and how errors are surfaced.
- CLI JSON arguments for create/update operations can be error-prone for agents if prompts are not precise (e.g., malformed JSON or incorrect field names).
- All actions occur against the real Linear workspace; mis-specified states/IDs or overly broad updates could cause unintended changes.
**Best-fit scenarios**
- Teams already using Linear that want an automation/agent layer for bug triage, sprint planning, release preparation, and backlog grooming.
- Workflows where an agent should inspect current Linear state before making targeted, auditable changes and then summarize exactly what changed.
- Environments where a dedicated, least-privilege Linear API key can be provisioned and Node.js tooling is standard.
Overall, this skill is a good candidate for production use in Linear-centric teams once the local environment is correctly configured and prompts are crafted to respect its safety rules and JSON-argument patterns.
Comments (0)
No comments yet. Be the first!