Name: superdocu
Rating: 66.4 (1 reviews)
Author: membranedev

superdocu

Superdocu integration. Manage Documents, Users, Groups, Templates. Use when the user wants to interact with Superdocu data.

Quality

80%

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

Quality

Content

82%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.

A strongly actionable integration skill built around concrete, copy-paste-ready Membrane CLI commands with a well-handled connection-state feedback loop. Its main weaknesses are minor over-explanation in the intro and a broken 'Step 1/Step 2' numbering scheme that slightly muddies the workflow.

Suggestions

Fix the dangling step references: define explicit 'Step 1' (ensure connection) and 'Step 2' (search/run actions) headers so the 'skip to Step 2' cues resolve.

Trim the marketing intro ('It helps businesses organize, store, and share... used by companies of all sizes...') to a one-line factual description of what Superdocu is.

Add a brief verification note after `membrane action run` / `membrane request` (e.g. check the `output`/error fields and confirm state) since proxy requests can be destructive (DELETE/PUT).

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and brief flag tables with little padding, but the opening marketing prose ('used by companies of all sizes looking to streamline their document workflows') and phrases like 'rather than auth plumbing' could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) with concrete flags, a full options table, and JSON-input examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with an explicit feedback loop (polling BUILDING -> READY / CLIENT_ACTION_REQUIRED / error states), but the dangling 'skip to Step 2' references and absent 'Step 1'/'Step 2' headers leave minor navigation gaps, and running/proxying actions lacks result verification.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline in a single, well-sectioned file (Overview, Authentication, Connecting, Searching, Actions, Best practices); structure is good, though at ~140 lines some reference material (proxy flags, action discovery) could arguably live in a separate file.	4 / 5
	Total	17 / 20 Passed

Description

78%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.

A concise, well-structured description that names the product, enumerates its core objects, and includes an explicit 'Use when' trigger. It is distinct and low-conflict, with only minor gaps in action specificity and trigger-phrase concreteness.

Dimension	Reasoning	Score
Specificity	Lists four concrete domain objects ('Manage Documents, Users, Groups, Templates') giving comprehensive coverage of the Superdocu domain, though the single verb 'Manage' is generic rather than enumerating distinct actions.	4 / 5
Completeness	Answers both 'what' ('Superdocu integration. Manage Documents, Users, Groups, Templates.') and 'when' ('Use when the user wants to interact with Superdocu data.'), but the 'when' clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural product and object keywords ('Superdocu', 'Documents', 'Users', 'Groups', 'Templates') plus the trigger phrase 'interact with Superdocu data', but misses common synonyms or file extensions a user might say.	4 / 5
Distinctiveness Conflict Risk	Names a specific product ('Superdocu integration') with a distinct trigger ('interact with Superdocu data'), giving it a clear niche with minimal risk of firing for an unrelated skill.	5 / 5
	Total	17 / 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/superdocu/SKILL.md
Commit: f484c82

Reviewed: 9 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.