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

deploybot

DeployBot integration. Manage data, records, and automate workflows. Use when the user wants to interact with DeployBot data.

Quality

64%

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

Quality

Content

71%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 efficiently structured around concrete Membrane CLI commands, with a clear sequenced connection workflow. Its main weaknesses are the absence of external reference files and a dangling 'Step 2' pointer plus missing post-action validation.

Suggestions

Fix the dangling 'skip to Step 2' reference by labeling the destination section or removing the pointer.

Add an explicit validation/check step after running actions or proxy requests (e.g. inspect the `output`/`error` fields before proceeding) to support feedback loops for batch or destructive operations.

Move the proxy flag table and bulk action-listing details into a separate reference file and link to it one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight CLI command examples and a compact flag table, but the intro and best-practices prose contain minor over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready membrane commands cover install, auth, connection, action list/run, and proxy requests, with only a minor gap where the polling loop is described in prose rather than an executable command.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-checking checkpoints and branching next-actions, but the 'skip to Step 2' pointer has no matching labeled section and there is no validation step after running actions.	4 / 5
Progressive Disclosure	The body is well-sectioned but monolithic at ~143 lines with no bundle files or one-level-deep references; the action list and proxy flag table could live in separate reference files.	3 / 5
	Total	15 / 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 correctly identifies the DeployBot niche and includes a 'Use when' clause, but its capability list is generic ('manage data, records') rather than reflecting concrete DeployBot actions. Trigger phrases are thin and lack natural synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete DeployBot actions such as triggering deployments, managing environments and servers, and viewing deployment history.

Expand the 'Use when' clause with natural trigger phrases users actually say, e.g. deploying code, triggering a deployment, or managing DeployBot environments/servers.

Add file-extension or entity synonyms (deployments, deployment pipelines, notification groups) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the DeployBot domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete DeployBot operations like deployments or environments.	2 / 5
Completeness	It states both what the skill does and when to use it, but the 'when' clause is generic and could name concrete DeployBot-related triggers.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with DeployBot data' provides one relevant trigger phrase but misses natural variations users say such as deploy, deployment, or push to server.	3 / 5
Distinctiveness Conflict Risk	Tying the skill explicitly to DeployBot makes it mostly distinct from other skills, with only minor overlap risk against generic data-management skills.	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/deploybot/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.