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

Blog Docs Log in Get started

ethyca

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

Quality

72%

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

Quality

Content

82%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 copy-paste-ready CLI commands and a well-sequenced connection state-machine, and is mostly token-efficient; its main gaps are a few padded sentences, the absence of a post-action validation checkpoint, and inline reference material that could be split out.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and compact bullet overviews, but contains a few padded sentences (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection'), fitting 'efficient; minor instances of over-explanation' rather than the fully lean level 5.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end (install, login incl. headless, connection ensure, polling, action list/run with JSON input, proxy request with a full flags table), matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	A clear install→auth→connect→poll sequence exists with an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-poll after user action), but there is no explicit validation/checkpoint after running actions, fitting 'clear sequence with most checkpoints; minor validation gaps' rather than the fully checkpointed level 5.	4 / 5
Progressive Disclosure	No bundle files exist (single-file skill) and sections are well organized (Overview, Working with Ethyca, Popular actions, Best practices), but the 20-item entity catalog and full connection-state reference are inlined rather than split into a reference file, fitting 'good structure; minor organization gaps' rather than the cleanly split level 5.	4 / 5
	Total	17 / 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 correctly answers both what and when and is anchored to a distinct product, but its action verbs and trigger terms are generic, missing the Ethyca-specific vocabulary (privacy requests, consent, compliance) that would make it sharply discoverable.

Suggestions

Replace generic verbs with Ethyca-specific actions, e.g. 'Manage privacy requests, consent preferences, datamaps, and data registries.'

Expand the 'Use when' clause to list concrete natural triggers: 'Use when the user wants to submit or track privacy requests (DSR/DSAR), manage consent, or build a data map in Ethyca.'

Use third person consistently and keep the concise style while adding the missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the Ethyca domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic and not Ethyca-specific (no privacy requests, consent, datamaps), matching the '1-2 concrete actions but not comprehensive' anchor rather than the more specific level 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Ethyca data') are present, but the 'when' is a single generic phrase rather than concrete trigger listings, matching 'both present but when could be more explicit' rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	The only natural trigger keyword is 'interact with Ethyca data'; common variations users would actually say (privacy requests, compliance, consent, DSR) are missing, fitting 'some relevant keywords but missing common variations' rather than the fuller coverage at level 4.	3 / 5
Distinctiveness Conflict Risk	Naming the distinct product 'Ethyca' with a product-bound trigger gives a clear niche with minimal conflict risk, fitting 'mostly distinct; minor overlap risk' rather than the maximally distinct level 5 whose richer trigger set is absent.	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/ethyca/SKILL.md
Commit: f484c82

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