Name: wavemaker
Rating: 56.8 (1 reviews)
Author: membranedev

wavemaker

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wavemaker/SKILL.md

Quality

Content

68%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 actionable and well-structured with strong executable CLI examples, but it carries a padded concept taxonomy and lacks validation checkpoints for operations that can mutate external WaveMaker data. It is a competent integration guide rather than a lean, failure-safe one.

Suggestions

Add explicit verification/validation steps after running actions or proxy requests (e.g., check the response `output`/`error` fields and confirm the intended state changed) to satisfy the destructive/batch workflow cap.

Trim or move the 35-item WaveMaker concept bullet list and the introductory platform description, which add tokens without actionable value.

Resolve the CONNECTION_ID placeholder flow inline (show how the id is obtained from `connection ensure --json` and passed forward) so the commands are end-to-end executable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with direct, copy-pasteable CLI commands, but the ~35-item WaveMaker concept taxonomy and the "WaveMaker is a low-code platform..." intro explain context Claude does not need, matching the anchor for efficient content with minor instances of over-explanation.	4 / 5
Actionability	Concrete executable commands dominate (install, login, connection ensure/get, action list/run, request) with specific flags and JSON examples; minor gaps remain such as unresolved CONNECTION_ID placeholders and the vague directive "Use action names and parameters as needed," fitting the mostly-executable anchor.	4 / 5
Workflow Clarity	A clear install → authenticate → connect → search → run sequence exists with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running actions, automating workflows, and proxy requests can mutate external data and there are no validation or verification checkpoints, so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), so the single-file body relies on well-organized sections and an external docs link for navigation; structure is good, but the large inline concept taxonomy is not offloaded and there are no one-level-deep detail references, so it is not a 5.	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 third-person, concise, and includes both a 'what' and a 'Use when' clause, but its actions are generic verbs and its trigger terms lack synonyms or concrete user phrases. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete WaveMaker-specific actions (e.g., 'create and deploy WaveMaker apps, manage project pages and variables, trigger backend services').

Expand trigger terms beyond 'WaveMaker data' to natural phrases users say, such as 'build a WaveMaker app', 'deploy a WaveMaker project', or 'connect to a WaveMaker service'.

Make the 'Use when' clause name concrete triggering situations rather than restating the domain.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the WaveMaker domain plus a few actions, but the verbs are generic ("manage", "automate") rather than concrete operations, matching the anchor that names the domain with 1-2 actions but is not comprehensive.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with WaveMaker data"), but the trigger clause is somewhat circular and could be more explicit, matching the anchor for both present with a less-specific 'when'.	4 / 5
Trigger Term Quality	The only natural keyword is "WaveMaker" ("interact with WaveMaker data"), with no synonyms, task variants, or file types a user would actually say, fitting the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	"WaveMaker integration" names a distinct product niche with clear triggers, giving mostly distinct coverage with only minor overlap risk against generic data-management skills; it is not a 5 because the trigger phrasing is generic within that niche.	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/wavemaker/SKILL.md
Commit: f484c82

Reviewed: 3 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.