plugin-forge_skill

This skill helps you create and manage Claude Code plugins with correct structure, manifests, and marketplace integration.
  • Python

273

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill softaworks/agent-toolkit --skill plugin-forge

  • README.md8.6 KB
  • SKILL.md5.1 KB

Overview

This skill creates and manages Claude Code plugins with the correct directory layout, manifests, and marketplace integration. It automates scaffolding, version bumps, manifest updates, and local install/test workflows to streamline plugin development and publishing. Use it to ensure plugins follow marketplace conventions and semantic versioning.

How this skill works

The tool provides scripts and conventions to scaffold plugin directories, generate plugin and marketplace manifests, and update both when versions change. It inspects plugin folders for commands, skills, agents, hooks, and external integration metadata, then updates marketplace.json entries and supports local install/uninstall test flows. Automation scripts (create_plugin.py, bump_version.py) perform routine tasks to avoid manual mistakes.

When to use it

  • Creating a new plugin for a Claude Code marketplace
  • Adding or modifying plugin components (commands, skills, agents, hooks)
  • Bumping plugin versions and keeping manifests in sync
  • Setting up or testing a plugin locally before publish
  • Preparing plugin entries for marketplace distribution

Best practices

  • Follow the prescribed directory layout for plugins and component subfolders to ensure correct namespacing
  • Keep plugin.json and marketplace.json versions in sync; use the bump script to automate semantic versioning
  • Name commands using subdirectory names to derive /namespace:command paths consistently
  • Include clear author, description, keywords, and category metadata in manifests for discoverability
  • Use conventional commit messages to make changelogs and releases predictable

Example use cases

  • Scaffold a new productivity plugin with metadata and initial command files using the create script
  • Add a new command or agent, then bump the plugin minor version and update marketplace entry automatically
  • Run local install/uninstall workflow to validate plugin behavior in a development Claude Code marketplace
  • Convert a utility tool into a marketplace-ready plugin with proper manifests and keywords for search

FAQ

Use the provided bump_version.py script with major|minor|patch and the marketplace root; it updates both plugin and marketplace manifests automatically.

Where should I place commands and how are names derived?

Put command markdown files under commands/<namespace>/ or commands/; command paths map to /namespace:command or /command based on the directory structure.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational