Name: jelastic
Rating: 55.2 (1 reviews)
Author: membranedev

jelastic

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 highly actionable with well-sequenced connection handling, but carries some redundant padding and keeps all detail inline rather than splitting it into reference files.

Suggestions

Trim redundant padding: fold the 'Popular actions' section (which repeats the action-list command) into 'Running actions', and cut or expand the bare 'Jelastic Overview' bullet list.

Move the proxy flags table and detailed action-discovery material into a references file (e.g. REFERENCE.md) and link to it from SKILL.md to improve progressive disclosure.

Resolve the undefined 'Step 2' reference so the connection workflow's checkpoint navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unnecessary padding (the thin 'Jelastic Overview' list and a 'Popular actions' section that repeats the action-list command already shown).	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request proxy) plus a flags table; minor gaps remain around placeholders like CONNECTION_ID and actionId.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling loop; the dangling 'skip to Step 2' reference is a minor gap.	4 / 5
Progressive Disclosure	All content is inlined in a single ~140-line file with section headers but no external references, and the API-ish material (flags table, action discovery, best practices) could reasonably live in separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

62%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 product-specific and includes an explicit 'Use when' trigger, but its capability list is generic and keyword coverage beyond 'Jelastic' is thin.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with 3-4 concrete Jelastic actions (e.g., 'create and scale environments, manage nodes, deploy applications') to lift specificity.

Add natural trigger synonyms and the connection/target phrasing users actually say, e.g. 'Use when the user wants to manage Jelastic environments, nodes, or deployments'.

Tighten the 'what' to concrete actions so completeness reads as clearly and explicitly answering both what and when.

Dimension	Reasoning	Score
Specificity	Names the Jelastic domain and a couple of actions ("Manage data, records, and automate workflows"), but those actions are generic and not comprehensive, fitting the 'domain + 1-2 concrete actions' anchor rather than the fuller list at score 4.	3 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Jelastic data") are present; the when is reasonably explicit, though the what is somewhat generic.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with Jelastic data" surfaces the core keyword "Jelastic", but coverage lacks common variations or synonyms beyond that single term.	3 / 5
Distinctiveness Conflict Risk	The product-specific term "Jelastic" carves a clear niche with a distinct trigger, keeping overlap risk low, though the generic 'manage data' framing leaves minor overlap potential with other data skills.	4 / 5
	Total	14 / 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/jelastic/SKILL.md
Commit: f484c82

Reviewed: 5 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.