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

Blog Docs Log in Get started

kaleido

Kaleido integration. Manage Organizations. Use when the user wants to interact with Kaleido 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/kaleido/SKILL.md

Quality

Content

68%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 executable Membrane CLI commands and a clear connection/state workflow, but it is capped on workflow clarity by missing validation loops for destructive create actions and is weighed down by an inaccurate, padded intro paragraph. Structure is solid for a single-file skill.

Suggestions

Add a validate→fix→retry feedback loop around the destructive create actions (e.g. verify the new consortium/environment exists and is in a healthy state before proceeding) to lift workflow clarity above the batch-operation cap.

Fix the dangling step numbering ('Step 2' with no Step 1, '1b' with no '1a') and reconcile the misleading intro that describes image/PDF conversion rather than the blockchain/consortia service the actions actually target.

Tighten or remove the generic opening paragraph that explains what Kaleido is, since it both pads tokens and contradicts the skill's real purpose.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete commands, but the opening paragraph over-explains what the product is ('Kaleido is a simple API for converting HTML, CSS, and JavaScript into static images or PDFs...') and some best-practice prose could be tightened, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened.'	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end (install, login, connection ensure, connection get --wait, action list/run with --input JSON, request proxy) plus a full actions table, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases.'	5 / 5
Workflow Clarity	A sequenced install→login→connect→search→run flow with state-based checkpoints exists, but destructive/batch create actions (create-consortium, create-environment, create-node) lack a validate→fix→retry feedback loop, and 'Step 2'/'1b' numbering is dangling, so per the batch-operations cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist, and the single SKILL.md is organized into clear, well-labeled sections (Overview, Working with Kaleido, Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices), matching 'good structure; most content is appropriately placed; minor organization gaps.'	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes both a capability statement and an explicit 'Use when' trigger, and the named product gives it a distinct niche. Its weakness is generic capability language ('Manage Organizations') and a trigger clause that lacks concrete task-level keywords.

Suggestions

Replace the generic 'Manage Organizations' with specific concrete actions such as 'List and create consortia, environments, nodes, and services' to lift specificity.

Expand the 'Use when' clause with concrete trigger phrases users would actually say, e.g. 'Use when managing Kaleido blockchain consortia, environments, nodes, or memberships'.

Mirror the natural terms from the body's action table (consortia, environments, nodes, services, memberships) so the description's keywords match user intent.

Dimension	Reasoning	Score
Specificity	Only 'Manage Organizations' is offered as a concrete action, which is generic; the domain (Kaleido, Organizations) is named but the action set is minimal rather than comprehensive, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both 'what' ('Kaleido integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with Kaleido data.') are explicit, but the 'when' clause is generic rather than concrete trigger phrases, so it sits below the 5 anchor at 'has both what and when; when could be more explicit or specific.'	4 / 5
Trigger Term Quality	The trigger 'interact with Kaleido data' includes the recognizable product keyword, but it lacks natural task variations or synonyms users would say (consortia, environments, nodes, blockchain), fitting 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	The named product 'Kaleido' carves a clear niche with minimal conflict risk, though 'Manage Organizations' / 'interact with Kaleido data' is broad enough for minor overlap with related skills, matching 'mostly distinct; minor overlap risk with closely related skills.'	4 / 5
	Total	13 / 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/kaleido/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.