Name: merge-1
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

merge-1

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/merge-1/SKILL.md

Quality

Content

63%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 delivers strong executable guidance and a reasonably sequenced workflow with validation, but it is monolithic with some restated context and mild redundancy. Splitting reference material into bundle files and tightening prose would raise the lower dimensions.

Suggestions

Move the full proxy flag reference and connection-state handling into separate reference files linked from the overview, reducing the main body.

Trim the Merge intro paragraph and auth prose to assume Claude's competence.

Reconcile the 'Searching for actions' and 'Popular actions' sections and fix the 'Step 2' / '1b' numbering so the workflow steps are consistently labeled.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command/flag examples, but the intro paragraph restates what Merge is and some auth prose ('so you can focus on the integration logic rather than auth plumbing') could be trimmed.	3 / 5
Actionability	Concrete copy-paste CLI commands, a flag table, and JSON input examples cover common cases; minor gaps remain in placeholder substitution and the redundant 'Searching for actions' vs 'Popular actions' sections.	4 / 5
Workflow Clarity	A clear sequence (install, authenticate, connect, poll for state, search, run) with validation via state-checking and a feedback loop for CLIENT_ACTION_REQUIRED; numbering is slightly inconsistent ('Step 2' referenced without clean step labels).	4 / 5
Progressive Disclosure	No bundle files exist, so everything is inline in a single ~140-line file; the full flag reference and state-handling detail could live in separate files, and the 'Merge Overview' bullet list is unexplained.	3 / 5
	Total	14 / 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 is functional, naming the product and including a 'Use when' trigger, but its capability list is generic. Tightening the actions and adding synonyms would lift the lower dimensions.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with 2-3 concrete actions (e.g., 'sync CRM contacts, fetch ticketing records, trigger workflow automations').

Add natural trigger synonyms beyond 'Merge data' so users phrasing the need differently still surface the skill.

Make the 'when' clause more specific about the scenarios (e.g., 'Use when the user wants to read or write data in a connected third-party tool via Merge').

Dimension	Reasoning	Score
Specificity	Names the Merge domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'Use when the user wants to interact with Merge data' trigger are present; not a 5 because the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'Merge' / 'Merge data'; it lacks synonyms or common variations users might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Merge is a named integration product, giving a clear niche with minor overlap risk against other integration skills, matching the 'mostly distinct' anchor.	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-1/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.