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

Blog Docs Log in Get started

gist

Gist integration. Manage Organizations. Use when the user wants to interact with Gist 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/gist/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 an efficient, executable guide to the Membrane CLI workflow with a well-validated connection state machine and clear command coverage. Its main weakness is the lack of validation guidance around the destructive actions it exposes.

Suggestions

Add an explicit validation/confirmation step before destructive actions such as delete-contact and delete-tag (e.g. verify the target ID exists, confirm with the user).

Clarify the actionId vs Key relationship in the popular-actions table so the run command is unambiguous.

Trim the introductory paragraph explaining what Gist is, since Claude already knows this and it does not advance the task.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command references, tables, and state-handling guidance, with only minor over-explanation such as the introductory paragraph explaining what Gist is; it fits the 'Efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action listing, running, and proxying, with only minor gaps such as the popular-actions table giving 'Key' while the run command expects an actionId.	4 / 5
Workflow Clarity	The connection lifecycle is a clear sequence with explicit checkpoints and a feedback loop (polling BUILDING state, branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive actions like delete-contact/delete-tag are listed without validation guidance, leaving a minor gap.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) in a single file with no nested references; the inline popular-actions table is the only content that might benefit from a separate file, giving good but not exemplary structure.	4 / 5
	Total	16 / 20 Passed

Description

53%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 has an explicit 'Use when' trigger and names the Gist domain, but its capability statement is generic ('Gist integration') and the 'Manage Organizations' action does not match the skill's actual contact/conversation focus. Trigger keywords are present but thin.

Suggestions

Replace 'Manage Organizations' with the actual capabilities, e.g. 'Manage contacts, conversations, campaigns, and tags in Gist'.

Expand the trigger clause to name concrete user phrases like 'when the user wants to manage Gist contacts, conversations, or campaigns'.

Add synonyms/extensions users might say (e.g. 'Gist workspace', 'customer messages') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("Gist integration") and one action ("Manage Organizations") but offers no comprehensive list of concrete actions, matching the 'Names domain and 1-2 concrete actions' anchor; the single named action also appears mismatched to the actual contact/conversation content.	3 / 5
Completeness	Both a 'what' ("Gist integration. Manage Organizations.") and a 'when' ("Use when the user wants to interact with Gist data") are present, but the 'what' is generic rather than concrete actions, sitting between the clear-what/no-when (3) and both-present (4) anchors.	3 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Gist data" provides the natural term "Gist" but misses common variations or synonyms, fitting the 'Some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Gist is a distinct niche app and the trigger "interact with Gist data" is specific, giving mostly-distinct identification with only minor overlap risk against closely related CRM/messaging 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/gist/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.