Name: documo
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

documo

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

Quality

68%

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

Quality

Content

75%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 executable Membrane CLI commands and a solid connection-state workflow, but it opens with conceptual filler about what Documo is and has minor step-numbering inconsistencies. Trimming the intro and tightening the numbered sequence would push conciseness and workflow clarity higher.

Suggestions

Cut or compress the opening overview paragraph ("Documo is a document management and automation platform...") since it explains the product rather than how to use the skill.

Normalize the connection steps into a single numbered list (1 install, 2 authenticate, 3 ensure connection, 4 wait for READY) and remove the orphan "Step 2" / "1b" references.

Add an explicit validation/retry checkpoint for `membrane action run` failures (check the `output`/error field, fix inputs, re-run) to match the rigor of the connection feedback loop.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Documo is ("used by businesses of all sizes to streamline document workflows... central hub for creating, storing, and managing documents") and adds soft phrasing like "so you can focus on the integration logic rather than auth plumbing" — concept padding Claude doesn't need, though most of the file is efficient CLI commands.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, polling, action list/run, request with the proxy flags table), with concrete examples covering the common cases.	5 / 5
Workflow Clarity	A clear connection sequence with an explicit state-machine feedback loop (READY / BUILDING / CLIENT_ACTION_REQUIRED → "poll again" after the user acts), but step numbering is inconsistent ("skip to Step 2" with no matching Step 1/Step 2 headers, plus a stray "1b").	4 / 5
Progressive Disclosure	Single self-contained file with well-organized section headers and no nested references (only an external docs URL); it is over 50 lines with a fair amount inlined, so it stops just short of the lean-overview ideal.	4 / 5
	Total	16 / 20 Passed

Description

61%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 cleanly states what and when and is distinct thanks to the named Documo platform, but its action list is generic rather than concrete and its trigger-term coverage is thin. Tightening it with specific Documo actions and richer trigger phrasing would lift the lower dimensions.

Suggestions

Replace generic verbs with concrete Documo actions, e.g. "Create, send, and sign documents, manage folders and records, and automate document workflows."

Expand the trigger clause with natural variations: "Use when the user wants to send or sign Documo documents, manage folders/records, or automate document workflows."

Drop the filler openers ("Documo integration.") so the description leads with concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" are generic verbs, not concrete Documo-specific actions (e.g. create documents, send for signature, manage folders); the domain is named but the actions are minimal/generic.	2 / 5
Completeness	Both halves are present: a "what" ("Documo integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Documo data"), though the when could be more trigger-specific.	4 / 5
Trigger Term Quality	"Documo" and "Documo data" are relevant natural terms, but coverage stops there — no synonyms, related phrases, or file extensions beyond the single platform name.	3 / 5
Distinctiveness Conflict Risk	Anchoring on a named platform ("Documo") gives it a clear niche with distinct triggers and minimal conflict risk versus other skills.	5 / 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/documo/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.