Agent skill

sync-status

Use when the user wants to check what config has changed, see sync status, or compare local vs remote config.

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill sync-status --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Version: 0.2.0
Declared author: Rohit Hazra
Allowed tools: Bash(bash${CLAUDE_PLUGIN_ROOT}/scripts/*")Bash(gh*)Bash(git*)Read
Path: plugins/productivity/claudebase/skills/sync-status/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Config Sync Status Compare your local Claude Code configuration against what's stored in the GitHub backup repo. ## Instructions Run the diff script: ```bash bash "${CLAUDE_PLUGIN_ROOT}/scripts/diff-config.sh" --profile PROFILE_NAME ``` If the user doesn't specify a profile, omit the `--profile` flag (uses active profile). ### Interpreting output The script shows each tracked file/directory with a status: - `+ local only` (green) — Exists locally but hasn't been pushed yet - `+ remote only` (cyan) — Exists in the repo but hasn't been pulled yet - `~ modified` (yellow) — Exists in both but differs ### Recommendations Based on the output, suggest the appropriate action: - Local-only files → suggest `/sync-push` - Remote-only files → suggest `/sync-pull` - Modified files → suggest checking what changed, then push or pull ## User Arguments $ARGUMENTS

What's inside
Steps it walks through
  1. Instructions
  2. Interpreting output
  3. Recommendations
  4. User Arguments
Commands it runs
bash "${CLAUDE_PLUGIN_ROOT}/scripts/diff-config.sh" --profile PROFILE_NAME
More from claude-code-plugins-plus-skills
All skills →
orchestrating-multi-agent-systemsExecute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers.…Workflow & Productivityrunning-clustering-algorithmsAnalyze datasets by running clustering algorithms (K-means, DBSCAN, hierarchical) to identify data…Data & Analyticsagency-osNotion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks…Databasesvalidating-ai-ethics-and-fairnessValidate AI/ML models and datasets for bias, fairness, and ethical concerns. Use when auditing AI…AI & Agentsbuilding-automl-pipelinesBuild automated machine learning pipelines with feature engineering, model selection, and…Data & Analyticsprocessing-computer-vision-tasksProcess images using object detection, classification, and segmentation. Use when requesting…AI & Agents
About this skill
What does the sync-status skill do?

Use when the user wants to check what config has changed, see sync status, or compare local vs remote config.

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill sync-status --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.