plugin-builder

Scaffolds elixirOS plugins with TypeScript templates and runtime wiring.

7|2|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill plugin-builder-prompt-or-die-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-builder
Source: https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/main/.claude/skills/plugin-builder
Command: npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill plugin-builder-prompt-or-die-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the repetitive setup work required to create new elizaOS plugins by generating a complete, consistent plugin package with actions, providers, services, evaluators, tests, and documentation.

Core Features & Use Cases

  • Plugin scaffolding from a single request: Creates a full plugin directory with TypeScript configuration, package metadata, and an entry point that registers the plugin components.
  • Action/provider/evaluator/service generation: Produces structured implementations with validation (e.g., Zod), runtime wiring, and clear extension points.
  • Production-grade project setup: Adds testing scaffolds and documentation so the plugin can be iterated on and published quickly.
  • Use case example: You need a new integration for an external system (e.g., a chat platform or API), including validated actions, context providers for enriched prompts, and evaluators for response quality.
  • Best-fit scenarios: Start from scratch, extend an existing plugin with additional components, or generate reusable plugin packages for repeatable capabilities.

Quick Start

Scaffold a plugin named "weather" with actions, a provider, and a tested service for fetching current conditions and formatting them for the agent.

Frequently Asked Questions about plugin-builder

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

FAQPage Schema
How do I scaffold an elizaOS plugin with TypeScript actions and providers?

Scaffolding an elizaOS plugin generates a complete TypeScript project structure with validated actions, providers, evaluators, and services, including package configuration and runtime wiring. You get a production-ready directory with an entry point that registers all plugin components.

What do I need to create a production-ready elizaOS plugin?

Creating a production-ready elizaOS plugin requires TypeScript configuration, package metadata, component implementations with Zod validation, testing scaffolds, and documentation setup. The scaffolding process generates all of these automatically to satisfy publishing requirements.

Can I extend an existing elizaOS plugin with additional actions and services?

Extending an existing elizaOS plugin with additional actions, providers, evaluators, or services is supported. The scaffolding generates structured implementations with clear extension points and runtime wiring so you can add new agent capabilities to a current plugin package.

Does elizaOS plugin scaffolding include test setup with Vitest?

elizaOS plugin scaffolding includes a complete Vitest test setup as part of the production-grade project configuration. The generated templates provide testing scaffolds for actions, providers, and services so plugins can be iterated on and validated quickly.

What's the best way to structure an elizaOS plugin for agent integrations?

The best way to structure an elizaOS plugin for agent integrations is using a consistent TypeScript project layout with separate directories for actions, providers, evaluators, and services. This approach ensures validated templates with proper runtime wiring and package configuration.