CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clip

Clip integration. Manage Recordses. Use when the user wants to interact with Clip data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/clip/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a competent, executable guide to driving Clip through the Membrane CLI, with genuine error-recovery handling for connection states and a useful proxy fallback. Its main weaknesses are a dangling 'Step 2' reference that breaks workflow navigation, an empty 'Popular actions' section that promises but never delivers concrete record operations, and minor redundancy that could be trimmed for token efficiency.

Suggestions

Define the step labels you reference: either add explicit 'Step 1' / 'Step 2' headings or replace both occurrences of 'skip to **Step 2**' with the actual section name (e.g. 'skip to Searching for actions').

Make 'Popular actions' earn its heading by listing 2-3 concrete Clip record actions (e.g. create/list/update a Record) with example action ids and input JSON, instead of repeating the discovery command already shown in 'Searching for actions'.

Trim low-value prose ('This is the fastest way to get a connection', the 'Agent Types' aside) and merge the duplicated action-list examples to tighten token usage.

DimensionReasoningScore

Conciseness

The body is command-driven and mostly efficient — CLI invocations, a flag table, and terse state-handling bullets with little padding. There are minor instances of over-explanation that could be trimmed: 'This is the fastest way to get a connection', the throwaway 'Agent Types' sentence, and two near-duplicate `action list` command forms in 'Searching for actions' vs 'Popular actions'. This matches anchor 4 ('efficient; minor instances of over-explanation') and is not anchor 5 because those trims exist; it is well above anchor 3's 'several unnecessary explanations'.

4 / 5

Actionability

Concrete, executable commands cover the whole path: `npm install -g @membranehq/cli@latest`, `membrane login --tenant --clientName=<agentType>`, `membrane connection ensure "https://clip.mx/" --json`, `membrane action run <actionId> ... --input '{"key": "value"}' --json`, plus a proxy flag table. It is not anchor 5 because common cases lack fully concrete examples: the 'Popular actions' heading lists no actual Clip actions (only a discovery command), and no example of a real record operation (e.g. creating a Record) with a real action id and input is shown. It is above anchor 3 because the guidance shown is executable, not pseudocode.

4 / 5

Workflow Clarity

A clear sequence is present (install → login → connection ensure → poll/handle state → search actions → run actions or proxy) with real checkpoints: `--wait` polling for BUILDING, explicit handling of READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with `clientAction` fields, and re-polling after user action. It is not anchor 5 because of a navigation defect: 'skip to **Step 2**' is referenced twice but no Step 1/Step 2 headings exist (only '#### 1b. Wait for the connection to be ready'), leaving a dangling reference, and 'Step 1' is never labeled. It is above anchor 3 because error states and recovery loops are explicitly handled rather than merely implied.

4 / 5

Progressive Disclosure

The skill has no bundle files (no references/, scripts/, or assets/ exist), and the single SKILL.md body is well-sectioned with clear headers (Install the CLI, Authentication, Connecting to Clip, Searching for actions, Running actions, Proxy requests, Best practices). This matches anchor 4 ('good structure; most content is appropriately placed; minor organization gaps'): the ~135-line body with the proxy options table and detailed clientAction reference inline is defensible for a single-purpose CLI integration, though it is somewhat long for one file and sections like the clientAction state handling could live in a reference file. It is not anchor 5 because there is no well-signaled split of overview vs detail content, and not anchor 3 because nothing is buried or clearly misplaced.

4 / 5

Total

16

/

20

Passed

Description

48%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 and usable 'Use when...' trigger clause tied to a named platform, but the capability statement is thin: one generic verb ('Manage') over an oddly pluralized object ('Recordses'), with no concrete operations or natural keyword variations. It is serviceable for discovery but clearly below the quality of the reference good examples.

Suggestions

Replace the generic 'Manage Recordses' with the concrete operations the skill actually supports, e.g. 'Create, read, update, delete, and list Clip records'.

Fix the non-standard plural 'Recordses' to 'Records' so the keyword matches what users would actually type.

Expand the trigger clause with natural variations and synonyms, e.g. 'Use when the user wants to interact with Clip data — creating, editing, fetching, or deleting records in Clip'.

DimensionReasoningScore

Specificity

The description names the domain ("Clip integration") but the only action offered is the generic verb "Manage Recordses" — no concrete operations (create, read, update, delete, list) are stated in the description itself. This matches anchor 2 ('Names the domain but actions are minimal or generic'); it is not anchor 3 because no concrete action like 'extracts content' is explicitly listed, and not anchor 1 because the domain is clearly named.

2 / 5

Completeness

The 'when' is explicit ("Use when the user wants to interact with Clip data"), but the 'what' is vague: "Clip integration" is fluff and "Manage Recordses" is a single non-concrete verb, so the description only weakly answers what the skill does. This falls between anchor 3 (clear 'what', missing 'when') and anchor 4 (both present, improvable) and sits at the midpoint rather than noticeably above it, so 3 is the best fit.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Clip", "Recordses", "interact with Clip data") but coverage is thin and misses natural variations and synonyms a user would say ("records", "add/edit data", CRUD terms), and "Recordses" is a non-standard plural users would never type. This is 'some relevant keywords but missing common variations or synonyms' (anchor 3), below anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The description names the specific platform "Clip" in both sentences, giving it a clear niche among app-integration skills with mostly distinct triggers. It is not anchor 5 because the standalone word "clip" carries minor ambiguity (clipboard, video clips) and no disambiguating synonyms are given; it is above anchor 3 because the repeated platform name makes overlap with unrelated skills unlikely.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.