create-rc-plugin

Generate Python RC plugin scaffolds for DirectumLauncher with manifest and module wiring.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill create-rc-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-rc-plugin
Source: https://github.com/dunaevdmitriys-dev/directum-mcp-server/tree/main/skills/create-rc-plugin
Command: npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill create-rc-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably create the boilerplate and correct file layout for a Python-based DirectumLauncher RC plugin, so you can avoid manual mistakes in manifests, module names, and service registration.

Core Features & Use Cases

  • Creates the correct plugin directory structure for both Type A (microservice) and Type B (applied solution).
  • Generates manifest.json with the required metadata and runtime/dependency fields.
  • Implements the Python entry module (__init__.py) to load plugin modules in DirectumLauncher.
  • Type A supports service wiring including HAProxy frontend/backend settings and healthcheck endpoint construction.
  • Type B supports installer wiring by using a ready BaseRnDComponent-based installer template from the existing scaffold.

Use case: you need to ship a new DirectumLauncher component as a deployable RC plugin and want the AI to produce a consistent scaffold that matches Directum RX 26.1 conventions.

Quick Start

Ask the AI to scaffold a Type A plugin named my_widget with the required display names, version 26.1.0.1, and networking settings (port, health endpoint, and HAProxy path prefix) following the RC plugin structure.

Frequently Asked Questions about create-rc-plugin

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

FAQPage Schema
How do I scaffold a DirectumLauncher RC plugin with Python?

Scaffolding a DirectumLauncher RC plugin involves generating the correct directory layout, manifest.json metadata, and __init__.py loading code for either microservice Type A or applied-solution Type B plugins.

What is the difference between Type A and Type B DirectumLauncher plugins?

Type A DirectumLauncher plugins are microservice-style components requiring networking and HAProxy service registration, whereas Type B plugins are applied solutions that use an installer template for module copying.

How do I configure HAProxy and healthcheck endpoints for a DirectumLauncher microservice plugin?

Configuring HAProxy and healthcheck endpoints for a DirectumLauncher microservice plugin requires setting the frontend/backend paths, port numbers, and health endpoint URLs during the Type A plugin scaffold generation.

Does Directum RX 26.1 require a specific manifest.json structure for RC plugins?

Directum RX 26.1 requires a specific manifest.json structure for RC plugins that validates plugin_path and alias consistency to enforce required runtime metadata and dependency fields.

Why does my DirectumLauncher plugin fail to load modules in Python?

DirectumLauncher plugin modules fail to load in Python when the __init__.py entry module is missing or the manifest.json contains incorrect plugin_path and alias configurations, which automated scaffolding prevents.