Configure Celigo AI agents and guardrails
Build LLM-powered import steps and safety guardrails in Celigo flows β provider choice (OpenAI/Gemini), prompt design, structured output, BYOK, PII and moderation guardrails
- What
- Build LLM-powered import steps and safety guardrails in Celigo flows β provider choice (OpenAI/Gemini), prompt design, structured output, BYOK, PII and moderation guardrails
- Cost
- Free
- Needs
- a Celigo platform account (paid iPaaS β AI-agent usage counts against the monthly AI token quota); optionally your own OpenAI/Gemini API key for BYOK β the skill is guidance the agent follows, not software
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Paid Celigo account required β Celigo is a paid integration platform (iPaaS), and AI-agent usage counts against the account's monthly AI token quota. Curated by Skill Harbor β @celigo's skill for configuring AI agents and guardrails: an AI agent is an LLM-powered import step inside a Celigo flow (records flow in, the model classifies/extracts/validates/generates, structured output flows back into the pipeline); a guardrail renders a fixed verdict (`flagged: true|false` plus reasoning) that the parent flow routes on β PII detection/masking, content moderation, or custom AI validation. The skill covers provider choice (OpenAI via the Responses API, or Gemini via LiteLLM proxy), prompt design, structured output (`json_schema`/`text`/`blob`), tool use (web search, MCP, Celigo Tools, image generation), response mapping, conversation history via a stable identifier, the Celigo AI vs BYOK decision (platform-managed credentials with a curated model list and token quota vs your own API key), a capability check before building, CLI commands (`celigo ai-agents`, `celigo guardrails`), a pre-submit checklist, gotchas (PUT erases omitted fields, case-sensitive `adaptorType`, Gemini model IDs need the `gemini/` prefix), and a common-errors table. Honest caveats: useless without a Celigo platform account β the CLI, the schemas and the quotas all live there; BYOK moves costs to your own provider billing. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Celigo platform account (paid iPaaS β AI-agent usage counts against the monthly AI token quota); optionally your own OpenAI/Gemini API key for BYOK β the skill is guidance the agent follows, not software Install "Configure Celigo AI agents and guardrails" for me. It gives my agent @celigo's workflow for building LLM-powered import steps and guardrails in Celigo flows: provider choice (OpenAI vs Gemini), prompt design, structured output (json_schema/text/blob), tool use (web search, MCP, Celigo Tools), response mapping, conversation history, Celigo AI vs BYOK, a capability check before building, CLI commands (celigo ai-agents, celigo guardrails), pre-submit checklist, gotchas and a common-errors table. MIT-licensed. Repository: https://github.com/celigo/ai/blob/main/skills/configuring-ai-agents/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "configuring-ai-agents". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. hand the agent a Celigo account with the CLI configured; add my API key to the vault for BYOK). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.