Name: hasdata
Rating: 59.2 (1 reviews)
Author: membranedev

hasdata

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

Quality

69%

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/hasdata/SKILL.md

Quality

Content

76%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 highly actionable, with copy-paste-ready CLI commands and a clear connection workflow including state feedback loops. Its main weakness is the absence of validation/verification checkpoints before destructive proxy or mutation operations, which caps workflow clarity.

Suggestions

Add a verification checkpoint before destructive proxy calls and mutating action runs, e.g. 'For -X DELETE/PUT/PATCH or actions that modify records, confirm the target id with the user and re-read the result output before proceeding' to lift workflow_clarity above 3.

De-duplicate the `membrane action list` instructions (which appear in both 'Searching for actions' and 'Popular actions') into a single canonical block to improve conciseness and organization.

Trim non-essential asides ('so you can focus on the integration logic rather than auth plumbing') and either make the 'Hasdata Overview' entity bullet list actionable or remove it, since it currently adds tokens without executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is command-driven and mostly tight (auth, connect, search, run, proxy all given as copy-paste commands), but has minor padding: 'so you can focus on the integration logic rather than auth plumbing', the informational 'Hasdata Overview' entity bullet list, and the `action list` command repeated across 'Searching for actions' and 'Popular actions'. Not a 5 because these trimmable tokens don't all earn their place; not a 3 because the core is efficient and assumes Claude's competence.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands with --json flags covering the common cases: install, login (including headless completion), connection ensure/get --wait, action list/run with --input, and a complete proxy flag table. Examples cover the realistic workflow end to end.	5 / 5
Workflow Clarity	The connection sub-flow is well sequenced with state feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, check error on CONFIGURATION_ERROR/SETUP_FAILED). However the proxy section enables destructive methods (DELETE/PUT/PATCH) and `action run` can mutate data, with no validation/verification checkpoint before such operations, so the destructive-operations cap holds it at 3.	3 / 5
Progressive Disclosure	Single-file body with no bundle files and no external references, organized into clear headed sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices). Good structure with only minor organization gaps (the redundant action-list sections). Not a 5 because no one-level-deep references are signaled and the >50-line length isn't justified by progressive disclosure.	4 / 5
	Total	16 / 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 functional and correctly structured with an explicit 'Use when...' trigger and brand-anchored distinctiveness, but its action vocabulary is generic. Strengthening it with concrete Hasdata-specific capabilities would raise specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete Hasdata capabilities, e.g. 'Append missing customer data, validate data accuracy, and enrich records against Hasdata datasets' to lift specificity from 3 to 4-5.

Expand the trigger clause with natural synonyms users actually say, e.g. 'Use when the user wants to enrich, clean, validate, or append customer data, or interact with Hasdata datasets and API keys.'

Mirror the domain vocabulary from the body (Dataset, Schema, Data Quality Check, Data Governance Rule) into the description so triggers align with how the platform is described.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain and 2-3 actions, but the verbs are generic ('Manage data, records') rather than concrete like 'append missing information' or 'validate data accuracy' seen in the body. Not a 4 because the actions lack the specificity of the 'Lists several specific actions' anchor.	3 / 5
Completeness	Explicitly answers both: what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Hasdata data'). Not a 5 because the 'when' clause is a single brand-tied trigger without the concrete synonym-rich trigger phrases of the 5 anchor.	4 / 5
Trigger Term Quality	'Hasdata' is a strong distinctive brand keyword and 'data, records, workflows' are reasonably natural, but coverage misses common synonyms and variations a user might say (e.g., 'enrich', 'append', 'customer data', 'clean data'). Falls at the 'some relevant keywords but missing common variations' anchor rather than the 'good keyword coverage' of 4.	3 / 5
Distinctiveness Conflict Risk	The repeated brand name 'Hasdata' creates a clear niche and the trigger is brand-anchored, giving low conflict risk. Not a 5 because the bare action verbs ('Manage data, records, automate workflows') are generic and could overlap with other data-management skills absent the brand.	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/hasdata/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.