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

Blog Docs Log in Get started

docsumo

Docsumo integration. Manage Documents, Workspaces, Users, Roles. Use when the user wants to interact with Docsumo 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/docsumo/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 a well-structured, actionable CLI integration guide with a clear connection workflow and validation checkpoints, slightly held back by minor padding, placeholder-based examples, and an unlabeled step reference.

Suggestions

Trim the product-overview opening and rhetorical padding (e.g., "so you can focus on the integration logic rather than auth plumbing") to tighten token efficiency.

Add one fully-worked action example with a real-ish input JSON and expected output so guidance is copy-paste ready beyond placeholder patterns.

Fix the dangling "Step 2" reference by labeling the workflow steps explicitly, and add a brief output/error-check note after running actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but includes minor padding such as the product overview paragraph and phrasing like "so you can focus on the integration logic rather than auth plumbing", matching the anchor for efficient content with minor over-explanation that could be trimmed.	4 / 5
Actionability	Commands are concrete and executable (install, login, connection ensure, action list/run, request) with a flags table and actions table, but rely on placeholders (CONNECTION_ID, <actionId>, <id>) and lack a fully-worked input example, fitting the anchor for mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connection setup is a clear sequenced workflow with validation checkpoints (state checks, --wait polling, error field inspection, poll-again after user action), but it references an unlabeled "Step 2" and the generic action-running section lacks output/error validation, matching the anchor for a clear sequence with most checkpoints and minor gaps.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and tables and no external bundle files; at over 150 lines it exceeds the simple-skill threshold, so it lands at good structure with minor organization gaps rather than the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

66%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 clearly identifies a specific niche (Docsumo) and provides both a what and a when clause, but the actions are described with a single generic verb and the trigger phrasing lacks synonyms or richer natural-language coverage.

Suggestions

Replace the generic verb "Manage" with distinct concrete actions (e.g., "Upload, extract, review, and delete documents; manage workspaces, users, and roles").

Broaden the trigger clause with natural phrases users would say, e.g., "Use when the user wants to upload invoices, extract data, or manage Docsumo documents and workspaces."

Add a few synonyms/file-type terms relevant to Docsumo usage (invoices, bank statements, contracts) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete entities ("Documents, Workspaces, Users, Roles") but uses a single generic verb ("Manage") rather than multiple distinct concrete actions, matching the anchor that names the domain with limited actions.	3 / 5
Completeness	Both "what" (manage Documents, Workspaces, Users, Roles) and "when" ("Use when the user wants to interact with Docsumo data") are present and explicit, but the "when" clause is generic and could be more specific, matching the anchor for both present with an improvable when.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Docsumo data" surfaces the key natural term "Docsumo" but offers few keywords and no synonyms or variations, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The description names a specific application ("Docsumo integration") giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/docsumo/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.