Name: dronedeploy
Rating: 52.8 (1 reviews)
Author: membranedev

dronedeploy

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

61%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 well-structured, actionable guide to the Membrane CLI integration with concrete commands and a useful connection-state feedback loop, but it carries some padded prose, a broken step reference, and lacks validation guidance for destructive proxy operations.

Suggestions

Add a verification checkpoint for destructive proxy requests (e.g. confirm before `-X DELETE`, check the response status/body before proceeding) to lift workflow_clarity above the destructive-operations cap.

Fix the dangling 'skip to Step 2' references by adding explicit numbered Step 1 / Step 2 headers so the connection workflow is unambiguous.

Trim the introductory background paragraph and filler sentences ('so you can focus on the integration logic...', 'This is the fastest way...') to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient operational CLI commands, but the opening background paragraph ('DroneDeploy is a cloud-based drone mapping and analytics platform...') and filler phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') could be trimmed, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests plus a full flags table, with only minor gaps (placeholder CONNECTION_ID/actionId and the circular 'Popular actions' discovery note) keeping it just below fully executable 5-anchor coverage.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence exists with a poll/re-poll feedback loop for connection state, but the prose references a 'Step 2' that is never labeled and the proxy path offers no verification before destructive HTTP methods (DELETE/PUT), so the destructive-operations cap and missing checkpoints hold it at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the body is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); the substantial connection state-machine and flags table are inline rather than split to a reference, a minor organization gap rather than a structural problem.	4 / 5
	Total	14 / 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 includes both a what-statement and an explicit Use-when trigger tied to a distinct named app, but its capability language is generic and its trigger phrasing lacks the concrete synonyms users would naturally say.

Suggestions

Replace generic verbs with concrete DroneDeploy capabilities, e.g. 'Create maps and 3D models, upload drone imagery, run volume measurements, and generate reports'.

Expand the Use-when clause with natural trigger phrases users actually say: 'Use when the user wants to work with DroneDeploy maps, drone imagery, flight plans, or aerial data.'

Drop buzzword padding ('automate workflows') in favor of specific actions to raise specificity and trigger-term quality.

Dimension	Reasoning	Score
Specificity	It names the domain ('DroneDeploy integration') but the listed actions 'Manage data, records, and automate workflows' are generic buzzwords rather than concrete capabilities (e.g. create maps, upload imagery, generate reports), matching the 'names domain but actions minimal/generic' anchor and falling short of the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It states what the skill does ('Manage data, records, and automate workflows') and includes an explicit 'Use when the user wants to interact with DroneDeploy data' trigger, but the when-clause is generic rather than listing concrete trigger phrases, so it lands at 'has both what and when; when could be more specific' instead of a 5.	4 / 5
Trigger Term Quality	It includes some relevant keywords ('DroneDeploy', 'data', 'records') but misses common natural variations and synonyms a user would say (drone, maps, aerial data, flight plans, 3D models), fitting 'some relevant keywords but missing common variations' rather than the sparse 2-anchor.	3 / 5
Distinctiveness Conflict Risk	The named DroneDeploy app gives it a clear, distinct niche with low conflict risk, but the generic action wording ('interact with DroneDeploy data') keeps it from the sharply distinct triggers of a 5.	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/dronedeploy/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.