Name: azuqua
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

azuqua

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

Quality

67%

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/azuqua/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 well-structured with concrete, executable Membrane commands and a clear connection-state workflow, but it over-explains Azuqua basics and lacks validation guidance for destructive proxy/action operations. Trimming the intro and adding verification steps for destructive calls would raise the score.

Suggestions

Add a validation/checkpoint step before destructive operations (e.g., 'Before running DELETE/PUT/PATCH via `membrane request` or `action run`, confirm the target and dry-run a GET first').

Trim the opening overview paragraph and the bare 'Azuqua Overview' bullet list, which restate concepts Claude already knows.

Fix or remove the 'Official docs' link (it points to help.workato.com, a different product) and reference genuine Azuqua documentation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but the intro paragraph ('Azuqua is a no-code, cloud-based platform...') and the thin 'Azuqua Overview' bullet list explain or pad concepts Claude already knows, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the cleaner 4.	3 / 5
Actionability	Provides concrete, executable commands (install, login, connection ensure, action list/run, request) with a flag table, but relies on placeholders like CONNECTION_ID and a literal 'QUERY' intent, leaving minor gaps that fit 'mostly executable guidance; concrete code or commands with minor gaps' short of fully copy-paste-ready.	4 / 5
Workflow Clarity	The connect-to-run sequence is clear with a state machine and feedback loops for connection readiness, but running actions and proxy requests support destructive HTTP methods (DELETE/PUT/PATCH) with no validation or verification guidance, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with clear headers and no nested references; no bundle files exist so there is no nesting risk, but the proxy flag table and clientAction details are inlined and the 'Official docs' link points to workato.com rather than Azuqua, leaving minor organization gaps that fit 'good structure; most content appropriately placed; minor gaps' rather than a 5.	4 / 5
	Total	14 / 20 Passed

Description

73%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 clearly identifies a distinct Azuqua niche and includes an explicit 'Use when' trigger, but its action list is generic and the trigger phrase is narrow. Tightening the 'when' clause and listing more concrete capabilities would push it toward a top score.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Azuqua capabilities (e.g., 'create and monitor Flows, configure Connectors, read and write Datastores').

Broaden the trigger clause to cover the main use cases, e.g., 'Use when the user wants to build or automate Azuqua Flows, manage Connectors, or read/write Datastore records.'

Add natural synonyms users might say ('Azuqua flows', 'Azuqua connectors', 'Azuqua automation') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azuqua integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than comprehensive, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	Provides a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Azuqua data'), but the 'when' is narrow and does not enumerate multiple concrete trigger phrases, so it falls short of the 5 anchor.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('Azuqua', 'data', 'records', 'automate workflows', 'integration') with an explicit trigger clause; a few natural synonyms are missing, fitting 'good keyword coverage; a few natural terms missing' rather than the fuller coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	Anchored to a specific named SaaS product ('Azuqua integration') with a trigger that requires Azuqua, giving a clear niche with minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.	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/azuqua/SKILL.md
Commit: f484c82

Reviewed: 4 minutes 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.