marketplace/bundles/pm-plugin-development/skills/plugin-create/SKILL.md
Create new marketplace components (agents, commands, skills, bundles) with proper structure and standards compliance
npx skillsauth add cuioss/plan-marshall plugin-createInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Interactive wizard for creating well-structured marketplace components following architecture best practices.
Execution mode: Interactive wizard — gather user input via AskUserQuestion, validate, generate, verify.
Prohibited actions:
Task in tools, reject and suggest creating a command instead.Constraints:
tools: Read, Write, Edit (not array syntax)python3 .plan/execute-script.py commandComponent Creation: Unified workflows for creating agents, commands, skills, and bundles with proper structure, frontmatter, and standards compliance.
Validation: Automated validation of component structure, frontmatter format, and architecture compliance.
Templates: Consistent templates for all component types with proper sections and formatting.
Duplication Detection: Prevents creating duplicate components by checking existing components in target bundle.
Pattern 5 + Pattern 6: Wizard-Style Workflow + Template-Based Generation
Activate when creating:
This skill provides 4 workflows, one for each component type. All workflows follow the same pattern:
Load the relevant workflow on-demand based on the component type being created.
Read standards/workflow-create-agent.md
Creates a new agent with proper frontmatter, tool selection, Rule 6/7 enforcement, and CONTINUOUS IMPROVEMENT RULE.
Read standards/workflow-create-command.md
Creates a new command with thin orchestrator pattern, parameter design, and CONTINUOUS IMPROVEMENT RULE.
Read standards/workflow-create-skill.md
Creates a new skill with directory structure, SKILL.md, README, and placeholder standards files.
Read standards/workflow-create-bundle.md
Creates a new bundle with plugin.json, directory structure, and optional initial components (delegates to workflows 1-3).
This skill uses the following reference files (load on-demand):
Script: pm-plugin-development:plugin-create → component.py
| Subcommand | Purpose |
|------------|---------|
| validate | Validates marketplace component structure |
| generate | Generates YAML frontmatter for components |
Purpose: Validates marketplace component structure
Usage:
python3 .plan/execute-script.py pm-plugin-development:plugin-create:component validate --file <file_path> --type <component_type>
Output: JSON with validation results
Purpose: Generates YAML frontmatter for components
Usage:
python3 .plan/execute-script.py pm-plugin-development:plugin-create:component generate --type <component_type> --config '<answers_json>'
Output: Formatted YAML frontmatter string
This skill uses the following templates in assets/templates/:
See Enforcement block above for all rules applied during component creation.
The canonical argparse surface for component.py (the skill's argparse CLI entry-point; cmd_generate.py and cmd_validate.py are internal command-handler modules imported by component.py, not standalone argparse CLIs). The plugin-doctor analyzer (_analyze_manage_invocation.py) reads this section as source-of-truth for the manage-invocation-invalid and missing-canonical-block rules. Consuming docs xref this section by name instead of restating the command inline. See pm-plugin-development:plugin-script-architecture cross-skill-integration.md § "Script invocation in documentation".
python3 .plan/execute-script.py pm-plugin-development:plugin-create:component generate \
--type {agent,command,skill} --config CONFIG
python3 .plan/execute-script.py pm-plugin-development:plugin-create:component validate \
--file FILE --type {agent,command,skill}
development
Domain-owned OpenRewrite log-line finding parser for the java-cui domain — parses the
development
Domain-owned OpenRewrite marker detection for the java-cui domain — scans Java/Kotlin sources for cui-rewrite TODO markers, categorizes them by recipe, and fails the gate on any detected marker
development
Operator control surface for the marshalld build server — enrol/drop a project in the machine-global registry (the opt-in enable signal and anti-laundering wall), manage the daemon lifecycle (start, stop, drain, status, install, upgrade) version-pinned to the verified bundle copy, and inspect the daemon's per-project interaction-audit log (read-only)
tools
The tiny build-consumption client for the marshalld build server — submit a build job, bounded long-poll for its result, ping the daemon identity, and preflight registry-plus-liveness in one call; consumption only, never provisioning or enrolment