Name: docupilot
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

docupilot

Docupilot integration. Manage Documents, Users, Workspaces. Use when the user wants to interact with Docupilot data.

Quality

63%

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

Quality

Content

61%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 actionable and well-structured with strong connection-handling guidance, but it carries a marketing intro and filler, and lacks validation/confirmation steps for the destructive actions it advertises.

Suggestions

Remove the marketing-style opening paragraph and the vague "Use action names and parameters as needed" line to tighten token efficiency.

Add a confirmation/validation checkpoint before running destructive actions like delete-template (e.g., verify the target template id and confirm with the user before executing).

Consider moving the popular-actions table and proxy flag reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with brief explanations, but the opening marketing paragraph ("document automation platform... businesses of all sizes") and filler like "When to use which actions: Use action names and parameters as needed." are unnecessary padding.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxying, with concrete flag tables; minor gaps remain around placeholders like "QUERY" in the intent example and CONNECTION_ID substitution.	4 / 5
Workflow Clarity	The connection workflow has explicit state handling and polling feedback loops, but the destructive operations it exposes (delete-template) are run via a generic `action run` with no validation or confirmation checkpoint, capping it at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well organized into clear sections (install, auth, connecting, searching, popular actions, proxy, best practices); the popular-actions and proxy-flag tables could be split into reference files but the current structure navigates well.	4 / 5
	Total	14 / 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 answers both what and when and is anchored to a distinct named app, but its actions are generic ("Manage") and its trigger terms rely on a single proper noun without synonyms or variations.

Suggestions

Replace the generic verb "Manage" with concrete actions the skill performs (e.g., create/generate/list/delete documents and templates).

Expand the trigger clause with natural user phrasings such as "when the user mentions Docupilot, document generation, or template merges".

Add file/term synonyms (e.g., .docx, templates, proposals) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Docupilot) and three resource areas ("Manage Documents, Users, Workspaces"), but the single generic verb "Manage" is not a set of distinct concrete actions, so coverage is non-comprehensive.	3 / 5
Completeness	It states a clear 'what' (manage Documents, Users, Workspaces) and an explicit 'when' ("Use when the user wants to interact with Docupilot data"), but the trigger phrasing is generic rather than concrete, keeping it below 5.	4 / 5
Trigger Term Quality	The only meaningful keyword is the proper noun "Docupilot" in "Use when the user wants to interact with Docupilot data"; common variations or synonyms a user might say are absent.	3 / 5
Distinctiveness Conflict Risk	"Docupilot integration" targets a specific named application, giving it a clear niche with distinct triggers and minimal risk of firing for unrelated 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/docupilot/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.