skills.rest
massgen
massgenOFFICIAL
Explore all skills by this author →
GitHub

backend-integrator

Automate MassGen backend integration across architecture, CLI/SDK wiring, capabilities, tests, and documentation.

1.1k|171|Updated Jul 18, 2025
Search Tags:#automation#integration#backend#MCP#LLM#CLI#SDK
One-click install
npx skills add https://github.com/massgen/MassGen --skill backend-integrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-integrator
Source: https://github.com/massgen/MassGen/tree/main/massgen/skills/backend-integrator
Command: npx skills add https://github.com/massgen/MassGen --skill backend-integrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MassGen backend integration is complex, requiring changes across multiple files and configurations. This skill provides a complete checklist and patterns to integrate a new LLM backend, audit existing backends for integration gaps, and ensure consistent behavior across the codebase.

Core Features & Use Cases

  • End-to-end integration checklist across the codebase (backend, CLI, SDK, and tooling).
  • Guidance for API-based backends and CLI/SDK wrappers, including MCP and native tool mixins.
  • Real-world use: adding a new provider (e.g., Codex, Mistral) or auditing an existing backend for missing integration points.

Quick Start

Follow Phase 1–11 steps to implement a backend integration, wire CLI/SDK, configure capabilities, tests, and documentation.

Frequently Asked Questions about backend-integrator

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

FAQPage Schema
How do I integrate a new LLM backend into my codebase?▼

To integrate a new LLM backend, follow an end-to-end checklist covering architecture, backend class implementation, CLI/SDK wiring, capabilities configuration, tests, and documentation across structured phases.

What does an LLM backend integration audit include?▼

An LLM backend integration audit checks for missing integration points across backend classes, CLI mappings, SDK wiring, capabilities, token management, and tests to ensure consistent codebase behavior.

How do I wire CLI and SDK mappings for a new LLM provider?▼

Wiring CLI and SDK mappings for a new LLM provider involves implementing backend classes and mapping them to CLI commands and SDK functions, ensuring capabilities and token management are configured correctly.

Can I add MCP and native tool mixins to an LLM backend integration?▼

Yes, you can add MCP and native tool mixins as optional features during LLM backend integration, extending the backend's capabilities and tooling support alongside the required CLI and SDK wiring.

What is the best way to document LLM backend integration changes?▼

The best way to document LLM backend integration changes is to follow a structured phase process that explicitly covers documentation alongside architecture, file structure changes, capabilities, and tests.

Do I need to configure token management when adding an LLM backend?▼

Yes, configuring token management is a required step when adding an LLM backend to ensure the provider correctly handles capabilities, limits, and integration behavior across the codebase.

Related Skills

Explore More Software Engineering Skills→
devingobledevingoble

dotnet-slopwatch

Detect LLM-introduced slop in .NET code modifications.

Community
Advanced
miles990miles990

goal-verifier

Validate milestone checkpoints against original goals and detect drift.

Community
Basic
ROYCE-8425ROYCE-8425
1

workspace-surface-audit

Audit workspace capabilities and recommend ECC-native skills, hooks, agents, and MCPs.

Community
Advanced
marinkobabicmarinkobabic

aif-security-checklist

Run OWASP Top 10 (2021)-aligned security audits for web applications.

Community
Intermediate