Name: documentpro
Rating: 52.8 (1 reviews)
Author: membranedev

documentpro

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

Quality

58%

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/documentpro/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 highly actionable with concrete, executable Membrane CLI commands and a clear connection-state workflow with validation checkpoints. Its main defects are a leaked LLM apology line that should be removed, an introductory paragraph explaining the app, and a broken step numbering ('1b' / 'Step 2') that mildly hurts workflow clarity.

Suggestions

Delete the leaked artifact on line 19 ('I am sorry, I cannot provide the API documentation URL...') — it is model output noise, not skill content.

Fix the step numbering: replace '#### 1b. Wait for the connection to be ready' with a proper 'Step 1 / Step 2' sequence and label the 'Step 2' referenced in the READY branch.

Tighten or move the opening 'DocumentPro is a document management system...' paragraph and the proxy-flag table into a short reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient concrete commands, but it opens by explaining what DocumentPro is and contains a leaked LLM apology ('I am sorry, I cannot provide the API documentation URL...') that is pure noise, pulling it down from efficient.	3 / 5
Actionability	It provides copy-paste-ready CLI commands for every stage (install, login, connection ensure/get, action list/run, request) with flags and a parameter table, with only minor gaps like the unresolved 'Step 2' reference.	4 / 5
Workflow Clarity	The connect-to-run sequence is clear with explicit state-based validation (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after action), though the '#### 1b' heading and unlabeled 'Step 2' references introduce minor sequencing gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Overview, Working with DocumentPro, Popular actions, Best practices) with no nested references, though it is over 50 lines and the proxy-flag table plus best-practices detail could arguably live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

50%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 correctly includes both a capability statement and an explicit 'Use when' trigger in third-person voice, but the actions are generic ('manage', 'automate') rather than concrete and the trigger terms are not natural user phrases. It is functional but lacks the specificity that would make it reliably surface for the right requests.

Suggestions

Replace generic verbs with concrete DocumentPro operations (e.g., 'upload and classify documents, extract fields from invoices, search records by metadata').

Expand the trigger to natural user phrases and file/term synonyms (e.g., 'Use when the user mentions DocumentPro, invoice extraction, document classification, or managing document records').

Name specific DocumentPro object types from the body (Document, Page, Template, Workspace) to sharpen distinctiveness from generic data skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('DocumentPro') but the actions — 'Manage data, records, and automate workflows' — are generic verbs with no concrete operations, matching the anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with DocumentPro data') are explicitly present, though both are somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Keywords ('data', 'records', 'workflows') are generic and the trigger phrase 'interact with DocumentPro data' is not a natural phrase users would say, missing common variations and synonyms.	2 / 5
Distinctiveness Conflict Risk	Naming the specific app 'DocumentPro' gives it a clear niche with minimal conflict risk, though the generic action verbs ('manage data, records') leave minor overlap with related data-management skills.	4 / 5
	Total	12 / 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/documentpro/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.