skills.rest
cyberpunk042
cyberpunk042COMMUNITY
Explore all skills by this author →
GitHub

infra-api

Govern API versioning, deprecation planning, and OpenAPI schema generation across LocalAI, MCP, CLI, and agent endpoints.

Updated Mar 26, 2026
Search Tags:#mcp#api-design#gateway#localai#api-lifecycle#infra-api
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill infra-api
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: infra-api
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/infra-api
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill infra-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and govern AICP's API surfaces across LocalAI REST, MCP tools, the AICP CLI, and the agent REST API, including contract design, versioning, deprecation planning, and OpenAPI schema considerations.

Core Features & Use Cases

  • Centralize API surface design for four surfaces (LocalAI proxy API, MCP tool surface, AICP CLI, and agent REST API).
  • Provide lifecycle controls for versioning, deprecation planning, and schema generation.
  • Enable operator-driven decisions for fleet RPC planning and tool governance.

Quick Start

Provide governance for a new API endpoint design or a version/deprecation decision in your next planning session.

Frequently Asked Questions about infra-api

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

FAQPage Schema
How do I manage API lifecycle and versioning across multiple agent endpoints?▼

To design OpenAPI schemas for fleet coordination, you centralize contract generation across LocalAI REST, MCP tools, and the CLI, enabling consistent tool governance and operator-driven RPC planning across the agent REST API.

How do I design OpenAPI schemas for fleet coordination across LocalAI and MCP tools?▼

To design OpenAPI schemas for fleet coordination, you centralize contract generation across LocalAI REST, MCP tools, and the CLI, enabling consistent tool governance and operator-driven RPC planning across the agent REST API.

Can I use a single governance workflow for both MCP tool surfaces and CLI endpoints?▼

Yes, you can govern both MCP tool surfaces and CLI endpoints within a single workflow that centralizes API contract design, versioning, and deprecation planning across four distinct surfaces including LocalAI and agent REST.

What is the best way to plan API deprecation across multi-surface agent endpoints?▼

The best way to plan API deprecation across multi-surface agent endpoints is to apply centralized lifecycle controls that dictate versioning and deprecation schedules across LocalAI, MCP, CLI, and REST APIs simultaneously.

Do I need explicit frontmatter metadata to operate API lifecycle governance for LocalAI?▼

Yes, explicit frontmatter metadata, script references, and lifecycle guidance are required to load and operate the API lifecycle governance workflow effectively within operator planning conversations.

Related Skills

Explore More Software Engineering Skills→
OpenAnalystIncOpenAnalystInc
3

10x-setup

Automate Notion workspace initialization with RACI, roles, departments, teams, and users.

Official
Advanced
imehrimehr

api-validation

Enforce API contracts with Zod and OpenAPI schemas for REST and RPC endpoints.

Community
Intermediate
cyberpunk042cyberpunk042

infra-search

Configure and optimize multi-surface search pipelines for AICP across KB, code, and wiki sources.

Community
Advanced
Adelie-SquadAdelie-Squad
17

api-developer

Design API contracts and generate OpenAPI 3.0 documentation.

Official
Advanced