skills.rest
luiseiman
luiseimanCOMMUNITY
Explore all skills by this author →
GitHub

plugin-generator

Generate a Claude Code plugin package from dotforge configuration.

8|1|Updated Mar 19, 2026
Search Tags:#automation#plugin#marketplace#claude-code#generator#dotforge
One-click install
npx skills add https://github.com/luiseiman/dotforge --skill plugin-generator-luiseiman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-generator
Source: https://github.com/luiseiman/dotforge/tree/main/skills/plugin-generator
Command: npx skills add https://github.com/luiseiman/dotforge --skill plugin-generator-luiseiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the packaging of a project's dotforge configuration into a ready-to-submit Claude Code plugin.

Core Features & Use Cases

  • Validate source: ensures CLAUDE.md exists and .claude/settings.json is present.
  • Detect components: converts .claude/rules into skills, and copies agents/commands/hooks as needed; creates a marketplace-ready structure.
  • Use Case: teams can reproduce plugin bundles across multiple projects for consistent deployment.

Quick Start

Run the generator from the project root to produce a ready-to-test plugin bundle.

Frequently Asked Questions about plugin-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code plugin from existing dotforge configuration?▼

To create a Claude Code plugin from dotforge configuration, run the generator from your project root to validate CLAUDE.md and .claude/settings.json, then convert .claude/rules into a structured plugin package with a plugin.json file.

What files are required to generate a Claude Code plugin package?▼

Generating a Claude Code plugin package requires a valid CLAUDE.md file and a .claude/settings.json file in your project root to pass source validation and enable the conversion of .claude/rules into plugin components.

How does the plugin generator convert dotforge rules into marketplace-ready components?▼

The plugin generator converts dotforge rules by transforming .claude/rules into skills, agents, hooks, and commands, then packaging them with optional assets into a marketplace-ready structure while respecting repository ignore rules.

Can I test a generated Claude Code plugin locally before submitting it to a marketplace?▼

Yes, you can test a generated Claude Code plugin locally by using the claude --plugin-dir command after the generator creates the structured output bundle from your dotforge configuration.

Does the plugin generator support replicating plugin structures across multiple projects?▼

Yes, the plugin generator supports replicating plugin structures across multiple projects by automating the packaging of dotforge configurations, enabling teams to reproduce consistent plugin bundles for deployment.

What happens if my project is missing the .claude/settings.json file during plugin generation?▼

If .claude/settings.json is missing during plugin generation, the source validation fails and prevents the creation of a Claude Code plugin package, as this file is a mandatory requirement for the conversion process.

Related Skills

Explore More Software Engineering Skills→
luiseimanluiseiman
8

export-config

Export dotforge configuration to Cursor, Codex, Windsurf, and OpenClaw artifacts.

Community
Intermediate
emdashcodesemdashcodes
13

claude-code-plugins

Plan, package, and distribute Claude Code plugins and marketplaces.

Community
Intermediate
damionrashforddamionrashford
15

plugin-settings

Manage per-project plugin settings via YAML frontmatter in .claude/plugin-settings.local.md.

Community
Intermediate
thoeltigthoeltig

managing-plugins

Automate Claude Code plugin creation, bundling, and manifest generation.

Community
Intermediate