Name: docsbot-ai
Rating: 64.8 (1 reviews)
Author: membranedev

docsbot-ai

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

Quality

77%

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

Quality

Content

76%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 highly actionable CLI integration guide with concrete commands, clear connection-state handling, and good organization. Its main gaps are the missing destructive-action validation (capping workflow clarity) and a large inlined action table that could be split out.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive operations, e.g. require a user confirmation or dry-run before running delete-bot, delete-conversation, delete-source, or delete-question.

Fix the dangling "Step 2" reference in the Connecting section by labeling the subsequent step (e.g. "Step 2 — Search for actions") so the workflow is unambiguous.

Consider moving the full popular-actions table to a references/ file (e.g. ACTIONS.md) and keeping only the top few examples inline to improve token efficiency and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, flags, and tables, with only minor over-explanation (e.g. "This is the fastest way to get a connection", "so you can focus on the integration logic rather than auth plumbing"), matching the 4 anchor rather than fully lean 5.	4 / 5
Actionability	It provides copy-paste-ready commands with real flags and JSON examples across install, login, connection ensure/get, action list/run, and proxy, covering the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	The connection workflow is sequenced with a poll-until-ready feedback loop, but the skill lists destructive actions (Delete Bot, Delete Conversation, Delete Source, Delete Question) with no validation or confirmation guidance, capping workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers and no nested references; the 20-row popular-actions table is arguably inlined reference content that could live in a separate file, placing it at 4 rather than 5.	4 / 5
	Total	16 / 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, third-person description that names the DocsBot AI niche and its core resources and includes an explicit Use-when clause. It is strong on distinctiveness but could be more specific about concrete actions and richer in natural trigger synonyms.

Suggestions

Replace the generic verb "Manage" with concrete actions per resource, e.g. "Create, list, update, and delete Documents, ChatSessions, Users, and Workspaces."

Expand the trigger clause with natural phrasings users actually say, e.g. "Use when the user wants to chat with a DocsBot, search its documentation, or manage DocsBot bots, teams, sources, and conversations."

Include the file/endpoint or entity synonyms (bots, teams, sources, conversations) so the description surfaces more of the actions listed in the body.

Dimension	Reasoning	Score
Specificity	"Manage Documents, ChatSessions, Users, Workspaces" names several concrete resources under a single verb, listing multiple specific capabilities but without distinct per-resource actions (create/delete/list), so it sits at 4 rather than 5.	4 / 5
Completeness	It states both what ("DocsBot AI integration. Manage Documents, ChatSessions, Users, Workspaces") and when ("Use when the user wants to interact with DocsBot AI data"), but the trigger clause is generic rather than listing concrete trigger phrases, fitting the 4 anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with DocsBot AI data" plus the named entities give good keyword coverage, though common natural variations (e.g. "chat with bot", "search docs") are missing, matching the 4 anchor.	4 / 5
Distinctiveness Conflict Risk	Naming the specific app "DocsBot AI" gives a clear niche with distinct triggers and minimal overlap with other skills, matching the 5 anchor.	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/docsbot-ai/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.