Killer-Skills Review
Decision support comes first. Repository text comes second.
This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.
Linear와 프로젝트 상태 관리를 동기화해야 하는 개발 에이전트에게 적합 Sincronizar estado de proyectos de Linear a la base de conocimiento.
이 스킬을 사용하는 이유
에이전트가 Linear 프로젝트와 로컬 지식 베이스 사이에서 데이터를 효율적으로 전송할 수 있는 능력을 부여하여 linear-scan과 linear-team-sync를 사용하여 linear-team-sync 등의 프로토콜을 통해 팀 협업과 문제 추적을 원활하게 함
최적의 용도
Linear와 프로젝트 상태 관리를 동기화해야 하는 개발 에이전트에게 적합
↓ 실행 가능한 사용 사례 for sync-linear
! 보안 및 제한 사항
- Linear 프로젝트 액세스 권한 필요
- 컨텍스트 소모를 피하기 위해 두 단계로 나누어짐
- linear-team-sync를 사용하여 단일 팀만 동기화 가능
Why this page is reference-only
- - Current locale does not satisfy the locale-governance contract.
- - The underlying skill quality score is below the review floor.
Source Boundary
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Decide The Next Action Before You Keep Reading Repository Material
Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.
Start With Installation And Validation
If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Cross-Check Against Trusted Picks
If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Move To Workflow Collections For Team Rollout
When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Browser Sandbox Environment
⚡️ Ready to unleash?
Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.
FAQ & Installation Steps
These questions and steps mirror the structured data on this page for better search understanding.
? Frequently Asked Questions
What is sync-linear?
Linear와 프로젝트 상태 관리를 동기화해야 하는 개발 에이전트에게 적합 Sincronizar estado de proyectos de Linear a la base de conocimiento.
How do I install sync-linear?
Run the command: npx killer-skills add alzado/pm-agent-framework/sync-linear. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.
What are the use cases for sync-linear?
Key use cases include: Linear 프로젝트 상태를 로컬 지식 베이스와 동기화, linear-team-sync를 사용하여 팀의 데이터 전송을 자동화, linear-scan을 사용하여 프로젝트 상태 불일치를 디버깅.
Which IDEs are compatible with sync-linear?
This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.
Are there any limitations for sync-linear?
Linear 프로젝트 액세스 권한 필요. 컨텍스트 소모를 피하기 위해 두 단계로 나누어짐. linear-team-sync를 사용하여 단일 팀만 동기화 가능.
↓ How To Install
-
1. Open your terminal
Open the terminal or command line in your project directory.
-
2. Run the install command
Run: npx killer-skills add alzado/pm-agent-framework/sync-linear. The CLI will automatically detect your IDE or AI agent and configure the skill.
-
3. Start using the skill
The skill is now active. Your AI agent can use sync-linear immediately in the current project.
! Reference-Only Mode
This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
sync-linear
Install sync-linear, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.