Orients Celigo builders to integration concepts and correct workflows.
npx skills add https://github.com/celigo/ai --skill getting-started-celigo
Please help me install this Agent Skill. Skill: getting-started Source: https://github.com/celigo/ai/tree/main/skills/getting-started Command: npx skills add https://github.com/celigo/ai --skill getting-started-celigo
Celigo users often struggle to decide what resource to create first and which skill to use when the task is unclear, leading to misconfigured dependencies and avoidable rework.
Ask an AI: “I’m new to Celigo—what should I build first to create a working integration between an external system and another destination, and how do I choose which skill to use?”
High-intent search queries and answers about installing and using this skill.
To build a Celigo integration, create resources bottom-up so dependencies exist before wiring them together. Establish connections first, then exports and imports, followed by flows and scripts to avoid misconfigured dependencies and rework.
The correct build order is dependency-first: create connections, then exports and imports, and finally assemble flows and integrations. This bottom-up workflow ensures referenced resources are configured before being wired into higher-level flows.
When integration requirements are ambiguous, use the getting-started skill to map your task type to the corresponding skill page. It provides a direct lookup table from common integration goals to specific skills based on decision matrices.
Connections, exports, imports, flows, APIs, and tools relate hierarchically in Celigo. Connections form the base layer, exports and imports handle data movement, and flows orchestrate these components alongside scripts and APIs into complete integrations.
You should separate sandbox and production environments when building Celigo integrations. Maintaining this separation discipline ensures safe account discovery, testing, and requirement design before deploying integration workflows to production.
If a Celigo integration flow is not working, check for missing resource dependencies. Rebuild bottom-up by verifying connections exist first, followed by exports and imports, ensuring all referenced resources are configured before wiring flows.
ydnikolaevExtract project information through structured stakeholder interviews into a discovery brief.
lyticsConfigure end-to-end data integrations with authentication, connections, and jobs.
kevinpbuckleyAutomate Unreal asset discovery and management using Python APIs.
notqueAnalyze a repository's type, language, and architecture into a markdown report.
