module-development

Guide developers in building Amplifier modules with protocol implementation and testing patterns.

1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/drillan/amplifier-skills-plugin --skill module-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-development
Source: https://github.com/drillan/amplifier-skills-plugin/tree/main/skills/module-development
Command: npx skills add https://github.com/drillan/amplifier-skills-plugin --skill module-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers in building Amplifier modules by detailing protocol implementation, entry points, mounting patterns, and testing strategies.

Core Features & Use Cases

  • Module contracts: Understand and implement provider, tool, hook, and orchestrator contracts.
  • Mount patterns: Learn how to expose modules via the Amplifier Mount Plan.
  • Validation & testing: Follow recommended validation and testing patterns to ensure reliability.

Quick Start

Begin by reading the module-development contract to understand the standard module structure, then reference the canonical patterns for mounting, configuration, and testing. Use this Skill as a structured guide during module design and onboarding.

Frequently Asked Questions about module-development

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

FAQPage Schema
How do I build an Amplifier module that complies with provider and tool contracts?

To build an Amplifier module, you must implement the standard provider, tool, hook, and orchestrator contracts, then expose the module via the Mount Plan following canonical structural patterns.

What is the Amplifier Mount Plan and how does module mounting work?

The Amplifier Mount Plan is the canonical pattern for exposing modules, defining how entry points are configured and integrated so that modules are discoverable and properly structured within the system.

What testing patterns should I follow for Amplifier module development?

Amplifier module development requires following recommended validation and testing patterns to ensure module reliability, verifying that entry points and contract implementations function correctly before integration.

Do I need to read contract documentation before starting Amplifier module development?

Yes, reading contract documentation is enforced before starting module development to ensure you understand the standard module structure, mounting configuration, and required compliance with module contracts.

What's the best way to structure entry points and observability in an Amplifier module?

The best way to structure entry points and observability is by referencing canonical patterns from the module-development contract, ensuring compliant integration with the Mount Plan and system observability requirements.