Use when the user wants to check what config has changed, see sync status, or compare local vs remote config.
Scanned 5/29/2026
Install to Claude Code
Skills Directorynpx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill sync-status --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sync Status?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-sync-status)More formats (shields.io, HTML) on the badges page.
---
name: sync-status
description: Use when the user wants to check what config has changed, see sync status, or compare local vs remote config.
user-invocable: true
allowed-tools: Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/*"), Bash(gh *), Bash(git *), Read
version: 0.2.0
author: Rohit Hazra
license: MIT
---
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
