Name: ceipal
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ceipal

Ceipal integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ceipal 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/ceipal/SKILL.md

Quality

Content

75%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 concrete Membrane CLI commands and a strong, state-aware connection workflow including feedback loops. Its main weaknesses are modest verbosity from background exposition and a long inline entity list that could be split into a reference file.

Suggestions

Trim the opening platform background ('Ceipal is a comprehensive talent management platform...') to a one-line context, since Claude does not need the marketing-style explanation.

Move the ~30-item entity list and the proxy-flags table into a separate references file linked from the body to improve progressive disclosure and token efficiency.

Add a short numbered quick-start checklist at the top (install → login → connection ensure → action list → action run) so the end-to-end workflow is scannable at a glance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands and tables, but it includes background Claude largely does not need ('Ceipal is a comprehensive talent management platform...') and a long inline bullet list of ~30 entity names that could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with a concrete flags table, matching the 'fully executable, copy-paste ready' anchor.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence exists, and the connection flow has explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/ERROR) with a poll-again feedback loop; held from 5 because the overall flow is section-based rather than a tight numbered checklist with validation at each stage.	4 / 5
Progressive Disclosure	No bundle files exist and the content is organized into well-labeled sections, so navigation is easy; it is not a 5 because the document runs long (~110 lines) with the entity list and proxy flags inlined where a separate reference could help.	4 / 5
	Total	16 / 20 Passed

Description

70%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 is third-person, concise, and includes an explicit 'Use when' trigger tied to a named product, giving it strong distinctiveness and completeness. It is held back from the top band by generic, abstract action verbs ('Manage data, records') rather than concrete Ceipal capabilities.

Suggestions

Replace generic verbs with concrete Ceipal actions, e.g. 'Manage candidates, jobs, clients, and placements, and automate recruiting workflows.'

Sharpen the trigger clause with natural user phrasings, e.g. 'Use when the user wants to query or update Ceipal candidates, jobs, submissions, or placements.'

Mention the recruiting/talent-management domain in the description to reinforce distinctiveness from generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Ceipal) and a few actions ('Manage data, records, and automate workflows'), but those actions are generic and abstract rather than concrete Ceipal capabilities, fitting the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Ceipal data') are present and explicit, though the 'when' clause is somewhat generic.	4 / 5
Trigger Term Quality	'Ceipal' and 'Ceipal data' are natural trigger terms a user would say; for a named SaaS product this is good coverage, though a few more natural phrasings could be added.	4 / 5
Distinctiveness Conflict Risk	The named product 'Ceipal' gives a clear, distinct niche with minimal conflict risk; it is not a 5 only because the description does not characterize the HR/recruiting domain that would further distinguish it.	4 / 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/ceipal/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.