provider-contract

Define standardized interface contracts for Waggle provider plugins.

3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kazukinagata/waggle --skill provider-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-contract
Source: https://github.com/kazukinagata/waggle/tree/main/skills/provider-contract
Command: npx skills add https://github.com/kazukinagata/waggle --skill provider-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a standardized interface contract and naming conventions for Waggle provider plugins, enabling consistent integration and compliance across backends.

Core Features & Use Cases

  • Standardized SKILL.md sections: Config Retrieval, Schema Validation, CRUD Operations, Query Tasks, Identity Resolution, and more to guarantee uniform provider behavior.
  • Interoperability: ensures providers expose consistent data models and APIs (task schema, frontmatter, and operation semantics) to Waggle core.
  • Use Case: A developer builds a new Waggle provider and follows this contract to guarantee compatibility across environments.

Quick Start

Create the provider directory with a SKILL.md and a provider-provider skeleton and start the discovery process to register the plugin.

Frequently Asked Questions about provider-contract

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

FAQPage Schema
What is a Waggle provider contract and when do I need it?

A Waggle provider contract is a standardized interface for provider plugins. You need it when building a new Waggle provider to ensure consistent configuration, schema validation, CRUD operations, and identity resolution across backends.

How do I define a provider interface for Waggle plugins?

To define a provider interface, create a provider directory with a SKILL.md and a provider skeleton. Start the discovery process to register the plugin, ensuring your SKILL.md includes required sections like Config Retrieval and Schema Validation for compliance.

Does every Waggle provider plugin require schema validation?

Yes, schema validation is a required section in the provider contract. Every Waggle provider plugin must expose consistent data models and task schemas to guarantee uniform behavior and interoperability with Waggle core.

What sections are required in a provider SKILL.md for compliance?

Required sections include Config Retrieval, Schema Validation, CRUD Operations, Query Tasks, and Identity Resolution. These sections guarantee uniform provider behavior and ensure your plugin passes the compliance checklist for Waggle core integration.

Why do I need a compliance checklist for Waggle provider plugins?

You need a compliance checklist to verify that your provider plugin follows naming conventions and exposes consistent APIs. It ensures interoperability across environments by validating that required SKILL.md sections and operation semantics are correctly implemented.

Can I use this provider contract for backends outside Waggle core?

No, this provider contract is specifically designed for Waggle provider plugins. It standardizes interfaces to ensure compatibility with Waggle core, applying naming conventions and compliance rules across all registered provider backends.