Name: droxy
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

droxy

Droxy integration. Manage Organizations. Use when the user wants to interact with Droxy data.

Quality

70%

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

Quality

Content

82%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 and well-sequenced, with executable commands and a real feedback loop in the connection workflow. Its main weaknesses are minor verbosity, an inlined bulk actions table that could be split out, and no validation guidance around the destructive actions it lists.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, command-focused code blocks and a compact actions table with little padding. Minor over-explanation remains (the auth-plumbing sentence, the purposeless Overview entity list, and the filler "Use action names and parameters as needed."). Not a 5 because of these trims; not a 3 because it is genuinely efficient.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (login, connection ensure, action list/run, request) with flags, --json output, and a popular-actions table supplying real keys. Specific examples cover the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit checkpoints and a poll-until-ready feedback loop branching on READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR. Minor validation gap: destructive actions (delete-resource, delete-chatbot) are listed without a validate-before-run checkpoint.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and no nested references, but no bundle files exist and the 15-row Popular actions table is bulk reference-style content inlined in SKILL.md. Good structure with a minor organization gap, so above the midpoint but short of 5.	4 / 5
	Total	17 / 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 states a clear niche and includes an explicit Use-when trigger, but its capability list is thin and generic ("Manage Organizations") and it omits the natural trigger terms a user would actually say. It is functional but under-specific.

Suggestions

Replace "Manage Organizations" with concrete enumerated actions drawn from the body (e.g. manage chatbots, create resources from YouTube/website/text, retrieve leads and conversations).

Add natural trigger terms users would say, such as "advertising campaigns", "chatbot leads", or "Droxy resources", not just the brand name.

Tighten the "what" to match the body's actual capabilities so completeness and specificity both reach 5.

Dimension	Reasoning	Score
Specificity	"Droxy integration" and "Manage Organizations" name the domain and one entity but provide minimal, generic actions rather than enumerated concrete capabilities (the body actually lists chatbots, resources, leads, conversations). Not a 1 because a concrete entity is named; not a 3 because there are no real action verbs enumerated.	2 / 5
Completeness	Both a weak "what" ("Manage Organizations") and an explicit "when" ("Use when the user wants to interact with Droxy data") are present. The explicit Use-when clause rules out the cap at 3, but the thin "what" keeps it below 5.	4 / 5
Trigger Term Quality	"Droxy" plus an explicit "Use when the user wants to interact with Droxy data" trigger gives some relevant keywords, but common natural synonyms a user would say (ad campaigns, advertising, leads, chatbots) are missing. Better than 2 due to the explicit Use-when trigger; short of 4 for thin keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Droxy" is a distinct brand niche with a clear, low-conflict trigger. Not a 5 because the trigger phrasing ("interact with Droxy data") is generic within that niche rather than concrete; clearly above the midpoint due to strong brand distinctiveness.	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/droxy/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.