Name: celonis-ems
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

celonis-ems

Celonis EMS integration. Manage Organizations. Use when the user wants to interact with Celonis EMS data.

Quality

72%

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/celonis-ems/SKILL.md

Quality

Content

78%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 body is highly actionable with copy-paste CLI commands and a well-structured, state-aware connection workflow, but it opens with concept padding Claude doesn't need and has a couple of dangling step references. Trimming the intro and fixing the Step 2 anchor would tighten it further.

Suggestions

Delete or compress the opening "Celonis EMS is an execution management system..." paragraph; assume Claude knows what Celonis is and lead directly with the integration workflow.

Label the "Step 2" target referenced after a READY connection so the skip instruction resolves to an actual section, or rephrase as "skip to Searching for actions".

Add a brief validation note before proxy requests (e.g. confirm the endpoint path and method) since `membrane request` can issue destructive HTTP methods.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Celonis EMS is an execution management system that helps businesses identify and eliminate inefficiencies...") over-explains what Celonis is and who uses it — concepts Claude already knows — which the rest of the body largely avoids, matching anchor 3.	3 / 5
Actionability	Executable, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action list/run, request proxy) covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The connection flow has a state-based feedback loop (BUILDING poll, CLIENT_ACTION_REQUIRED re-poll, CONFIGURATION_ERROR check), but the "skip to Step 2" reference points at an unlabeled step and proxy/destructive calls lack validation, matching anchor 4.	4 / 5
Progressive Disclosure	This single-file skill with no bundle files is organized under clear section headers (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references, meeting the organized-sections bar for anchor 5.	5 / 5
	Total	17 / 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 names a distinct product niche and supplies both a what and a when, but its action list is thin and trigger phrasing is generic. Expanding concrete actions and natural-language triggers would lift specificity and completeness.

Suggestions

Enumerate more concrete actions beyond "Manage Organizations" (e.g. query Knowledge Models, list KPIs, run analyses) to raise specificity.

Broaden trigger terms with natural variations users say (e.g. "process mining", "Celonis data", "Knowledge Model") instead of only "Celonis EMS data".

Make the 'when' clause more explicit with concrete triggers, e.g. "Use when the user asks about Celonis EMS, process mining, or Knowledge Model data."

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names the domain plus one concrete action but offers no comprehensive action list, matching anchor 3; it is not 4 because only a single action is enumerated.	3 / 5
Completeness	It states both what ("Celonis EMS integration. Manage Organizations.") and when ("Use when the user wants to interact with Celonis EMS data."), but the when is generic, matching anchor 4 rather than the concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	"Celonis EMS integration" and "interact with Celonis EMS data" surface the core term but omit synonyms or extensions (e.g. process mining), matching anchor 3 rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"Celonis EMS" is a clearly named product niche with distinct triggers and minimal overlap risk, matching anchor 5.	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/celonis-ems/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.