What problem does it solve? Building a PROCESIO Custom Action connector by hand requires writing C# code against the PROCESIO SDK, packaging it as a .nupkg, and iterating through compile errors. This Skill drives the AI Connector Builder platform (connector-builder.procesio.app), which turns API documentation into a compiled connector through an 8-stage LLM pipeline (gather, clarify, plan, generate, validate, compile, fix, deliver), so you can go from API docs to an installable .nupkg without writing the connector code yourself. ## Core Features & Use Cases - Full build lifecycle control: Create builds from API doc URLs or pasted documentation, answer clarification questions, approve or revise the plan, approve generated files, and download the compiled .nupkg artifact. - Feedback and iteration loops: Revise plans with free-text feedback, regenerate individual files with instructions, auto-fix validation findings, retry failed stages, and jump between pipeline stages with override-stage. - Builder self-improvement: Edit the platform's knowledge base (prompts, spec modules, examples, validation rules) to change how every future build generates code, plus inspect logs, events, and LLM telemetry for cost and token analysis. - Use Case: Point the builder at a REST API's documentation, walk through the clarify and plan stages, download the resulting .nupkg, then upload it to PROCESIO with customaction-upload to test the connector live in a real process. ## Quick Start Ask the AI to create a connector-builder build from your API documentation URL with your requirements, then gather, answer the clarification questions, approve the plan and generated files, and download the compiled .nupkg artifact.
