Name: cloudquery
Rating: 61.6 (1 reviews)
Author: membranedev

cloudquery

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

Quality

Content

88%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 executable commands, a well-sequenced connection workflow including validation checkpoints and error-recovery feedback loops, and clear section structure. The main weakness is a few marketing-flavored asides that slightly inflate token usage.

Suggestions

Trim opinion/marketing asides (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', 'burn less tokens') to improve token efficiency.

Consider moving the proxy flag options table to a short reference and keeping only the one or two most-used examples inline, reducing body length.

Add a brief validation note after `membrane action run` (e.g. inspect the `output` field for errors) to extend the feedback-loop discipline beyond the connection step.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with copy-paste commands and minimal concept explanation, but includes a few padded/marketing phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', 'burn less tokens') that could be trimmed, matching 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides fully executable commands throughout (install, login, connection ensure, action list/run with JSON input, proxy requests) covering the common cases copy-paste ready, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection workflow is explicitly sequenced with a state machine and validation checkpoints (READY skip to step 2; BUILDING poll; CLIENT_ACTION_REQUIRED act then re-poll; CONFIGURATION_ERROR/SETUP_FAILED check error), providing clear feedback loops for error recovery, matching the top anchor.	5 / 5
Progressive Disclosure	The skill is self-contained with clear section headers and no nested references, but at ~140 lines inlines substantial material (the full proxy flag table and state-machine explanation) that could be split out, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	18 / 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 is concise, third-person, and includes an explicit Use-when trigger, giving it solid completeness and distinctiveness. It is weakened by generic capability phrasing and thin natural-language trigger terms that would better match how users actually request CloudQuery work.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete CloudQuery actions such as 'query cloud assets via SQL, run policy packs, and schedule syncs'.

Expand the trigger clause with natural phrasings users say, e.g. 'Use when the user wants to query cloud resources, run security policies, or inventory cloud infrastructure with CloudQuery'.

Add file-format or product synonyms (cloud asset inventory, SQL, policy packs) so the description surfaces for a wider range of natural requests.

Dimension	Reasoning	Score
Specificity	It names the Cloudquery domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete CloudQuery capabilities like querying cloud assets or running policy packs, fitting the 'names domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It has both a 'what' (Cloudquery integration, manage data/records/workflows) and an explicit 'when' clause ('Use when the user wants to interact with Cloudquery data'), though the when-scope could be more specific, fitting the 'both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The only natural keyword present is 'Cloudquery data'; common variations users would say (cloud asset inventory, SQL, cloud resources, security, infrastructure) are absent, matching 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The branded 'Cloudquery integration' framing gives it a clear niche with minimal conflict risk, while the broad 'manage data, records, automate workflows' phrasing leaves only minor overlap, matching 'mostly distinct; minor overlap risk with closely related skills'.	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/cloudquery/SKILL.md
Commit: f484c82

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