Name: merge
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

merge

Merge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Merge data.

Quality

68%

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/merge/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 a tight, command-driven reference that is highly actionable and includes a genuine polling feedback loop for connection readiness. Main weaknesses are broken step numbering (a '1b' and a referenced 'Step 2' that don't exist) and a confusing placeholder 'Merge Overview' section.

Suggestions

Fix the workflow numbering: add a '1a'/'Step 1' header for `connection ensure` and label the actions step as 'Step 2' so the 'skip to Step 2' reference resolves.

Remove or replace the placeholder '## Merge Overview' bullet list ('PDF / Page / Merge'), which conveys no useful information.

Add a brief verification step after running actions (e.g., check the `output` field and error state) to complete the feedback loop for batch/run operations.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and mostly lean (install, login, connection, action, proxy commands with a compact flags table), with only minor over-explanation such as the intro paragraph and the uninformative '## Merge Overview' bullet list ('PDF / Page / Merge'); not a 5 because of those trims.	4 / 5
Actionability	It provides copy-paste-ready executable commands throughout (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run`, `membrane request` with a flags table); not a 5 because of unsubstituted placeholders (CONNECTION_ID, QUERY) and minor gaps.	4 / 5
Workflow Clarity	The connect workflow has an explicit validation feedback loop (poll state until READY, handle CLIENT_ACTION_REQUIRED, re-poll), giving clear checkpoints; not a 5 because numbering is broken ('#### 1b' with no 1a, references to a non-existent 'Step 2') and there is no post-run verification checkpoint.	4 / 5
Progressive Disclosure	The single-file skill is organized into clear, well-placed sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no external references needed; not a 5 because the 'Merge Overview' filler section and lack of an overview-vs-detail split leave minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

62%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 cleanly states both what the skill does and when to use it, and the named 'Merge' platform anchors it well against conflicts. Its weakness is generic action verbs and thin trigger-term coverage, which keep specificity and trigger quality at the midpoint.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Sync Merge data, manage records, and run Merge actions through pre-built connectors.'

Expand the trigger clause with natural phrasings users actually say: 'Use when connecting to Merge, querying or syncing Merge data, or running Merge API actions.'

Drop the filler 'Manage data, records' abstraction in favor of named Merge operations to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('Merge integration') plus a couple of actions ('Manage data, records' and 'automate workflows'), but the actions are fairly generic rather than comprehensive, matching the '1-2 concrete actions' anchor; not a 4 because the listed actions lack specificity.	3 / 5
Completeness	It states what ('Merge integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Merge data.'), but the trigger could name more concrete scenarios; not a 5 because the 'when' trigger phrases are not comprehensive.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Merge data' surfaces the natural keyword 'Merge data', but it misses common variations users would say (connect to Merge, integrate with Merge, Merge API, sync), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named 'Merge' platform gives it a clear niche with low conflict risk, but the generic verbs 'manage data, records, automate workflows' leave minor overlap with general data/workflow skills; not a 5 because the action language is not sharply distinct.	4 / 5
	Total	14 / 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/merge/SKILL.md
Commit: f484c82

Reviewed: 6 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.