Name: documint
Rating: 60 (1 reviews)
Author: membranedev

documint

Documint integration. Manage Documents, Templates, Folders, Users, Teams, Workspaces. Use when the user wants to interact with Documint data.

Quality

70%

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/documint/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 a well-structured, actionable CLI integration guide with strong sequencing and polling-based feedback loops for connection readiness. Its main weakness is token efficiency — a marketing-style intro and a few soft sentences pad the otherwise lean command reference.

Suggestions

Remove or drastically shorten the opening marketing paragraph ('Documint is a document automation platform that helps users...'); Claude does not need the business pitch.

Tighten soft sentences like 'so you can focus on the integration logic rather than auth plumbing' to just state the behavior.

Fix the dangling 'skip to Step 2' reference by either labeling the next section 'Step 2' or rewording to 'skip to Searching for actions below'.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening marketing paragraph ('Documint is a document automation platform that helps users create and manage documents... used by businesses of all sizes to streamline...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, connection get --wait, action list/run, request) plus a full proxy flag table, with only minor gaps such as generic <actionId>/CONNECTION_ID placeholders and no example with real input JSON values.	4 / 5
Workflow Clarity	The install → login → connect → poll-until-ready → search → run sequence is clear with state-based checkpoints and explicit feedback loops ('poll again... to check if state moved to READY', 'Keep polling until state is no longer BUILDING'), but the dangling 'skip to Step 2' reference (no Step 2 heading exists) and inconsistent step numbering hold it below a 5.	4 / 5
Progressive Disclosure	No bundle files exist and the content is well-organized into clearly headed sections with no nested references, but the skill is over 50 lines and the detailed clientAction state reference and proxy flag table are inlined rather than split out, leaving minor organization gaps versus the ideal overview-with-references structure.	4 / 5
	Total	15 / 20 Passed

Description

73%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 brand-distinctive and supplies both a capability summary and an explicit 'Use when' trigger, scoring well on completeness and distinctiveness. Its main weakness is the single generic verb 'Manage' covering many objects rather than listing distinct concrete actions.

Suggestions

Replace the generic verb 'Manage' with distinct concrete actions, e.g. 'Create, list, and get Documents, Templates, and Folders; manage Users, Teams, and Workspaces.'

Expand the trigger clause with concrete examples, e.g. 'Use when the user wants to create documents from templates, list templates, or manage Documint folders, users, or workspaces.'

Dimension	Reasoning	Score
Specificity	It names the domain and enumerates concrete entities ('Manage Documents, Templates, Folders, Users, Teams, Workspaces'), but the single generic verb 'Manage' is the only action — it does not list distinct concrete actions like create, list, or get, matching the anchor that names the domain with minimal/generic actions.	3 / 5
Completeness	Both 'what' (Documint integration managing the listed entities) and 'when' ('Use when the user wants to interact with Documint data') are present, but the 'when' clause is somewhat generic rather than enumerating concrete trigger phrases, fitting the anchor where 'when' could be more explicit.	4 / 5
Trigger Term Quality	Good keyword coverage including the brand 'Documint' plus natural entity terms (Documents, Templates, Folders, Users, Teams, Workspaces) and an explicit 'Use when the user wants to interact with Documint data' trigger, though a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The description is brand-anchored to 'Documint integration' and triggers specifically on 'Documint data', giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/documint/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.