public-api-tooling

Update ChatbotX API clients, OpenAPI types, CLI commands, and MCP tools.

601|129|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/ChatbotXIO/ChatbotX --skill public-api-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-api-tooling
Source: https://github.com/ChatbotXIO/ChatbotX/tree/main/.agents/skills/public-api-tooling
Command: npx skills add https://github.com/ChatbotXIO/ChatbotX --skill public-api-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps ChatbotX's public API surface consistent across generated types, typed clients, CLI commands, and MCP server tools so changes do not drift across multiple entrypoints.

Core Features & Use Cases

  • OpenAPI-Driven Clients: Works with generated OpenAPI types and domain client modules under packages/public-apis.
  • CLI and MCP Integration: Supports dynamic API discovery and execution in apps/cli and apps/mcp-server.
  • Auth and Validation Patterns: Handles workspace token auth, schema validation, and request helpers for public API access.
  • Use Case: When a new API endpoint is added or its response shape changes, this Skill guides the update flow from builder procedure to generated types, client wrappers, and runtime tooling.

Quick Start

Use the public-api-tooling skill to update the ChatbotX API client, OpenAPI types, CLI command behavior, and MCP tool registration for the specified endpoint change.

Frequently Asked Questions about public-api-tooling

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

FAQPage Schema
How do I keep OpenAPI types and CLI commands in sync when an API endpoint changes?

To sync OpenAPI types and CLI commands, this Skill guides the update flow from builder procedure to generated types, typed client functions, and runtime tooling for the specified endpoint change.

What is the best way to update MCP server tools after a public API response shape changes?

To update MCP server tools after a response shape changes, this Skill applies synchronized OpenAPI metadata, typed client functions, and Zod validation to reflect the new response shape.

How does dynamic API discovery work with generated OpenAPI types?

Dynamic API discovery works by integrating generated OpenAPI types and domain client modules with CLI and MCP server entrypoints to maintain consistent endpoint access and runtime execution.

Do I need Zod validation to add a new endpoint to the public API client?

Yes, you need Zod validation along with synchronized OpenAPI metadata and typed client functions to ensure schema validation and request helpers work correctly for the new endpoint.

Can I use workspace token auth with CLI and MCP server integration?

Yes, you can use workspace token auth with CLI and MCP server integration, as this Skill handles workspace token auth, schema validation, and request helpers for public API access.

Why do my generated OpenAPI types drift from the CLI command behavior?

Generated OpenAPI types drift from CLI command behavior when changes are not synchronized across multiple entrypoints, which this Skill prevents by maintaining consistency across types, clients, and runtime tools.