Name: celigo
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

celigo

Celigo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Celigo data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/celigo/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, mostly actionable CLI guide with a strong connection-state workflow, but it explains iPaaS concepts Claude already knows and omits validation/verification steps for destructive proxy and action operations.

Suggestions

Cut the introductory paragraph defining iPaaS and naming user roles; keep only the official docs link and move straight to working with Celigo.

Add a validation/verification checkpoint for destructive operations, e.g. before proxy POST/PUT/PATCH/DELETE or record-mutating actions, confirm the target and inspect the response output for success.

Flesh out the 'Popular actions' section with a few concrete example action names/intents, or remove the empty heading to avoid a dead reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and code, but the opening paragraph explaining what an iPaaS is and who uses Celigo ('It's used by IT professionals, business analysts, and citizen integrators...') plus phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanations Claude does not need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete copy-paste commands cover install, auth, connect, search, run, and proxy with a full flags table, but placeholders (CONNECTION_ID, <actionId>, QUERY) and a 'Popular actions' section that only repeats the discovery command rather than listing any actions leave minor gaps, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection flow has clear state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but running actions and proxy requests support destructive verbs (PUT/PATCH/DELETE) with no validation or verification guidance, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no need for external bundle files (none present); the thin 'Celigo Overview' bullets and inlined proxy/connection detail are minor organization gaps rather than misplacements, matching 'good structure; most content appropriately placed'.	4 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly names the Celigo domain and provides an explicit 'Use when' trigger, with strong distinctiveness from the brand specificity. It is held back by generic action verbs ('manage data, records') and thin trigger-term coverage that omits common synonyms.

Suggestions

Replace generic verbs with concrete Celigo operations, e.g. 'Create and manage integration flows, run and monitor records, and automate workflows between NetSuite, Salesforce, and other SaaS apps.'

Expand the trigger phrase to cover natural variations users say: 'Use when the user wants to manage Celigo integrations, build or troubleshoot flows, or move data between NetSuite, Salesforce, and other connected apps.'

Dimension	Reasoning	Score
Specificity	Names the Celigo domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage') rather than concrete operations, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states both what ('Celigo integration. Manage data, records, and automate workflows.') and an explicit when ('Use when the user wants to interact with Celigo data'), but the when is a single trigger phrase that could be more specific, matching 'has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Celigo data' supplies the natural keyword 'Celigo' but misses common variations/synonyms a user might say (NetSuite, Salesforce, iPaaS, flows, integration), fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tied to the specific Celigo brand with a distinct trigger ('interact with Celigo data'), giving a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/celigo/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.