Name: cloze
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

cloze

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

Quality

57%

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

Quality

Content

57%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 actionable and gives a clear connection/action workflow with good feedback loops for connection state, but it carries unnecessary marketing prose and inlines sizeable reference material. Destructive actions lack validation guidance, capping workflow clarity.

Suggestions

Trim the opening marketing paragraph about Cloze and the over-explanation of Membrane auth to tighten token efficiency.

Add a validation/confirmation checkpoint before destructive actions (delete-project/company/person) such as confirming the identifier or running a get-* first.

Move the full popular-actions table and proxy flag reference into a references/ file and link to it from SKILL.md for proper progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but opens with marketing prose about what Cloze is ('automatically captures data from emails, calls, meetings...') and lightly over-explains Membrane auth, which Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands (install, login, connection ensure, action list/run, request) with real flags and a concrete popular-actions table, with only minor placeholder gaps (CONNECTION_ID, <actionId>).	4 / 5
Workflow Clarity	The connection setup has a clear state-machine with polling feedback loops (BUILDING/CLIENT_ACTION_REQUIRED/READY), but destructive actions (delete-project, delete-company, delete-person) are featured as popular actions with no validation or confirmation guidance, capping this dimension at 3.	3 / 5
Progressive Disclosure	The skill is well-sectioned but entirely monolithic: the 18-row popular-actions table and proxy-options reference are inlined in SKILL.md with no bundle files (references/scripts/assets are absent) and no one-level-deep references to split out the reference material.	3 / 5
	Total	13 / 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 'what' and a 'Use when' trigger in third person, but the capability list is thin and generic. It is distinct thanks to the named Cloze platform yet lacks the concrete action breadth of strong examples.

Suggestions

Replace the generic 'Manage Organizations' with several concrete actions (e.g., 'find and update people, manage projects and companies, create to-dos').

Expand the trigger clause with natural variations users would say (e.g., 'contacts', 'deals', 'projects in Cloze').

Keep the third-person voice but add 1-2 more specific capabilities to lift specificity toward the 4-5 anchors.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Cloze integration') but only offers one generic action ('Manage Organizations'), which is minimal and not concrete like 'extract', 'fill', or 'merge'.	2 / 5
Completeness	It states both what ('Cloze integration. Manage Organizations.') and when ('Use when the user wants to interact with Cloze data.'), but the 'what' is sparse and the trigger could be more specific.	4 / 5
Trigger Term Quality	'Cloze' and 'Cloze data' are relevant natural keywords a user would say, but coverage is thin with no synonyms or variations beyond the product name.	3 / 5
Distinctiveness Conflict Risk	'Cloze' is a named, specific platform giving it a clear niche with low conflict risk, though the generic 'interact with Cloze data' trigger leaves minor overlap ambiguity with other CRM-style 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/cloze/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.