Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage Linear issues, projects, and team workflows.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Manage issues, check project status, and stay on top of your team's work.
export LINEAR_API_KEY="your-api-key"
# Optional: default team key used when a command needs a team
export LINEAR_DEFAULT_TEAM="TEAM"
Discover team keys:
{baseDir}/scripts/linear.sh teams
If LINEAR_DEFAULT_TEAM is set, you can omit the team key in team and call:
{baseDir}/scripts/linear.sh create "Title" ["Description"]
# My stuff
{baseDir}/scripts/linear.sh my-issues # Your assigned issues
{baseDir}/scripts/linear.sh my-todos # Just your Todo items
{baseDir}/scripts/linear.sh urgent # Urgent/High priority across team
# Browse
{baseDir}/scripts/linear.sh teams # List available teams
{baseDir}/scripts/linear.sh team <TEAM_KEY> # All issues for a team
{baseDir}/scripts/linear.sh project <name> # Issues in a project
{baseDir}/scripts/linear.sh issue <TEAM-123> # Get issue details
{baseDir}/scripts/linear.sh branch <TEAM-123> # Get branch name for GitHub
# Actions
{baseDir}/scripts/linear.sh create <TEAM_KEY> "Title" ["Description"]
{baseDir}/scripts/linear.sh comment <TEAM-123> "Comment text"
{baseDir}/scripts/linear.sh status <TEAM-123> <todo|progress|review|done|blocked>
{baseDir}/scripts/linear.sh assign <TEAM-123> <userName>
{baseDir}/scripts/linear.sh priority <TEAM-123> <urgent|high|medium|low|none>
# Overview
{baseDir}/scripts/linear.sh standup # Daily standup summary
{baseDir}/scripts/linear.sh projects # All projects with progress
{baseDir}/scripts/linear.sh standup
Shows: your todos, blocked items across team, recently completed, what's in review.
{baseDir}/scripts/linear.sh create TEAM "Fix auth timeout bug" "Users getting logged out after 5 min"
{baseDir}/scripts/linear.sh urgent # See what needs attention
Always use Linear-derived branch names to enable automatic issue status tracking.
{baseDir}/scripts/linear.sh branch TEAM-212
# Returns: dev/team-212-fix-auth-timeout-bug
# 1. Get the branch name from Linear
BRANCH=$({baseDir}/scripts/linear.sh branch TEAM-212)
# 2. Pull fresh main first (main should ALWAYS match origin)
cd /path/to/repo
git checkout main && git pull origin main
# 3. Create worktree with that branch (branching from fresh origin/main)
git worktree add .worktrees/team-212 -b "$BRANCH" origin/main
cd .worktrees/team-212
# 4. Do your work, commit, push
git push -u origin "$BRANCH"
⚠️ Never modify files on main. All changes happen in worktrees only.
# Full workflow example
ISSUE="TEAM-212"
BRANCH=$({baseDir}/scripts/linear.sh branch $ISSUE)
# Always start from fresh main
cd ~/workspace/your-repo
git checkout main && git pull origin main
# Create worktree (inside .worktrees/)
git worktree add .worktrees/${ISSUE,,} -b "$BRANCH" origin/main
cd .worktrees/${ISSUE,,}
# ... make changes ...
git add -A && git commit -m "fix: implement $ISSUE"
git push -u origin "$BRANCH"
gh pr create --title "$ISSUE: <title>" --body "Closes $ISSUE"
| Level | Value | Use for |
|---|---|---|
| urgent | 1 | Production issues, blockers |
| high | 2 | This week, important |
| medium | 3 | This sprint/cycle |
| low | 4 | Nice to have |
| none | 0 | Backlog, someday |
Team keys and IDs are discovered via the API and cached locally after the first lookup.
Use linear.sh teams to refresh and list available teams.
LINEAR_API_KEY env varTEAM-123Inspired by schpet/linear-cli by Peter Schilling (ISC License). This is an independent bash implementation for Clawdbot integration.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when interacting with Apple Calendar on macOS. Use it for listing calendars, viewing events, creating/updating/deleting calendar events, and checking availability/free-busy times. Triggers on requests like "check my calendar", "schedule a meeting", "what's on my schedule", "am I free tomorrow", or any calendar-related operations.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
日本語の概要は準備中です。原文の説明を表示しています。
ActiveCampaign CRM integration for lead management, deal tracking, and email automation. Use for syncing demo leads, managing clinic sales pipeline, and triggering follow-up sequences.
日本語の概要は準備中です。原文の説明を表示しています。