Celigo agent skills for Claude Code, Cursor and RevampKey

5 ready-made playbooks that teach an AI agent how to do real Celigo work: which tools to call, what to check first, and when to stop and ask you.

Download RevampKey, free I have it: connect Celigo

Connect Celigo once and all 5 skills install themselves and stay up to date. Mac, Windows and Linux.

All 5 Celigo skills

Each skill is one job. You ask in plain words and the agent loads the skill that matches, then follows its steps.

Start hereAsks before writing24 Celigo tools

Use Celigo Platform MCP safely with AI

Connects an AI agent to your Celigo integrator.io account and works out which environment you are in before reading anything. Read-only by default: it asks for your explicit yes before any change, retry or delete.

Use it when

Starting any Celigo task and needing to confirm the right account and environment first
Working out whether to list, read or change something in an integration
Getting a blocked or permission-denied response and needing to know what to do next

Tools it uses

list_environments
list_flows
list_connections
list_flow_runs
list_flow_errors
list_exports
list_apis
list_iclients
list_ai_agents
list_guardrails
list_edi_profiles
list_edi_transactions
list_file_definitions
list_current_jobs
list_execution_logs
list_audit_log_entries
get_schema
get_flow_error_retry_data
get_storage_file_download_url
install_template
delete_resource
delete_lookup_cache_data
cancel_flow_run
cancel_storage_upload

Example

Before we look at anything, which Celigo environment are we working in, and how many flows are there?

You're in the production environment. There are 46 flows in it. I'll keep to listing and reading, and I won't change anything without your explicit yes.

Use in RevampKeyRead the full skill →

Read-only3 Celigo tools

Triage and retry Celigo flow errors

Works through open flow errors in your Celigo account, groups them by cause, and separates transient failures that are safe to retry from data or config problems that need fixing first. It asks for your approval before any retry.

Use it when

Your Celigo error queue has grown and you need to clear it safely
Many failed records share an error and you want to know if retrying will help
A connection expired and you want to confirm which errors it caused

Tools it uses

list_flow_errors
list_flow_runs
get_flow_error_retry_data

Example

Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.

There are 46 open errors across 3 clusters. 31 are timeouts from NetSuite returning 503 during its maintenance window; these are transient and the retry payloads check out. 12 are a missing required field, 'Customer Email', in the source records, so retrying will not help and the records need fixing in Shopify. 3 are expired-credential 401s from one connection. I propose retrying the 31 timeouts once NetSuite is healthy. Shall I go ahead?

Use in RevampKeyRead the full skill →

Read-only6 Celigo tools

Diagnose a failing Celigo flow with AI

Finds why one specific Celigo flow or run failed, working from its runs, logs and flow errors to a root cause. It asks before changing or retrying anything.

Use it when

A flow stopped syncing after last night's run
One integration keeps erroring on the same step
You need to know whether an edit caused a failure

Tools it uses

list_flows
list_flow_runs
list_execution_logs
list_flow_errors
get_flow_error_retry_data
list_connections

Example

Why did the Shopify to NetSuite order flow fail on last night's run?

The run failed at the NetSuite import step, starting with run 4821 at 02:14. The last good run was 4807 the evening before. The import rejected 37 records with the same error, "customer ID is required", all from one new Shopify storefront. The likely cause is a mapping that drops the customer field for that storefront. I haven't changed anything. Should I show you the mapping so you can review it before a retry?

Use in RevampKeyRead the full skill →

Read-only1 Celigo tools

Review your Celigo audit trail with AI

Reads the Celigo audit log for a chosen environment and time window, lines changes up against when a flow began failing, and reports the likely cause. Read-only; it asks before changing anything.

Use it when

A flow started failing and you want to know what changed just before it
You need to see who edited a connection or integration in the last week
You are preparing an audit trail for a review or handover

Tools it uses

list_audit_log_entries

Example

Something on the Shopify to NetSuite flow started failing on the 14th. Who changed it in the last week and what changed?

In production, the audit log shows 6 changes to the Shopify to NetSuite flow between the 10th and the 14th. The likeliest link is a mapping edit by Priya Nair at 16:40 on the 13th, the evening before the first failed run. I read 6 of 6 entries. I could not see the before and after values for that edit, so I cannot confirm the field. Should I list the connection changes next, or pause here?

Use in RevampKeyRead the full skill →

Asks before writing6 Celigo tools

Audit integration health across your Celigo account

Surveys your flows and integrations, finds the ones with open errors or recent failed runs, and returns a ranked list of what needs attention first. Read-only: it changes nothing and asks before any follow-up action.

Use it when

Start of the day, to see what broke overnight
Before a release, to confirm the account is clean
When someone asks which integrations are unhealthy

Tools it uses

list_flows
list_flow_errors
list_flow_runs
list_current_jobs
list_execution_logs
cancel_flow_run

Example

Audit my Celigo account and tell me which integrations need attention first.

I checked 86 flows in the production environment over the last 24 hours. Three need attention now: the Shopify to NetSuite order sync has 212 failed runs and 38 open errors, touching orders; the Salesforce accounts export has 19 failed runs; the invoice sync has 4 open errors. Eleven disabled flows have old errors and look intentional. The other 72 flows showed no errors or failed runs in that window. I could not check the sandbox environment because you have not switched to it.

