Ultimate plugin management toolkit with 5 Agent Skills - automates creating, validating, auditing, and managing plugins in the claude-code-plugins marketplace

Installation

npx claude-plugins install @jeremylongshore/claude-code-plugins-plus/skills-powerkit

Contents

Folders: commands, skills

Files: LICENSE, README.md

Documentation

The ultimate plugin management toolkit for the claude-code-plugins marketplace - Includes 5 Agent Skills that automatically manage plugin development, validation, auditing, and marketplace updates.

What Is This?

Skills Powerkit is a “meta-plugin” - a plugin specifically designed to help you CREATE, VALIDATE, AUDIT, and MANAGE plugins within the claude-code-plugins repository.

Think of it as your AI assistant FOR building plugins - it knows the repository structure, standards, and workflows, and automatically handles all the tedious tasks.

5 Included Agent Skills

1. 🛠️ Plugin Creator

Automatically scaffolds new plugins from scratch

Activates when you say:

• “Create a new plugin”
• “Scaffold a plugin for [purpose]”
• “Add new plugin to marketplace”

What it does:

• Creates complete directory structure
• Generates plugin.json with proper schema
• Creates README, LICENSE, component files
• Adds entry to marketplace catalog
• Syncs marketplace.json
• Validates everything

Example: “Create a security plugin called ‘owasp-scanner’ with commands”

2. ✅ Plugin Validator

Automatically validates plugin structure and compliance

Activates when you say:

• “Validate this plugin”
• “Check plugin for errors”
• “Is my plugin ready to commit?”

What it does:

• Validates plugin.json schema
• Checks required files exist
• Validates markdown frontmatter
• Verifies script permissions
• Checks marketplace compliance
• Runs comprehensive validation suite

Example: “Validate the skills-powerkit plugin”

3. 📦 Marketplace Manager

Automatically manages marketplace catalog and syncing

Activates when you say:

• “Add plugin to marketplace”
• “Sync marketplace catalog”
• “Update marketplace version”

What it does:

• Updates marketplace.extended.json
• Runs npm run sync-marketplace
• Validates both catalog files
• Checks for duplicates
• Ensures catalog integrity

Example: “Add the new security-scanner to marketplace”

4. 🔍 Plugin Auditor

Automatically audits plugins for security and quality

Activates when you say:

• “Audit this plugin”
• “Security review”
• “Check best practices”

What it does:

• Scans for security vulnerabilities
• Checks hardcoded secrets
• Validates best practices
• Verifies CLAUDE.md compliance
• Generates quality score
• Provides recommendations

Example: “Audit the security-scanner plugin for production”

5. 🔢 Version Bumper

Automatically handles semantic version updates

Activates when you say:

• “Bump version to patch/minor/major”
• “Release version [x.y.z]”
• “Update plugin version”

What it does:

• Calculates new semantic version
• Updates plugin.json
• Updates marketplace catalog
• Syncs marketplace.json
• Updates CHANGELOG.md (if exists)
• Creates git tags (optional)

Example: “Bump the security-scanner plugin to patch version”

Who Is This For?

For Repository Maintainers

• Create new plugins quickly with proper structure
• Validate plugins before merging PRs
• Audit plugins for quality and security
• Manage marketplace catalog efficiently

For Plugin Contributors

• Ensure your plugin meets all standards
• Validate before submitting PR
• Check compliance with CLAUDE.md
• Get quality recommendations

For This Repository Specifically

This plugin is optimized for claude-code-plugins workflow:

• Knows the two-catalog system (extended vs CLI)
• Understands repository structure
• Follows CLAUDE.md standards
• Handles Skills, Commands, Agents, MCP plugins
• Manages marketplace sync automatically

Installation

# Add marketplace (if not already added)
/plugin marketplace add jeremylongshore/claude-code-plugins

# Install Skills Powerkit
/plugin install skills-powerkit@claude-code-plugins-plus

That’s it! All 5 skills are now active in this repository.

How to Use

Just talk naturally while working on plugins!

Example Workflows

