new-provider

Scaffolds a new MQL provider using the Go-based provider-scaffold tool.

407|38|Updated Aug 16, 2022
One-click install
npx skills add https://github.com/mondoohq/mql --skill new-provider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-provider
Source: https://github.com/mondoohq/mql/tree/main/.claude/skills/new-provider
Command: npx skills add https://github.com/mondoohq/mql --skill new-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need to add a new integration target to MQL, but starting a provider from scratch is complex and error-prone.

Core Features & Use Cases

  • Provider scaffolding: Generates the initial provider structure using the repo’s built-in provider-scaffold tool.
  • Initial setup guidance: Helps you collect and confirm the required provider-id and provider-name inputs.
  • End-to-end registration and build path: Instructs you on registering the provider in defaults and docs, then initializing the Go module and building/installing the provider.

Quick Start

Create a provider by running the scaffolding workflow and then build and install it so you can start a shell session for the new provider.

Frequently Asked Questions about new-provider

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

FAQPage Schema
How do I scaffold a new MQL provider integration?

Scaffolding a new MQL provider requires a lowercase hyphen-separated provider-id and a human-readable provider-name. You then run the go-based provider-scaffold tool to generate the initial structure and perform registration steps.

What steps are needed to build and install a generated MQL provider?

Building and installing a generated MQL provider requires running go mod tidy, generating resources code, and building the provider binaries for discovery so you can start a shell session for the new provider.

What inputs do I need to generate a provider structure in Go?

Generating a provider structure in Go requires a lowercase hyphen-separated provider-id and a human-readable provider-name to correctly initialize the Go module and scaffold the integration files.

Why do I need to update defaults and README tables when adding an infrastructure target to MQL?

Updating defaults and README tables when adding an infrastructure target to MQL registers the new provider in repository documentation and configuration, ensuring it is recognized during resource generation and provider discovery.

Can I bootstrap an external service integration in MQL without manually writing Go modules?

Bootstrapping an external service integration in MQL is handled by the provider-scaffold tool, which generates the foundational Go module structure automatically, though you must still run go mod tidy and build the binaries.

When should I not use provider scaffolding to extend MQL?

Provider scaffolding should not be used if your integration requires non-Go languages or bypasses standard resource generation, as the tool specifically scaffolds Go modules and automates Go-based provider binary builds.