Skip to content
Back to skills

Planr Sync

ASecurity

Audit OpenPlanr planning artifacts for graph and protocol drift. Use when statuses, references, schemas, or generated planning views may be inconsistent.

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 23, 2026
developmentgit

Works with

  • cli

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned October 7, 2026

npx -y skills add openplanr/OpenPlanr --skill planr-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Planr Sync?

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

Security grade badge for Planr Sync
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/openplanr-planr-sync/badge)](https://www.skillsdirectory.com/skills/openplanr-planr-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
---
name: planr-sync
description: Audit OpenPlanr planning artifacts for graph and protocol drift. Use when statuses, references, schemas, or generated planning views may be inconsistent.
license: MIT
---

# OpenPlanr Sync

Reconcile local planning artifacts and, when requested, GitHub or Linear state.
Reason about conflicts in this active session. Local and GitHub work never require
the OpenPlanr CLI.

Remote steps run through the host's own connections, as described in
[tracker connections](references/tracker-connections.md), which also holds the status
mapping and what to tell the user when a connection is missing:

- GitHub: the host's GitHub connection, or, when the GitHub CLI is signed in, the
  packaged [sync helper](scripts/sync.mjs), which creates and edits issues through `gh`;
  close or reopen an issue with `gh issue close` or `gh issue reopen`. `openplanr github`
  is an optional equivalent; `openplanr sync` only repairs local cross-references.
- Linear: the host's Linear connection.

Audit is read-only by default. Apply local changes only when the request asks for
reconciliation, and push remote changes only when the request asks for external
synchronization. If a connection is unavailable, complete local reconciliation
and report only the external step that could not run.

## Return

Lead with what is aligned, repaired or still blocked. Summarize aligned, locally
repairable, conflict and unavailable counts; link changed paths or remote items
by purpose. State what was actually validated or synchronized and distinguish
local success from an unavailable remote step. Give each material conflict its
impact and recovery action, with one most useful next step. Keep full mapping
and diagnostics in their existing records. Different chat wording never causes
a second synchronization or a corrective run.

When the OpenPlanr dashboard is running, the reconciled graph is browsable at
`#/overview` and recent changes at `#/activity`. This is navigation only.

Files in this skill

  • SKILL.md1.3 KB
  • agents/openai.yaml365 B
  • compatibility.json358 B
  • host-profiles.json5.4 KB
  • modules.json920 B
  • openplanr.skill.json674 B
  • scripts/sync.mjs9 KB

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.