rudder-create-plugin

Scaffold Rudder plugin packages with the alpha SDK and validate worker/UI surfaces.

280|30|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Undertone0809/rudder --skill rudder-create-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rudder-create-plugin
Source: https://github.com/Undertone0809/rudder/tree/main/server/resources/bundled-skills/rudder-create-plugin
Command: npx skills add https://github.com/Undertone0809/rudder --skill rudder-create-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the uncertainty and boilerplate of creating a new Rudder plugin by guiding you through the expected worker/UI surfaces, route conventions, scaffold flow, and validation steps.

Core Features & Use Cases

  • Scaffold-ready plugin creation: Generates a plugin package using the current alpha SDK/runtime instead of hand-writing templates.
  • Guided post-scaffold correctness: Helps you verify and adjust key files like src/manifest.ts, src/worker.ts, src/ui/index.tsx, tests, and package.json.
  • Operational verification: Provides a repeatable typecheck, test, and build checklist to ensure the plugin integrates correctly.

Quick Start

Use the skill to scaffold a new plugin package, then run typecheck, tests, and build to confirm it matches the supported runtime assumptions.

Frequently Asked Questions about rudder-create-plugin

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

FAQPage Schema
How do I scaffold a Rudder plugin package using the alpha SDK?

To scaffold a Rudder plugin, use the scaffold tool to generate a package structure with the alpha SDK runtime, then update the manifest, worker, and UI entry points to match supported conventions.

What files need to be updated when creating a new Rudder plugin?

When creating a Rudder plugin, you need to verify and adjust key files including src/manifest.ts, src/worker.ts, src/ui/index.tsx, tests, and package.json to ensure they follow worker and UI surface conventions.

What capabilities and APIs should I avoid when authoring a Rudder plugin?

When authoring a Rudder plugin, you should limit declared capabilities and avoid using ctx.assets to maintain compatibility with the supported runtime assumptions and worker/UI surface conventions.

How do I verify a Rudder plugin integrates correctly after scaffolding?

To verify a Rudder plugin integrates correctly, run a repeatable checklist of typecheck, tests, and build commands to confirm the package matches the supported alpha SDK runtime assumptions.

What's the best way to add an example plugin to an existing Rudder repository?

The best way to add an example Rudder plugin is to use the scaffold tool to generate the package, update the manifest and worker/UI entry points, and perform typecheck, tests, and build verification for discoverable behavior.