plugin-factory
Install
Pick the surface you use. Plugins run inside Claude Code, which is available in the terminal CLI, the desktop app on Mac and Windows, the web app at claude.ai/code, and the VS Code and JetBrains extensions. The slash commands are identical on every surface.
From inside any Claude Code session — terminal, desktop app, web app, or IDE extension:
-
Add the RBA Skills marketplace (only needed once per machine):
/plugin marketplace add rbaconsulting/rba-skills-plugin -
Install plugin-factory:
/plugin install plugin-factory@rba-ai-hub -
Activate it without restarting:
/reload-plugins
Prefer to browse and click? Run /plugin inside Claude Code to open the interactive plugin manager. It looks the same in the desktop app, web app, terminal, and IDE extensions.
-
Open the plugin manager:
/plugin - Press Tab to reach Marketplaces, choose Add, then enter
rbaconsulting/rba-skills-plugin. - Press Tab again to Discover. Search for
plugin-factory, press Enter, and pick a scope (User, Project, or Local). - Run
/reload-pluginsto activate it.
If you have the Claude Code CLI installed and want to drive it from a normal shell prompt:
$ claude plugin marketplace add rbaconsulting/rba-skills-plugin
$ claude plugin install plugin-factory@rba-ai-hub The next Claude Code session loads it automatically.
Overview
Plugin & Skill Factory
Internal scaffolding factory for contributors to the RBA Skills catalog. This plugin turns a plain-language description — "I want a skill that generates Optimizely content-type models" — into a fully spec-compliant plugin bundle or standalone artifact, passing CI validation on the first try.
Every output artifact enforces:
name= folder = kebab-case (slug identity rule)- Least-privilege
allowed-tools(no bareBash, no wildcardWebFetch) - Hook security classification before any
hooks.jsonis written SKILL.md≤ 500 lines (depth pushed intoreference.md/templates.md/examples.md)- All four required plugin bundle files (
plugin.json,rba-meta.json,README.md, one artifact) - Correct placement: plugin bundle vs. standalone vs. dev-tooling
What's in this bundle
| Artifact | Purpose |
|---|---|
scaffold-plugin skill |
Scaffolds a complete new plugin bundle from a description — all four required files + first skill |
scaffold-skill skill |
Adds a single skill (SKILL.md + optional sibling files) to an existing plugin or standalone path |
scaffold-agent skill |
Generates a subagent definition for an existing plugin, with correct tools least-privilege list |
scaffold-hook skill |
Generates hooks/hooks.json for an existing plugin; runs hook security classification and explains each event |
audit-plugin skill |
Reads an existing plugin bundle and produces a gap report against CLAUDE.md rules — naming, facets, privilege, line counts |
plugin-factory-agent agent |
Autonomous end-to-end factory: takes a plain-language request, picks the right skill(s), scaffolds the artifact(s), validates, and reports |
/new-plugin-factory command |
Quick entry-point slash command — routes to the right factory skill based on what you pass |
When to use
- Starting a new plugin from scratch: run
scaffold-plugin— describes what the plugin does, gets back the full bundle ready fornpm run validate - Adding a skill to an existing plugin: run
scaffold-skillwith the plugin slug and skill description - Adding a subagent: run
scaffold-agent— it builds the agent.mdwith a correcttoolslist reviewed against least-privilege rules - Adding hooks: run
scaffold-hook— classifies each hook event, flags security implications, writeshooks.json - Auditing a draft PR: run
audit-pluginbefore opening a PR to catch naming, facet, and privilege violations before CI does - Hands-off scaffolding: invoke
plugin-factory-agent— it orchestrates the full pipeline and delivers validated output
Platform adapters
All scaffolding is platform-agnostic by default. The factory includes adapter guidance for platform-specific tags and skill patterns:
- Sitecore — Helix layer naming, XM Cloud rendering-host patterns, SXA conventions
- Optimizely — CMS 12+ content-type model, A/B test implementation hygiene
- Umbraco — composition patterns, Document Type naming, Examine index considerations
- Azure — Bicep / APIM / Key Vault patterns for hook commands and MCP server entries
- Azure DevOps — pipeline trigger patterns for hook
PostToolUsecommands
How to install
claude plugin install plugin-factory@rba-ai-hub
Then invoke any skill directly, use the /new-plugin-factory slash command as a single entry point, or let the autonomous plugin-factory-agent handle the full pipeline.
Bundled artifacts
Skills
- audit-plugin — Reads an existing RBA Skills plugin bundle (or standalone skill) and produces a gap report listing every violation of the CLAUDE.md rules: slug/name identity mismatches, missing required files, invalid facet values, bare-Bash or wildcard-WebFetch privilege violations, SKILL.md line-count overruns, and custom RBA fields leaking into plugin.json. Use before opening a PR to catch issues before CI does.
- scaffold-agent — Generates a subagent definition (.md file) for an existing RBA Skills plugin bundle, building a correct `tools` list under least-privilege rules, writing an orchestration step sequence, and confirming the agent slug matches its filename. Use when you need an autonomous reviewer or orchestrator agent to accompany a plugin's skills.
- scaffold-hook — Generates hooks/hooks.json for an existing RBA Skills plugin, classifying each hook event by security risk level, explaining what each hook will run and when, and refusing to write hooks that access credentials or execute with elevated privilege. Use when you need to automate post-write formatting, pre-commit validation, or stop-event notifications within a plugin's lifecycle.
- scaffold-plugin — Scaffolds a complete, CI-passing RBA Skills plugin bundle from a plain-language description. Generates all four required files (plugin.json, rba-meta.json, README.md, first SKILL.md) plus optional agents, commands, and hooks. Enforces slug=name identity, least-privilege allowed-tools, facet assignment, and the 500-line SKILL.md limit. Use when starting a new plugin from scratch.
- scaffold-skill — Adds a single, CI-passing skill (SKILL.md plus optional reference.md, templates.md, examples.md) to an existing RBA Skills plugin bundle or standalone path. Derives the correct slug, enforces least-privilege allowed-tools, caps SKILL.md at 500 lines, and routes depth to sibling files. Use when you want to extend an existing plugin with a new skill or create a standalone skill without the full plugin scaffold.
Agents
- plugin-factory-agent — Autonomous end-to-end plugin factory: takes a plain-language description of a new plugin or skill, picks the correct factory skill(s), scaffolds all required artifacts, runs audit-plugin to verify compliance, and delivers a validated scaffold ready for `npm run validate`. Use when you want a single invocation to go from idea to complete, CI-ready plugin bundle.
Slash Commands
- /new-plugin-factory — Quick entry-point for all RBA Skills plugin and skill factory operations. Dispatches to the right factory skill based on what you pass: a plugin description for a full bundle, an existing plugin slug to extend it, or a mode flag to run a specific factory operation. Wraps scaffold-plugin, scaffold-skill, scaffold-agent, scaffold-hook, and audit-plugin.
Hooks
- PostToolUse — PostToolUse hook
Technical details
- Homepage
- https://rba-skills.tylerschroeder.net/plugins/plugin-factory/
- License
- MIT
- Maturity
- experimental
- Security review
- No security review
- Owners
-
- engineering
- Disciplines
- engineering
- Lifecycle
- build
- Tags
- Last updated
- by Tyler Schroeder
- Source
plugins/plugin-factory/
Edit this plugin's README on GitHub — opens GitHub's web editor. No git knowledge needed.