Name: usercentrics
Rating: 47.2 (1 reviews)
Author: membranedev

usercentrics

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

Quality

51%

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

Quality

Content

45%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 skill hides a genuinely useful, executable Membrane CLI integration guide behind an enormous, duplicated, generic term list that consumes ~90% of the body and adds no value. The actionable connection/action workflow is strong, but token efficiency and progressive disclosure are severely compromised by the padding.

Suggestions

Delete the ~1500-line enumeration of generic terms (CMP Data, Comment, Review, Approve, etc.) — it is duplicated many times over and provides no skill-specific guidance Claude does not already know.

Move any genuinely needed entity/terminology reference into a separate references/ file linked once from the body, or replace the list with a short curated set of Usercentrics-specific resources (Services, Vendors, TCF strings, Consent Decisions, Banners).

Add a brief error-recovery note to the proxy and action-run sections (e.g. how to interpret non-2xx responses or action output errors) to close the workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	The body is ~1696 lines yet roughly 1500 of them (lines 21-1570) are a massively duplicated enumeration of generic nouns/verbs ('Comment', 'Review', 'Rate', 'Approve', 'Reject' repeated dozens of times) that explain nothing Claude does not already know and add no skill-specific value, matching the 'Severely verbose; heavily padded' anchor 1 — in fact worse than its example.	1 / 5
Actionability	The operational section provides copy-paste-ready commands with real flags and placeholders ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://usercentrics.com/" --json', 'membrane action run <actionId> --connectionId=... --input ...'), matching anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps'); not 5 because no fully worked example with real action IDs and sample output is shown.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-check checkpoints and a feedback loop (ensure -> poll --wait -> handle CLIENT_ACTION_REQUIRED -> re-poll -> READY -> search -> run), matching anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps'); not 5 because the proxy/action-run sections lack explicit error-recovery guidance and there is no validate-then-fix checklist.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets are absent) and all content is inlined into one monolithic SKILL.md, with a ~1500-line term dump that clearly belongs in a separate reference file or should be removed entirely, matching anchor 2 ('content that clearly belongs in separate files is inlined'); the few section headers lift it only slightly above a wall of text, not enough to reach anchor 3 given the absence of any signaled references.	2 / 5
	Total	11 / 20 Passed

Description

57%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 successfully pairs a 'what' with a 'when' trigger and anchors on a distinctive product name, but its capability verbs are generic ('manage', 'automate') and it lacks natural synonyms like 'consent', 'CMP', or 'cookie banner'. It is functional for activation but under-specific.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Usercentrics actions, e.g. 'Manage consent settings, banners, TCF strings, services, and vendors'.

Add natural trigger synonyms users would say, e.g. 'Use when working with consent management, cookie banners, GDPR/CCPA consent, or Usercentrics data.'

Tighten the 'when' clause with specific activation contexts rather than the vague 'interact with Usercentrics data'.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage data, records, and automate workflows' name the Usercentrics domain but the actions (manage, automate) are minimal and generic rather than concrete, matching the anchor 'Names the domain but actions are minimal or generic' rather than anchor 3 which requires 1-2 concrete actions.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Usercentrics data'), matching anchor 4 where both are present but the 'when' could be more specific; not 5 because the trigger phrase is generic and lacks concrete activation terms.	4 / 5
Trigger Term Quality	The description repeats 'Usercentrics' / 'Usercentrics data', a specific proper noun a user would naturally say, but offers no synonyms or variations (consent, CMP, cookie banner) that anchor 5 requires; this sits at anchor 3 ('some relevant keywords but missing common variations') rather than anchor 2 which demands only generic keywords.	3 / 5
Distinctiveness Conflict Risk	The Usercentrics proper-noun niche gives it a mostly distinct trigger with minor overlap risk, matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'); not 5 because the generic action verbs ('manage data, automate workflows') overlap with any data-management skill.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1697 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/usercentrics/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.