Workflow 1: Create New Plugin

You: "I need to create a new DevOps plugin called 'docker-optimizer' with commands"

Skills Powerkit automatically:
1. Recognizes "create new plugin" → Invokes Plugin Creator
2. Scaffolds plugins/devops/docker-optimizer/
3. Generates plugin.json, README, LICENSE, commands/
4. Adds to marketplace.extended.json
5. Syncs marketplace.json
6. Validates everything
7. Reports: "✅ Plugin created and ready!"

Workflow 2: Validate Before Commit

You: "Is my owasp-scanner plugin ready to commit?"

Skills Powerkit automatically:
1. Recognizes "ready to commit" → Invokes Plugin Validator
2. Checks plugin.json schema
3. Validates frontmatter
4. Verifies marketp

...(truncated)

## Included Skills

This plugin includes 4 skill definitions:

### marketplace-manager

> |

<details>
<summary>View skill definition</summary>

# Marketplace Manager

## Purpose
Automatically manages the claude-code-plugins marketplace catalog system, handling updates to marketplace.extended.json, syncing to marketplace.json, and ensuring catalog integrity.

## Trigger Keywords
- "update marketplace"
- "sync marketplace" or "sync catalog"
- "add to marketplace"
- "marketplace catalog"
- "update catalog"
- "regenerate marketplace"

## Two-Catalog System

**Critical Understanding:**

marketplace.extended.json (SOURCE OF TRUTH) ├── Full metadata ├── Extended fields (featured, mcpTools, etc.) └── Edit THIS file manually

↓ npm run sync-marketplace

marketplace.json (GENERATED) ├── CLI-compatible subset ├── Sanitized fields └── NEVER edit directly

## Marketplace Management Tasks

### 1. Add Plugin to Catalog

When adding new plugin:

```json
// Add to marketplace.extended.json
{
  "name": "plugin-name",
  "source": "./plugins/category/plugin-name",
  "description": "Clear one-line description",
  "version": "1.0.0",
  "category": "productivity",
  "keywords": ["keyword1", "keyword2"],
  "author": {
    "name": "Author Name",
    "email": "[email protected]"
  },
  "repository": "https://github.com/user/repo",
  "featured": false  // true for featured plugins
}

Then:

npm run sync-marketplace

2. Update Plugin Version

When bumping version:

1. Update plugins/category/plugin-name/.claude-plugin/plugin.json
2. Update marketplace.extended.json entry
3. Run npm run sync-marketplace
4. Validate

…(truncated)

plugin-auditor

|

# Check for hardcoded secrets
grep -r "password\s*=\s*['\"]" --exclude-dir=node_modules
grep -r "api_key\s*=\s*['\"]" --exclude-dir=node_modules
grep -r "secret\s*=\s*['\"]" --exclude-dir=node_modules

# Check for AWS keys
grep -r "AKIA[0-9A-Z]{16}" --exclude=README.md

# Check for private keys
grep -r "BEGIN.*PRIVATE KEY" --exclude=README.md

# Check for dangerous patterns
grep -r "rm -rf /" | grep -v "/var/" | grep -v "/tmp/"
grep -r "eval\s*\(" --exclude=README.md

plugin-creator

|

plugin-validator

|

# Required fields:
- name (kebab-case, lowercase, hyphens only)
- version (semantic versioning x.y.z)
- description (clear, concise)
- author.name
- author.email
- license (MIT, Apache-2.0, etc.)
- keywords (array, at least 2)

# Optional but recommended:
- repository (GitHub URL)
- homepage (docs URL)

---
name: command-name
description: Brief description
model: sonnet|opus|haiku
---

---
name: agent-name
description: Agent purpose
model: sonnet|opus|haiku
---

---
name: Skill Name
description: What it does AND when to use it
allowed-tools: Tool1, Tool2, Tool3  # optional
---

plugin-name/
├── .claude-plugin/        

...(truncated)

</details>

## Source

[View on GitHub](https://github.com/jeremylongshore/claude-code-plugins-plus-skills)