integrate-maxio

Orchestrates a maxio-sdk subagent to plan and implement Maxio Advanced Billing .NET SDK integrations.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/apimatic/plugin-marketplace --skill integrate-maxio-apimatic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integrate-maxio
Source: https://github.com/apimatic/plugin-marketplace/tree/main/plugins/maxio-sdk/skills/integrate-maxio
Command: npx skills add https://github.com/apimatic/plugin-marketplace --skill integrate-maxio-apimatic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Integrating the Maxio Advanced Billing (formerly Chargify) .NET SDK from memory leads to hallucinated signatures, wrong enum values, and compile errors on SDK types. This Skill enforces a plan-first workflow where a dedicated maxio-sdk agent produces an authoritative contract sheet before any code is written. ## Core Features & Use Cases - Plan-first orchestration: Spawns a single maxio-sdk agent that writes a maxio-plan.md contract sheet with exact signatures, wire names, error accessors, and enum values. - Hard gating rules: Blocks all project-file edits until the plan file exists and has been read, and mandates loading every dotnet-* companion skill the sheet names. - Error delegation: Routes any compile or runtime error involving MaxioAdvancedBilling SDK types back to the warm agent instead of guessing fixes. - Use Case: When asked to add subscription creation, usage billing, or coupon handling to a C# project, the Skill spawns the agent, gathers the contract sheet, implements against it, and hands SDK-type errors back to the agent for in-place fixes. ## Quick Start Ask the agent to integrate Maxio Advanced Billing subscriptions into your C# project using the Maxio .NET SDK.

Frequently Asked Questions about integrate-maxio

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

FAQPage Schema
How do I integrate the Maxio Advanced Billing SDK in a C# project?▼

Load this Skill first, which spawns a maxio-sdk agent to write a maxio-plan.md contract sheet with exact signatures and enum values. You then implement from that sheet, building after each change and delegating SDK-type errors back to the agent.

How do I fix CS1061 or CS0234 errors on MaxioAdvancedBilling types?▼

Send the exact error output and involved files to the already-running maxio-sdk agent as a follow-up message, not a new spawn. It investigates from its bundled SDK map, fixes the code in place, and reports whether it could build-verify.

Does this Skill work with Maxio SDKs in Python, Java, or other languages?▼

No. The scope guard restricts it to the Maxio Advanced Billing .NET SDK (AsadAli.AdvancedBilling.Sdk, namespace MaxioAdvancedBilling) in C#/.NET projects only. For any other language or API, the Skill does nothing.

Why must I wait for the maxio-sdk agent before writing any code?▼

The agent edits files in place, so your writes would race its writes, and coding before the contract sheet exists means guessing SDK facts from memory. Only read-only prerequisite work like repo surveys and baseline builds is allowed during the wait.

Should I spawn a new maxio-sdk agent for each follow-up question?▼

No. Spawn the agent once per session and send every later need as a follow-up message to that same warm agent. A fresh spawn rebuilds its entire SDK map context, which is the dominant cost.