Name: cdata-software
Rating: 56.8 (1 reviews)
Author: membranedev

cdata-software

CData Software integration. Manage data, records, and automate workflows. Use when the user wants to interact with CData Software 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/cdata-software/SKILL.md

Quality

Content

67%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 action-oriented and well-structured, with executable commands and a clear connect-to-run workflow including state feedback loops. Its weaknesses are moderate verbosity (padded intro, duplicated content) and a single-file structure that could offload some reference detail.

Suggestions

Remove the generic CData intro paragraph and the empty 'Connection / Table / Column / Query' overview bullets, and de-duplicate the action-list command between 'Searching for actions' and 'Popular actions'.

Fix the dangling 'Skip to Step 2' references by explicitly numbering the connect/search/run steps so the workflow path is unambiguous.

Consider moving the proxy flag table and the detailed clientAction field spec into a one-level-deep reference file (e.g., REFERENCE.md) to tighten the overview while keeping detail accessible.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes padding such as the generic intro paragraph on what CData is, the low-value 'Connection / Table / Column / Query' overview bullets, and a duplicated action-list command across 'Searching for actions' and 'Popular actions', matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the trimmed anchor 4.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (membrane connection ensure, action run, request) plus a full flag table covering common cases, fitting 'mostly executable guidance with minor gaps'; it is not a 5 because of unresolved placeholders (CONNECTION_ID) and slightly overlapping command examples.	4 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connect → poll until READY → search actions → run) with an explicit feedback loop on connection states (BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-polling guidance, matching 'clear sequence with most checkpoints'; it stops short of 5 due to the confusing unlabeled 'Skip to Step 2' references and no explicit validation of action results.	4 / 5
Progressive Disclosure	With no bundle files present, the single-file body is well-organized into clear sections (Overview, Working with, Authentication, Connecting, Searching, Popular actions, Best practices), fitting 'good structure; most content appropriately placed'; it is not a 5 because the proxy flag table and detailed clientAction spec could justify one-level-deep reference files to keep the overview leaner.	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 clear and distinct, with an explicit 'Use when' clause covering both what and when. Its main weakness is generic action verbs and limited trigger-term variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs ('Manage data, records') with concrete CData-specific actions (e.g., 'query connected data sources, list tables and columns, run SQL-like queries') to raise specificity.

Add natural trigger synonyms and entity terms users say (e.g., 'CData connector', 'CData drivers', 'query CData data') for better trigger-term coverage.

Tighten the 'Use when' clause with concrete trigger phrases (e.g., 'when the user mentions CData, connectors, or querying connected data sources').

Dimension	Reasoning	Score
Specificity	The description names the domain ('CData Software integration') and lists a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; it is not a 4 because the actions lack specificity and comprehensive coverage.	3 / 5
Completeness	It answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with CData Software data') with an explicit trigger clause, but the 'when' is somewhat generic so it falls short of the concrete, richly-triggered anchor 5.	4 / 5
Trigger Term Quality	It surfaces relevant terms ('CData Software', 'interact with CData Software data') but misses common variations, synonyms, or named entity types a user might say, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'CData Software' gives it a clear niche with low conflict risk, matching 'mostly distinct; minor overlap risk'; it is not a 5 because the action wording ('manage data, records, automate workflows') is broad enough to overlap with general data skills.	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/cdata-software/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.