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

docupost

DocuPost integration. Manage Documents, Users, Groups, Folders, Tags, Templates and more. Use when the user wants to interact with DocuPost 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/docupost/SKILL.md

Quality

Content

68%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 content is highly actionable with concrete CLI commands and a clear connection-state workflow, but it carries marketing-flavored preamble and lacks validation/confirmation before destructive actions like sending physical mail. Structure is clean for a single-file skill.

Suggestions

Delete the product-marketing intro paragraph ("DocuPost is a document management... Think of it as a central hub") and the "focus on the integration logic" aside; Claude does not need this framing.

Add an explicit confirmation checkpoint before `membrane action run` for destructive/outward-facing actions (e.g., "Confirm with the user before running send-letter/send-postcard, as these are irreversible.").

Fix the dangling "Step 2" references by either numbering the workflow steps (Step 1, Step 2) or removing the cross-references so the sequence is self-contained.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI commands, but the opening "DocuPost is a document management and automation platform... Think of it as a central hub" and lines like "so you can focus on the integration logic rather than auth plumbing" explain context Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with clearly marked placeholders and a flags table, covering the common cases comprehensively.	5 / 5
Workflow Clarity	A sequence exists and the connection section has a poll-after-action feedback loop, but running destructive real-world actions ("Send Letter", "Send Postcard") has no confirmation checkpoint, capping clarity at 3; references to an undefined "Step 2" also add gaps.	3 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well organized into clear sections with headers; the proxy-flags and popular-actions tables are minor inline reference material that could be split out, fitting the 4 anchor.	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 is third-person, product-specific, and answers both what and when, but its action vocabulary is generic and its trigger phrasing lacks natural synonyms. It is solid but could be sharpened with concrete verbs and more user-natural triggers.

Suggestions

Replace the single generic verb "Manage" with concrete actions (e.g., "Create, search, send, and track Documents, Users, Groups...") to raise specificity.

Add natural trigger phrases users would say, such as "Use when the user wants to send letters/postcards, search DocuPost records, or automate document workflows."

Mirror the entity nouns with everyday synonyms (e.g., "mailings", "records") so the trigger terms match how users phrase requests.

Dimension	Reasoning	Score
Specificity	It names the domain and many concrete resource types ("Documents, Users, Groups, Folders, Tags, Templates") but only one generic action verb ("Manage ... and more"), so actions are not comprehensive enough for a 4.	3 / 5
Completeness	It answers both "what" ("Manage Documents, Users, Groups, Folders, Tags, Templates") and "when" ("Use when the user wants to interact with DocuPost data"), but the "when" clause is somewhat generic rather than concrete, fitting the 4 anchor.	4 / 5
Trigger Term Quality	It surfaces the product name and several entity keywords but relies on the generic phrase "interact with DocuPost data", missing the common natural variations and synonyms users would actually say.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("DocuPost integration") gives it a clear, distinct niche with low conflict risk, though the generic "Manage Documents..." phrasing could mildly overlap with other document 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/docupost/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.