Skip to content
Back to skills

Mcp Linear Sync

ASecurity

Execute a controlled synchronization in Linear using the prevalidated MCP plan.

  • 72 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added June 5, 2026
businessgo

Works with

  • mcp

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add devton/agentic-workflow-blueprint --skill mcp-linear-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mcp Linear Sync?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mcp Linear Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/devton-mcp-linear-sync/badge)](https://www.skillsdirectory.com/skills/devton-mcp-linear-sync)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
## agentic-workflows-blueprint.workflow.mcp-linear-sync

### Goal

Execute a controlled synchronization in Linear using the prevalidated MCP plan.

### Scope

- Applies to: creating/updating Linear milestones and issues via MCP.
- Does not cover: planning from scratch (use `mcp-linear-planner` first).

### Triggers

- "Run Linear sync"
- "Apply MCP plan to Linear"
- "Create/update issues in Linear from workflow"

### Inputs

- `linearMcpPlan` (from `mcp-linear-planner`)
- `teamId` / `projectId` (if required by selected actions)
- `issuePayloads` (titles, descriptions, parent/milestone links)
- `dryRun` (optional boolean)
- `changeWindow` (optional): execution window to respect during write calls
- `riskClass` (optional): risk level for execution controls
- `rollbackTicket` (optional): rollback reference for handoff and incident traceability

### Invariants

- Re-check tool schema before each distinct MCP tool usage.
- Do not run if preflight has unresolved blockers.
- Keep call sequence deterministic and log each action outcome.
- On error, return actionable remediation instead of silent retries.
- If outside `changeWindow`, stop and return `manual_intervention`.

### Procedure

1. Validate `linearMcpPlan` and unresolved blockers.
2. If `dryRun = true`, render planned calls without mutating state.
3. Validate operational controls (`changeWindow`, `riskClass`, `rollbackTicket`) from plan or explicit input.
4. Execute calls in order:
  - context fetch calls (`list_teams`, `list_projects`, `list_milestones`);
  - write calls (`create_milestone`, `create_issue`, `update_issue`).
5. Record each action with status (`success`, `failed`, `skipped`).
6. Produce a final sync report with created/updated entities, failures, and operational metadata.

### Outputs

- `syncReport` with action-by-action status.
- `createdEntities` and `updatedEntities` lists.
- `retryPlan` for failed actions (if any).

### Review gate

- No call executed without matching schema validation.
- Sync report clearly maps inputs to resulting Linear entities.
- Failures include exact next-step remediation.
- Execution respects change window constraints when provided.

### References

- `../../SKILL.md`
- `../mcp-linear-planner/SKILL.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.