Name: dronahq
Rating: 56.8 (1 reviews)
Author: membranedev

dronahq

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

Quality

65%

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

Quality

Content

68%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 a solid, actionable CLI integration guide with a well-validated connection workflow. Its main gaps are a missing verification step around running data-modifying actions and minor redundancy/organization issues.

Suggestions

Add an explicit verify step after `membrane action run` (e.g. inspect the `output` field and confirm the expected record change) to lift workflow_clarity past the destructive-operation cap.

Fix the 'Popular actions' section: either list actual popular DronaHQ actions or remove it, since it currently just repeats the discovery command.

Provide one fully worked action example with a real input schema and sample output so the action-run guidance is copy-paste complete.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven content with only minor trimmable prose (the opening product blurb, 'Use action names and parameters as needed', and the redundant 'Popular actions' section), fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides concrete copy-paste commands across install, auth, connect, discover, run, and proxy, but has minor gaps: placeholder IDs, a generic '{"key": "value"}' input example, and no worked end-to-end action example with real output.	4 / 5
Workflow Clarity	The connection flow has a clear state-machine with polling feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but running data-modifying actions lacks any validation/verification step, so the destructive/batch cap holds it at 3.	3 / 5
Progressive Disclosure	It is a single well-organized file with clear section headers and no bundle references to navigate; minor organization gaps (the misplaced 'Popular actions' section) keep it below a 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 is competent: it pairs a clear 'what' with an explicit 'Use when' trigger and leverages a distinct product name. Its weaknesses are generic, non-DronaHQ-specific actions and a narrow trigger phrase lacking synonyms.

Suggestions

Replace generic verbs with DronaHQ-specific capabilities (e.g. 'control sheets, queries, tables, and datasources') to raise specificity.

Broaden the trigger clause with natural variations, e.g. 'Use when the user wants to query, update, or automate DronaHQ records and datasources.'

Mirror the 'what' breadth in the 'when' so records/workflows are covered as triggers, not just 'DronaHQ data'.

Dimension	Reasoning	Score
Specificity	It names the DronaHQ domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than DronaHQ-specific (e.g. sheets, queries, datasources), so it is not comprehensive enough for a 4.	3 / 5
Completeness	It has a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' clause, so both are present; the 'when' is slightly narrow (only 'interact with DronaHQ data'), keeping it below the concrete multi-trigger 5.	4 / 5
Trigger Term Quality	'DronaHQ' is a natural keyword users would say, but the trigger phrase is narrow ('Use when the user wants to interact with DronaHQ data') and lacks synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	DronaHQ is a distinct named niche giving clear triggers, but the generic action verbs ('manage data, records, automate workflows') create minor overlap risk with other data/low-code skills, so it is mostly distinct rather than minimal-risk.	4 / 5
	Total	14 / 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/dronahq/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.