building-tools

Encapsulate Celigo integration logic behind callable input/output contracts for MCP tools.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/celigo/ai --skill building-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-tools
Source: https://github.com/celigo/ai/tree/main/skills/building-tools
Command: npx skills add https://github.com/celigo/ai --skill building-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building the same lookup–transform–import–branching logic repeatedly across flows, APIs, agents, and MCP servers wastes time and creates inconsistent behavior.

Core Features & Use Cases

  • Reusable, contract-driven tools: Encapsulate logic behind a defined input and output schema so multiple consumers can call the same building block.
  • Composable orchestration with routers and branches: Use routers to select branches and chain processing stages, including nested tool composition patterns.
  • First-class processor pipeline: Execute export/import page processors, then apply response mapping and output mappings to return the exact shape callers need.
  • MCP-ready exposure: Make tool definitions callable from MCP servers as external AI agent endpoints.
  • When to use: Build a tool when the same logic is needed by 2+ consumers, when you need connection flexibility, or when you must expose logic via an MCP server.

Quick Start

Ask the AI to help you define a tool with an input JSON Schema, wire required export/import page processors into router branches, and configure response mapping and output mappings so the tool returns a validated result.

Frequently Asked Questions about building-tools

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

FAQPage Schema
How do I expose Celigo integrations as callable tools for an MCP server?

You can expose Celigo integrations as callable tools by encapsulating lookup, import, and transform logic behind input/output contracts and configuring them for MCP server exposure. This allows AI agents to call the tools as external endpoints.

What is the best way to reuse integration logic across flows, APIs, and AI agents?

Reusing integration logic across flows and APIs involves encapsulating lookup, transform, and branching processes behind a defined input and output schema. This contract-driven approach ensures consistent behavior without rebuilding logic for each consumer.

How do I configure routing and branching for reusable integration tools?

Routing and branching are configured using a router with first-matching selection logic to choose branches. Sequential page processors then execute export and import operations, applying response mapping before returning the final output.

Do I need a JSON schema to build a tool with Celigo?

Yes, defining a JSON schema is required to build a tool. Tool input schema validation requires a root type object for MCP compatibility, ensuring the callable input and output contracts are strictly enforced.

When should I build a reusable integration tool instead of duplicating logic in flows?

You should build a reusable tool when the same lookup or import logic is needed by two or more consumers, when connection flexibility is required, or when you must expose integration logic via an MCP server.

How does response mapping work with sequential page processors in integration orchestration?

Sequential page processors execute export and import operations, after which response mapping is applied to process the results. Final output mapping then transforms the data to match the declared output schema required by the caller.