From claude-tools
Regenerates Plugins section of README.md from .claude-plugin/marketplace.json and plugin directories, scanning for skills, commands, agents, hooks, MCP, and updating details blocks with installation tables and ZIP badges.
npx claudepluginhub fcakyon/claude-codex-settings --plugin claude-tools# Update README.md Regenerate the Plugins section of README.md based on current plugin structure and marketplace data. ## Steps 1. Read `.claude-plugin/marketplace.json` to get the full list of plugins with descriptions, versions, and metadata. 2. For each plugin, scan `plugins/<name>/` to discover: - Skills: `plugins/<name>/skills/*/SKILL.md` - Commands: `plugins/<name>/commands/*.md` - Agents: `plugins/<name>/agents/*.md` - Hooks: `plugins/<name>/hooks/hooks.json` - MCP: `plugins/<name>/.mcp.json` 3. Update each plugin's `<details>` block in README.md. Use this format:...
/demo-skillsDemonstrates Skills Powerkit's 5 plugin management skills for creating, validating, auditing, syncing marketplace entries, and bumping versions of Claude Code plugins.
/validateValidates Claude Code plugin structure including plugin.json, marketplace.json, skills frontmatter, and commands, producing a structured checklist of pass/fail results.
/release-docsBuilds and updates the static HTML documentation site by inventorying plugin agents, commands, skills, and MCP servers. Supports optional --dry-run preview.
/plugin-reviewReviews Claude Code plugin at <plugin-path> against best practices, tracks progress in state file, validates components, and recommends improvements.
/docs-updateSyncs documentation across README files and wiki articles by locating wiki repo, analyzing main repo changes, interactively confirming updates, and committing to both.
/create-pluginConverts an existing project into a structured Claude Code plugin by generating manifests, organizing components into directories, and creating documentation.
Share bugs, ideas, or general feedback.
Regenerate the Plugins section of README.md based on current plugin structure and marketplace data.
Read .claude-plugin/marketplace.json to get the full list of plugins with descriptions, versions, and metadata.
For each plugin, scan plugins/<name>/ to discover:
plugins/<name>/skills/*/SKILL.mdplugins/<name>/commands/*.mdplugins/<name>/agents/*.mdplugins/<name>/hooks/hooks.jsonplugins/<name>/.mcp.jsonUpdate each plugin's <details> block in README.md. Use this format:
<details>
<summary><strong>plugin-name</strong> - Short description</summary>
| Claude Code | Codex CLI | Gemini CLI |
| --------------------------------------------- | -------------------------------------------------- | -------------------------------------------------------- |
| `/plugin install plugin-name@claude-settings` | `codex plugin install plugin-name@claude-settings` | `gemini extensions install --path ./plugins/plugin-name` |
One-line description.
**Skills:**
- [`skill-name`](./plugins/plugin-name/skills/skill-name/SKILL.md) - Description from SKILL.md frontmatter
**Commands:** (if any)
- [`/plugin-name:cmd`](./plugins/plugin-name/commands/cmd.md) - Description from frontmatter
**Agents:** / **Hooks:** / **MCP:** (if applicable)
</details>
**Skills** (ZIP for claude.ai, Claude Code, Cursor, Codex, VS Code):
| Skill | Description | ZIP |
| ---------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [`skill-name`](./plugins/plugin-name/skills/skill-name/SKILL.md) | Description | [](https://github.com/fcakyon/claude-codex-settings/releases/latest/download/skill-name.zip) |
Also update the Installation section if plugin names have changed.
Do NOT modify non-plugin sections (header, Configuration, Statusline, TODO, References, Star History).