Name: dromo
Rating: 62.4 (1 reviews)
Author: membranedev

dromo

Dromo integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Dromo data.

Quality

73%

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/dromo/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.

The content is highly actionable with executable CLI commands and a clear connection-state workflow, though it lacks validation safeguards around destructive actions and inlines reference-style bulk content rather than splitting it out.

Suggestions

Add an explicit validation/confirmation checkpoint before running destructive actions (e.g. verify the target ID and confirm with the user before delete-* actions).

Move the 14-row Popular actions table into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Trim the introductory paragraph's product-marketing framing ("Think of it as a low-code alternative...") to assume Claude's competence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, with command blocks and state tables carrying the content, but the intro ("Think of it as a low-code alternative...") and a few auth-plumbing explanations over-explain context Claude largely knows.	4 / 5
Actionability	It provides copy-paste-ready executable commands throughout (install, login, connection ensure, action list/run with JSON input, request proxy) plus a full actions table and proxy-flag table covering the common cases.	5 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with polling and a state-decision tree, but destructive actions (delete-upload, delete-headless-import, delete-import-schema) are listed with no validation checkpoint before execution, capping this dimension per the destructive/batch guideline.	3 / 5
Progressive Disclosure	The body is a well-organized single overview with clear section headers and no nested references, but the sizable inlined actions table and API-style material could live in a separate reference file, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

71%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 clear and distinctive, naming the Dromo domain and an explicit (if generic) 'Use when' clause. It is slightly held back by thin trigger-term coverage and a non-specific trigger phrase.

Suggestions

Add concrete trigger phrases and synonyms to the 'Use when' clause, e.g. 'Use when the user wants to manage Dromo imports, upload data, or import schemas.'

Replace the generic verb 'Manage' with specific operations (e.g. 'Create, list, update, and delete Dromo leads, deals, and import schemas').

Drop 'and more' or replace it with the remaining concrete entity types to avoid vague coverage signaling.

Dimension	Reasoning	Score
Specificity	Names the Dromo domain and lists several concrete entities ("Manage Leads, Persons, Organizations, Deals, Projects, Activities and more") rather than vague language, but the action verb is generic ("Manage") and "and more" signals incomplete coverage.	4 / 5
Completeness	It answers both what ("Manage Leads, Persons, Organizations, Deals, Projects, Activities...") and when ("Use when the user wants to interact with Dromo data"), but the 'when' clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Only a thin set of natural terms appears ("Dromo integration", "interact with Dromo data") with no synonyms, file extensions, or common user variations, matching the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Dromo is a specific named product, giving the skill a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/dromo/SKILL.md
Commit: f484c82

Reviewed: ~17 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.