Use in RevampKeyRead the full skill →

Get all 5 without copying a file

RevampKey adds the skills when you connect Celigo, updates them for you and removes them when you disconnect.

Download RevampKey

How Celigo skills work

Connect Celigo
The Celigo MCP server gives the agent its tools.
Ask in plain words
“Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.” Each SKILL.md says when it applies, so only the one that fits is loaded.
Approve any change
The agent calls the tools in order, checks its work, and shows you any change before it makes it.

How to install Celigo skills

In RevampKey the skills install themselves when you connect Celigo. In other tools each skill is one folder with a SKILL.md file, and you also need the Celigo MCP server connected there.

About 1 minute · nothing to copy

Download RevampKey for Mac, Windows or Linux and sign in.
Open Connectors and connect Celigo. All 5 skills come with it and stay up to date; they go away when you remove the connector.
Ask in plain language, for example “Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.”
Download RevampKeyConnect Celigo · 1 click
Get RevampKey to connect Celigo
RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Celigo is one click away with its skills already attached.
Download RevampKey
Not now? Use the skills in your current tool
for s in essentials error-retry-triage flow-failure-diagnosis integration-audit-trail-review integration-health-audit; do curl -fsSL --create-dirs -o .claude/skills/celigo-$s/SKILL.md https://revampkey.com/marketplace/celigo/skills/$s/SKILL.md done
Other tools

Into this project’s .claude/skills folder

Connect the Celigo MCP server in Claude Code.

Run this in your project folder to add all 5 skills:

for s in essentials error-retry-triage flow-failure-diagnosis integration-audit-trail-review integration-health-audit; do
  curl -fsSL --create-dirs -o .claude/skills/celigo-$s/SKILL.md https://revampkey.com/marketplace/celigo/skills/$s/SKILL.md
done

Ask in plain language, for example “Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.”

Into the shared .agents/skills folder

Connect the Celigo MCP server in Cursor.

Run this in your project folder to add all 5 skills:

for s in essentials error-retry-triage flow-failure-diagnosis integration-audit-trail-review integration-health-audit; do
  curl -fsSL --create-dirs -o .agents/skills/celigo-$s/SKILL.md https://revampkey.com/marketplace/celigo/skills/$s/SKILL.md
done

Ask in plain language, for example “Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.”

Into the shared .agents/skills folder

Connect the Celigo MCP server in Codex.

Run this in your project folder to add all 5 skills:

for s in essentials error-retry-triage flow-failure-diagnosis integration-audit-trail-review integration-health-audit; do
  curl -fsSL --create-dirs -o .agents/skills/celigo-$s/SKILL.md https://revampkey.com/marketplace/celigo/skills/$s/SKILL.md
done

Ask in plain language, for example “Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.”

Into the shared .agents/skills folder

Connect the Celigo MCP server in VS Code.

Run this in your project folder to add all 5 skills:

for s in essentials error-retry-triage flow-failure-diagnosis integration-audit-trail-review integration-health-audit; do
  curl -fsSL --create-dirs -o .agents/skills/celigo-$s/SKILL.md https://revampkey.com/marketplace/celigo/skills/$s/SKILL.md
done

Ask in plain language, for example “Triage the open errors on my Shopify to NetSuite flow and tell me which ones are safe to retry.”

RevampKey or copy the files?

In RevampKey

One click when you connect Celigo
Updated for you when a skill improves
Removed when you disconnect
The MCP server is set up for you
800+ other connectors, same way

Download free

Copy into your project

One command per project
Run it again to get updates
You connect the Celigo MCP server yourself
Works in Claude Code, Cursor, Codex and VS Code

See the command

Celigo skills FAQ

What is a Celigo agent skill?

A SKILL.md file: a short playbook an AI agent loads when your request matches it. Each Celigo skill describes one job, which Celigo tools to use in which order, what to check first and when to stop and ask you.

Do the Celigo skills change anything on their own?

3 of the 5 only read. The others tell the agent to show you the change and wait for a yes before it creates, edits or deletes anything in Celigo.

Which tools can use these skills?

Any agent that reads the open Agent Skills format: Claude Code, Cursor, Codex, VS Code with Copilot and RevampKey. In RevampKey they are attached when you connect Celigo; elsewhere you copy the folders into your project or skills directory.

Do I need the Celigo MCP server too?

Yes. The skills tell the agent how to do the work; the Celigo MCP server gives it the tools to do it. The Celigo MCP setup guide covers every client.

Celigo MCP server setup · This page as Markdown

Put Celigo’s best workflows in your agent

Download RevampKey, connect Celigo and ask your first question in about a minute.

Download RevampKey Connect Celigo · 1 click

All 5 Celigo skills

Use Celigo Platform MCP safely with AI

Use it when

Tools it uses

Triage and retry Celigo flow errors

Use it when

Tools it uses

Diagnose a failing Celigo flow with AI

Use it when

Tools it uses

Review your Celigo audit trail with AI

Use it when

Tools it uses

Audit integration health across your Celigo account

Use it when

Tools it uses

Get all 5 without copying a file

How Celigo skills work

How to install Celigo skills

RevampKey or copy the files?

In RevampKey

Copy into your project

Celigo skills FAQ

Put Celigo’s best workflows in your agent

Skills for related tools