Name: document360
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

document360

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/document360/SKILL.md

Quality

Content

63%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 CLI commands and a clear connection workflow including state-driven feedback loops. Its weaknesses are token-heavy overview/entity content that could be trimmed and the lack of any progressive disclosure into separate reference files.

Suggestions

Trim the product-explainer intro and move the 28-item entity list and Popular actions table into a separate `references/` file, keeping only the core install/auth/connect/run workflow inline in SKILL.md.

Fix the "skip to Step 2" navigation by explicitly labeling the searching/running-actions section as Step 2, or remove the dangling cross-reference.

Remove or correct the "Search Drive" row in the Popular actions table, which appears to be a Google Drive action that does not belong to a Document360 skill.

Dimension	Reasoning	Score
Conciseness	The intro explains what Document360 is ("Think of it as a help center builder with advanced features...") and a ~28-item entity bullet list is token-heavy; the command sections are efficient but the overview and entity list could be tightened. It is mostly efficient with some unnecessary padding, matching the 3 anchor better than the lean 5.	3 / 5
Actionability	Provides many copy-paste ready `membrane` commands (install, login, connection ensure, action list/run, request with flag table) covering common cases; minor gaps and an accuracy nit (a "Search Drive" row that looks like a Google Drive action) keep it just below 5.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state-machine feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED and re-poll after user action); a navigation hiccup — "skip to Step 2" with no labeled Step 2 — is a minor checkpoint gap that prevents a 5.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in one ~180-line file with decent section headers; bulk reference material (the 28-item entity list and the Popular actions table) that would fit better in separate reference files is inlined, matching the 3 anchor rather than the cleanly split 5.	3 / 5
	Total	14 / 20 Passed

Description

73%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 names the product and includes both a what and an explicit Use-when trigger, with strong distinctiveness from the specific Document360 niche. It is held back from the top tier by the generic "Manage" verb and a slightly broad trigger clause.

Suggestions

Replace the generic verb "Manage" with specific concrete actions, e.g. "Create and update Projects, Users, and Roles; list and publish articles; manage categories and team accounts."

Tighten the trigger clause with concrete user phrases, e.g. "Use when the user wants to manage Document360 knowledge base articles, categories, projects, or team/reader accounts."

Add natural synonym coverage (e.g. "knowledge base", "help center", "docs") so the description matches more varied user phrasings.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Projects, Users, Roles" — names the Document360 domain and a few concrete objects, but the verb "Manage" is generic rather than enumerating distinct specific actions; not comprehensive enough for a 4.	3 / 5
Completeness	Provides both a "what" ("Document360 integration. Manage Projects, Users, Roles.") and an explicit "when" ("Use when the user wants to interact with Document360 data"); the "when" is slightly generic rather than concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	Contains the natural product name "Document360" and an explicit trigger clause ("Use when the user wants to interact with Document360 data"), but lacks synonyms or file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	"Document360 integration" targets a specific named product niche with a distinct trigger ("interact with Document360 data"), yielding minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/document360/SKILL.md
Commit: f484c82

Reviewed: ~18 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.