extension-builder

Generate a complete Pyrite extension scaffold with plugin classes, entry types, and tests.

3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/markramm/pyrite --skill extension-builder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extension-builder
Source: https://github.com/markramm/pyrite/tree/main/.claude/skills/extension-builder
Command: npx skills add https://github.com/markramm/pyrite --skill extension-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building Pyrite extensions manually is error-prone and time-consuming. The Extension Builder automates scaffolding, ensuring consistent structure, tests, and configuration.

Core Features & Use Cases

  • Generates a complete extension folder under extensions/<name>/ with pyproject.toml, source, tests, and plugin wiring.
  • Creates entry types, validators, presets, and optional components (hooks, tables, workflows, CLI commands) based on user input.
  • Produces a ready-to-run dev-install setup and a test suite to validate load and basic functionality.

Quick Start

Describe your extension needs in plain language and the builder will generate a full Pyrite extension scaffold.

Frequently Asked Questions about extension-builder

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

FAQPage Schema
How do I scaffold a Pyrite extension automatically?▼

To scaffold a Pyrite extension, describe your extension needs in plain language and the builder generates a complete folder structure with plugin class, entry types, validators, presets, tests, and dev-install configuration.

What files and structure are included when generating a Pyrite extension?▼

Generating a Pyrite extension produces a folder with pyproject.toml, source files, tests, plugin wiring, entry types, validators, presets, and optional components like hooks, tables, workflows, and CLI commands.

Can I include hooks, tables, and workflows in my Pyrite plugin scaffold?▼

Yes, you can include hooks, tables, workflows, and CLI commands in your Pyrite plugin scaffold by specifying them in your plain language extension description before generation.

Do I need to manually configure dev-install and tests for a new Pyrite extension?▼

No, you do not need to manually configure dev-install or tests. The scaffold automatically produces a ready-to-run dev-install setup and a test suite validating load and basic functionality.

What is the best way to ensure consistent structure when building multiple Pyrite extensions?▼

The best way to ensure consistent structure across Pyrite extensions is automated scaffolding, which enforces a plug-in architecture with a clear manifest, standard directory layout, and generated tests.

Why does building Pyrite extensions manually lead to errors?▼

Building Pyrite extensions manually leads to errors because it is time-consuming and error-prone, risking inconsistent structure and missing configuration across the plugin manifest, validators, and tests.