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

qualetics

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

A practical, command-rich integration skill with good actionability and a genuinely useful connection-state workflow. It is held back by a marketing-flavored intro, broken step numbering, and a missing verification step for action results.

Suggestions

Remove the marketing description of what Qualetics is and the "focus on integration logic rather than auth plumbing" flourish to tighten the intro.

Fix the workflow numbering: label the connection step as "Step 1" with a "1a / 1b" split (or drop the sub-numbering) and explicitly label "Step 2" where actions are searched and run.

Add a verification checkpoint after running actions (e.g. inspect the `output` field for errors/status before reporting success) to close the feedback loop on data operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven prose, but the opening marketing line ("Qualetics is a SaaS platform that helps businesses improve performance through data analytics and AI-powered insights...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-pasteable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flags table for proxying, with only minor gaps such as unresolved placeholders (CONNECTION_ID, actionId) and no concrete input example beyond a generic key/value object.	4 / 5
Workflow Clarity	A connect-then-act sequence exists with real validation checkpoints (polling connection state, handling CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but step numbering is incoherent — it references "Step 2" without a labeled Step 2 and has a "1b" with no "1a" — and there is no validation/verification feedback loop on action results.	3 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-sectioned file (Overview, Working with Qualetics, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with clear headers; it is appropriately organized but, at ~150 lines and with no one-level-deep references, it cannot reach the top anchor.	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.

A competent description with third-person voice, an explicit "Use when" trigger, and a named-app niche. It is held back by generic action verbs and a single, broad trigger phrase rather than a rich set of natural trigger terms.

Suggestions

Replace generic verbs with concrete Qualetics operations (e.g. "query dashboards, manage data sources, run and deploy models, review audit logs") to lift specificity.

Expand the trigger clause with natural phrases users actually say (e.g. "Use when the user wants to query Qualetics dashboards, manage data sources or models, or review audit logs").

Add file-format or entity keywords (dashboards, reports, data sources, models) so trigger coverage includes common synonyms.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Qualetics domain plus 2-3 actions, but the actions are generic (manage, automate) rather than concrete operations, matching the anchor for naming a domain with limited concrete actions.	3 / 5
Completeness	It has both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Qualetics data"), but the when-clause is a single generic trigger rather than multiple concrete trigger phrases, so it is not the top anchor.	4 / 5
Trigger Term Quality	"Qualetics data", "records", and "workflows" are relevant keywords, but coverage is thin — missing natural synonyms or variations a user would say (e.g. analyze, pull, sync, dashboards), so it sits at some-relevant-keywords rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	Explicitly naming "Qualetics" gives it a clear niche with minimal conflict risk, but the surrounding action words (data, records, workflows) are generic enough to create minor overlap with other data/analytics 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/qualetics/SKILL.md
Commit: f484c82

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