Skip to content
Back to skills

Usage

ASecurity

Show plugin-cache-sync status and explain sync workflow

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 24, 2026
toolsbash

Works with

  • claude code

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add bengous/claude-code-plugins --skill usage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Usage?

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

Security grade badge for Usage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bengous-usage/badge)](https://www.skillsdirectory.com/skills/bengous-usage)

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: plugin-cache-sync-usage
description: Show plugin-cache-sync status and explain sync workflow
allowed-tools:
  - Bash(${CLAUDE_PLUGIN_ROOT}/scripts/plugin-cache-sync *)
  - Bash(echo *)
---

# plugin-cache-sync

Sync Claude Code plugin cache from local sources.

To test a plugin under edit, prefer `claude --plugin-dir /path/to/plugin`: it reads
the source directly, needs no version bump, and writes nothing to the cache. Use
`sync` only to make an edit live in ordinary sessions launched without flags.

## Current Status

!`"${CLAUDE_PLUGIN_ROOT}/scripts/plugin-cache-sync" version 2>&1 || echo "(plugin-cache-sync not available)"`

!`"${CLAUDE_PLUGIN_ROOT}/scripts/plugin-cache-sync" status 2>&1 || echo "(could not get status)"`

## Workflow

1. **Check status**: `plugin-cache-sync status` — shows which plugins are stale and which are enabled
2. **Sync one plugin**: `plugin-cache-sync sync <name>` — partial name match (e.g. `plugin-cache-sync sync meta`)
3. **Sync all**: `plugin-cache-sync sync --all`
4. **Enable a new plugin**: `claude plugin enable <name>@<marketplace>` — `sync` does not touch `settings.json`, so a brand-new plugin must be enabled once before Claude Code will load it
5. **Restart Claude Code** — `/reload-plugins` reports success and keeps serving the definitions loaded at startup, so a synced change stays invisible until you restart

> `sync` warns when a plugin is synced but not enabled.

## Standalone Mode

For repos not registered as a known marketplace:

- **CWD auto-detection**: if `$PWD/.claude-plugin/marketplace.json` exists, plugin-cache-sync uses it automatically
- **Explicit source**: `plugin-cache-sync --source /path/to/repo sync --all`

## Installation

Run `/plugin-cache-sync:install` to add `plugin-cache-sync` to your PATH.
On Windows, run `/plugin-cache-sync:update` after plugin updates to re-copy the script.

## Key Paths

| Path | Purpose |
|------|---------|
| `~/.claude/plugins/cache/` | Plugin cache (what plugin-cache-sync syncs) |
| `~/.claude/plugins/installed_plugins.json` | Installed plugin registry |
| `~/.claude/plugins/known_marketplaces.json` | Marketplace sources |

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.