Help us improve
Share bugs, ideas, or general feedback.
From core-plugin
Suggests uninstalled marketplace plugins on friction. Triggered passively. Use when agent retries, user corrects approach, or no good tool exists. Out of scope: plugin installation, plugin development, MCP server setup.
npx claudepluginhub bernatmv/ai-rules --plugin core-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/core-plugin:plugin-advisorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**plugin-advisor skill loaded.**
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
plugin-advisor skill loaded.
By Joshua Martell (jmartell). Originally from claude-kit.
A compact plugin index lives at ~/.claude_files/plugin-index.md. Each line is
one plugin with its source and a short description. The index is built by a
Sonnet subagent reading marketplace.json — no Python script needed.
On load, check freshness and rebuild if the index is missing or stale (see Freshness Check). This ensures the index is warm before friction occurs.
Use ls -l (not stat — stat triggers quoted-chars permission prompts):
ls -l ~/.claude/plugins/marketplaces/*/.claude-plugin/marketplace.json
Then read the index (~/.claude_files/plugin-index.md) and compare each marketplace
section's <!-- source: metadata against the ls -l output. Rebuild if:
ls -l but has no section in the index (new marketplace)Consider suggesting a plugin when you observe two or more of these signals:
Do not suggest on first attempt. Only after genuine friction.
~/.claude_files/plugin-index.md~/.claude/plugins/marketplaces/*/plugins/<name>/ (Anthropic first-party)
~/.claude/plugins/marketplaces/*/external_plugins/<name>/ (vendor/external)Brief, one line, with install command:
Plugin available:
playground— self-contained HTML explorers with live preview. Install:claude plugin install playground
Then continue working on the task. The suggestion is informational — don't stop.
~/.claude/plugins/installed_plugins.jsonjira skill which covers this" rather than suggestingWhen the index is stale or missing, launch a Sonnet subagent with this prompt.
Pass the ls -l output as context so the subagent can embed the metadata.
Build a compact plugin index. Use ONLY Read and Write tools. No Bash.
For EACH marketplace directory under ~/.claude/plugins/marketplaces/:
Read: ~/.claude/plugins/marketplaces/<name>/.claude-plugin/marketplace.json
Skip rules:
- Skip plugins with "-lsp" in the name
- Skip "example-plugin"
For each kept plugin, write one line:
name (source): description (under 70 chars, specific to when it helps)
Source labels:
- "Anthropic" if source starts with "./plugins/"
- "vendor" if source starts with "./external_plugins/"
- Author/org name if source is a URL
Drop any plugin whose description is too vague to match a specific problem.
Output format — one section per marketplace, with source metadata from the
ls -l output I'm providing:
# Available Plugins
# On friction, suggest matching plugin: claude plugin install <name>
## claude-plugins-official
<!-- source: 548512 Mar 13 14:23 marketplace.json -->
plugin-name (Anthropic): description
another-plugin (vendor): description
## devex-claude-plugins
<!-- source: 12345 Mar 12 09:15 marketplace.json -->
some-plugin (vendor): description
The <!-- source: SIZE DATE TIME marketplace.json --> line stores the size and
mtime from ls -l. Use the actual values from the ls -l output below:
{paste ls -l output here}