Name: dataddo
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

dataddo

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

Quality

61%

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/dataddo/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 highly actionable with concrete Membrane CLI commands and a solid connection-state feedback loop, but it loses conciseness to a marketing-style intro and lacks validation checkpoints for destructive action/proxy operations. It is well-structured for a single-file skill though no reference files are used.

Suggestions

Cut the opening "Dataddo is a no-code data integration platform... used by data analysts, marketers..." paragraph, which explains background Claude already knows.

Add a verification step after `membrane action run` and after proxy requests (e.g. check the response status/error field and retry or surface failures) to support destructive operations.

Consider moving the proxy flags table and clientAction field reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening marketing paragraph ("no-code data integration platform... used by data analysts, marketers...") and explanatory prose like "This is the fastest way to get a connection" add unnecessary context Claude does not need, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action run with --input JSON, proxy flags table), matching the mostly-executable anchor; minor gaps are the unsubstituted placeholders (CONNECTION_ID, QUERY) and the duplicated search command in "Popular actions".	4 / 5
Workflow Clarity	The connection flow has a clear poll/feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll), but running actions and proxy requests (which support destructive DELETE/PUT methods) lack validation or verification checkpoints, so per the destructive-operations cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	It is a single, well-organized file with clear section headers (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) and no nested references, fitting the good-structure anchor; it scores below 5 only because no content is split into reference files and some inline detail (e.g. clientAction sub-fields, proxy flag table) could live separately.	4 / 5
	Total	14 / 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 answers both what and when with an explicit trigger and a distinct product name, but its capability phrasing is generic rather than concrete. Tightening "Manage data, records, and automate workflows" into specific Dataddo operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage", "automate") with concrete Dataddo operations, e.g. "Create and manage Sources, Flows, Schedules, and Destinations in Dataddo".

Add natural trigger synonyms users say, e.g. "Use when the user wants to create Dataddo flows, manage sources/destinations, or schedule data pipelines".

Mention key Dataddo objects (sources, destinations, flows, schedules) in the description to improve keyword coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Dataddo domain and a few actions, but the actions are generic ("manage", "automate") rather than concrete operations, fitting the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Dataddo data"), but the what is generic enough that it does not reach the concrete-trigger-phrases anchor of 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Dataddo data" surfaces relevant keywords ("Dataddo", "data") but misses common variations and synonyms a user might naturally say, matching the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Dataddo" gives a clear niche and distinct trigger with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing keeps minor overlap risk, fitting the mostly-distinct anchor.	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/dataddo/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.