Name: close
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

close

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

Quality

66%

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/close/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 executable commands and a strong connection-state workflow, weakened only by some introductory over-explanation and minor step-labeling ambiguity. It is well structured for a single-file skill with no external references.

Suggestions

Trim the opening marketing paragraph ('designed to help sales teams close more deals...') and the bare Close Overview list, which restate what the actions table already conveys.

Resolve the ambiguous 'skip to Step 2' reference by labeling the downstream sections as explicit numbered steps (e.g. Step 2: Search for actions).

Consider moving the 21-row Popular actions table into a references file and linking to it, keeping only the most common examples inline.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean command- and table-driven, but the opening 'Close is a CRM and sales engagement platform...' paragraph and the Close Overview list add explanation and mild marketing fluff that could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connect, poll, search actions, run actions, proxy) plus a concrete actions table and flag reference.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints and a poll→act→re-poll feedback loop, but the 'skip to Step 2' reference is ambiguous and there is no explicit post-action validation.	4 / 5
Progressive Disclosure	The single-file body is well organized into clearly headed sections with a useful inline actions table; no bundle files exist, and the 21-row reference table is the only bulk content that might warrant its own file.	4 / 5
	Total	16 / 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 uses third person and includes an explicit 'Use when' trigger, but it is thin on concrete actions and trigger-term variety. Expanding the action list and trigger phrases would lift specificity and trigger_term_quality.

Suggestions

Replace the generic 'Manage Organizations' with concrete actions, e.g. 'Manage leads, contacts, opportunities, and activities in Close.'

Broaden the trigger clause to include natural user phrasing, e.g. 'Use when the user wants to work with Close CRM data — leads, deals, contacts, or sales activities.'

Keep the named-app qualifier ('Close') to preserve distinctiveness from other CRM skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Close integration') but offers only one generic action ('Manage Organizations'), which is minimal and does not reflect the leads/contacts/opportunities scope shown in the body.	2 / 5
Completeness	Both 'what' ('Close integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Close data.') are present, though each could be more concrete.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Close', 'Close data') but misses the natural variations users would actually say (leads, contacts, deals, CRM, sales pipeline).	3 / 5
Distinctiveness Conflict Risk	Naming the specific Close CRM gives it a distinct niche with minimal conflict risk, though the generic 'Manage Organizations' phrasing could overlap slightly with other CRM/sales 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/close/SKILL.md
Commit: f484c82

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