nexus

Generate unified HTTP, CLI, and MCP interfaces from a single workflow registration.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill nexus-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/03-nexus
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill nexus-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Nexus eliminates the repeated work of exposing the same workflow through separate API, CLI, and agent/tool interfaces by generating a unified multi-channel platform from a single registration.

Core Features & Use Cases

  • Zero-config multi-channel deployment: register once and serve the same workflow via HTTP API, CLI commands, and MCP tools.
  • Unified sessions across channels: keep state consistent whether the workflow is started via API, continued via CLI, or invoked via MCP.
  • Production-grade enterprise capabilities: add authentication, RBAC, tenant isolation, rate limiting, audit logging, and health monitoring.
  • Workflow-first developer experience: treat workflows as the unit of deployment instead of hand-writing routes/endpoints.
  • Kubernetes & security middleware: supports Kubernetes probe patterns, OpenAPI generation, security headers, and CSRF protection.

Quick Start

Create a Nexus app, register your workflow with the required build step, then start the platform so it becomes available on HTTP, CLI, and MCP.

Frequently Asked Questions about nexus

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

FAQPage Schema
How do I deploy a single workflow to HTTP API, CLI, and MCP simultaneously?

Multi-channel workflow deployment is achieved by registering a single workflow through a unified framework, which automatically generates and serves the same workflow via HTTP API, CLI commands, and MCP tools from one configuration.

Can I add enterprise authentication and Kubernetes probes to my workflow deployment?

Yes, enterprise auth, RBAC, tenant isolation, rate limiting, and Kubernetes probe patterns are supported as production-grade middleware capabilities integrated directly into the workflow deployment platform.

Does multi-channel workflow deployment automatically generate OpenAPI documentation?

Yes, OpenAPI generation is supported natively as part of the production-grade capabilities, automatically creating API documentation when workflows are deployed through the unified multi-channel platform.

Do I need a root SKILL.md file to register workflows for multi-channel deployment?

Yes, a root SKILL.md entry is required for workflow discovery, and you must complete the correct registration lifecycle by building the workflow before registering it for multi-channel exposure.