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

Blog Docs Log in Get started

creatio

Creatio integration. Manage Leads, Organizations, Users. Use when the user wants to interact with Creatio data.

Quality

64%

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

Quality

Content

62%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 skill delivers strong executable CLI guidance and a well-validated connection workflow, but a massive inline noun list wastes tokens and reference-style content is not offloaded into bundle files. Actionability and workflow clarity are its strengths; conciseness and progressive disclosure are its weaknesses.

Suggestions

Remove or drastically trim the ~140-line bullet list of bare nouns; it adds no actionable guidance and burns context tokens.

Move the popular-actions table and the long entity list into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Replace the vague closer 'Use action names and parameters as needed' with a concrete pointer to the action-list/search command.

Dimension	Reasoning	Score
Conciseness	The ~140-line flat bullet list of bare nouns (Contact, Account, Opportunity ... Support) is heavy padding that adds no actionable value and inflates the token budget, though the CLI sections themselves are reasonably lean. Noticeably verbose with several padded sections, matching anchor 2.	2 / 5
Actionability	Provides copy-paste-ready CLI commands with real flags and JSON examples (action run --input, request --method/--header/--data, polling), covering the common cases. The trailing 'Use action names and parameters as needed' is vague, leaving minor gaps, so anchor 4 rather than 5.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with an explicit state feedback loop (BUILDING -> poll -> READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-polling after a user action, plus a discover-before-build best practice. Matches anchor 5 (explicit validation steps and error-recovery loops).	5 / 5
Progressive Disclosure	No bundle files exist, and the large inline noun list and popular-actions table are reference-style content that arguably belongs in a separate file yet is inlined. Section headers give some structure, fitting anchor 3 (some structure, content that should be separate is inline).	3 / 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 answers both what and when and is anchored to a distinct platform, but its actions are generic ('Manage') and trigger phrasings lack synonyms. It is solid but not exemplary.

Suggestions

Replace the generic 'Manage Leads, Organizations, Users' with concrete actions (e.g. 'create, update, and list leads, organizations, and users').

Broaden the trigger with natural variations, e.g. 'Use when the user wants to interact with Creatio data — querying, creating, or updating CRM records.'

Dimension	Reasoning	Score
Specificity	Names the Creatio domain and entities (Leads, Organizations, Users) but the only action verb is the generic 'Manage', so coverage is not comprehensive. It sits above anchor 2 (minimal actions) but below anchor 4 (several specific actions).	3 / 5
Completeness	Both 'what' (Creatio integration, Manage Leads/Organizations/Users) and an explicit 'when' clause are present, but the 'when' is fairly generic. Fits anchor 4 (has both; 'when' could be more specific) rather than the concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Creatio data' supplies the natural term 'Creatio', but no synonyms or common phrasings of the intent are covered. Matches anchor 3 (some relevant keywords, missing common variations).	3 / 5
Distinctiveness Conflict Risk	'Creatio' is a specific named platform with a distinct trigger, giving it a clear niche and minimal overlap with other skills. Matches anchor 5 (clear niche, minimal conflict risk).	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/creatio/SKILL.md
Commit: f484c82

Reviewed: ~14 hours 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.