Name: docugenerate
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

docugenerate

DocuGenerate integration. Manage Documents, Templates. Use when the user wants to interact with DocuGenerate data.

Quality

57%

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

Quality

Content

57%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 Membrane CLI commands and a clear connection workflow, but it is held back by some padding prose, missing safeguards around destructive actions, and a monolithic single-file structure. Splitting reference material and adding validation for destructive operations would raise the lower dimensions.

Suggestions

Add a validation/confirmation checkpoint before running destructive actions (e.g., require the document/template ID to be fetched and confirmed before delete-document/delete-template).

Move the popular-actions table and proxy flag reference into separate reference files linked from SKILL.md to improve progressive disclosure.

Trim explanatory prose (e.g., the audience description and the 'focus on the integration logic' aside) that does not add executable value.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes unnecessary prose like "It's used by software developers and technical writers to streamline the documentation process" and "so you can focus on the integration logic rather than auth plumbing", fitting 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete executable commands (membrane login, connection ensure, action list/run, request) and a populated actions table provide copy-paste-ready guidance, with only minor gaps such as unresolved CONNECTION_ID placeholders, matching 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection flow is sequenced with state-checking feedback (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the skill exposes destructive operations (delete-document, delete-template) with a generic run command and no validation or confirmation step, triggering the destructive-operations cap at 3.	3 / 5
Progressive Disclosure	The single-file body (~145 lines) has clear section headers but inlines content that could live in separate references (the actions table, proxy flag reference) and provides no one-level-deep file links, matching 'Some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	13 / 20 Passed

Description

57%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 answers both what and when with a distinct product-specific trigger, but its action verbs are generic and its trigger-term coverage lacks synonyms. Tightening "Manage" into concrete actions and adding natural variations would lift the weaker dimensions.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g., 'Generate documents from templates, list, get, update, and delete documents and templates').

Broaden trigger terms with natural synonyms and file/extension cues users would actually say (e.g., 'document generation', 'template rendering', 'DocuGenerate API').

Make the 'Use when' clause more specific about scenarios (e.g., 'Use when the user wants to generate or manage DocuGenerate documents and templates via the Membrane CLI').

Dimension	Reasoning	Score
Specificity	Quotes "Manage Documents, Templates" name the domain and two entities but the action verb "Manage" is generic, matching the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires concrete actions like 'extracts content'.	2 / 5
Completeness	"DocuGenerate integration. Manage Documents, Templates" states the what and "Use when the user wants to interact with DocuGenerate data" states the when, but the when could be more specific, matching 'Has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	"Documents", "Templates", and "DocuGenerate data" provide some relevant keywords but lack common variations or synonyms, fitting 'Some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The DocuGenerate-specific trigger creates a clear niche with minimal overlap risk, though the generic "Manage Documents, Templates" phrasing keeps it just short of the 5-anchor's distinct trigger phrases.	4 / 5
	Total	13 / 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/docugenerate/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.