Name: documerge
Rating: 56.8 (1 reviews)
Author: membranedev

documerge

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

Quality

65%

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

Quality

Content

67%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 actionable, well-structured CLI workflow with good validation checkpoints, held back mainly by a padded intro and reference material that could be progressively disclosed into separate files.

Suggestions

Trim the introductory marketing paragraph ('document automation platform that helps users generate documents... used by businesses of all sizes') to one line, since Claude can infer Documerge's purpose.

Move the proxy flag reference table and the full connection-state machine into a separate reference file, linking to it from the main flow to improve progressive disclosure.

Fix the step numbering (label 'Step 1' explicitly and resolve the dangling 'Step 2' reference) so the connection workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands, but the marketing-style intro paragraph and phrasing like 'so you can focus on the integration logic rather than auth plumbing' add unnecessary padding Claude could infer.	3 / 5
Actionability	Provides concrete executable CLI commands throughout (install, login, connection ensure, action list/run, request) with flags, leaving only minor gaps around placeholder values like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with state-check validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-then-retry feedback loop, though step labeling is inconsistent ('Step 2' referenced without a labeled Step 1).	4 / 5
Progressive Disclosure	Single-file skill with well-organized sections and no external bundle files; over 50 lines with some inlined reference material (proxy flag table, connection state machine) that could be split out, but overall well-structured and navigable.	4 / 5
	Total	15 / 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 covers both capability and trigger guidance and is anchored to a distinct product, but its action list is generic and it lacks richer natural-language trigger terms.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Generate documents from templates, merge records, and automate document workflows' instead of 'Manage data, records, and automate workflows'.

Add natural trigger synonyms users would say, such as 'templates', 'contracts', 'proposals', or 'document generation'.

Tighten the 'when' clause to name the specific tasks (e.g. 'Use when generating contracts, proposals, or reports from Documerge templates').

Dimension	Reasoning	Score
Specificity	Names the Documerge domain and a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete and coverage is not comprehensive.	3 / 5
Completeness	Explicitly states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Documerge data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product keyword 'Documerge' plus 'data' and 'records', but lacks common synonyms or file extensions that users might actually say.	3 / 5
Distinctiveness Conflict Risk	Anchored to a distinct named product (Documerge) with a product-specific trigger, leaving only minor overlap risk with generic data-management skills.	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/documerge/SKILL.md
Commit: f484c82

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