Name: didomi
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

didomi

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

Quality

70%

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

Quality

Content

75%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 executable commands and a well-sequenced connection workflow, but it carries some marketing-fluff padding and references an unlabeled 'Step 2'. Trimming the filler and fixing the step labeling would sharpen the weaker dimensions.

Suggestions

Remove marketing-style filler ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and condense the opening background paragraph to essentials Claude does not already know.

Label the post-connection section explicitly as 'Step 2' (or rephrase the 'skip to Step 2' reference) so the workflow's forward references resolve cleanly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but includes unnecessary padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection', plus a background paragraph on what Didomi is that Claude largely already knows — fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout — install, login, connection ensure/get with --wait, action list/run with --input JSON, and request with a full flag table — covering the common cases concretely.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again recovery loop, but the 'skip to Step 2' reference points to an unlabeled step and validation labeling is slightly inconsistent, leaving a minor gap.	4 / 5
Progressive Disclosure	Content is well organized under clear ## sections with no bundle files to reference, and most material is appropriately placed inline; it is a single monolithic file with no one-level-deep references, which keeps it just below the ideal split structure.	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly states what the skill does and when to use it with a clear named niche, but its action verbs are generic and trigger coverage relies mostly on the platform name alone. Tightening the action list and adding concrete user-facing trigger phrases would lift the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Didomi-specific actions (e.g., 'configure consent notices, manage vendors and purposes, retrieve consent strings, process user requests').

Expand the 'Use when' clause with natural trigger phrases users would actually say, such as 'Use when the user mentions Didomi, consent management, GDPR/CCPA consent, consent notices, or vendor and purpose configuration.'

Dimension	Reasoning	Score
Specificity	Names the domain (Didomi) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete specific operations, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Didomi data'), though the when could be more specific with concrete trigger phrases — fitting the anchor where both are present but when could be more explicit.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Didomi' and 'interact with Didomi data', but lacks common variations or synonyms beyond the platform name, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Targets a clearly named niche platform (Didomi) with distinct triggers, so it is unlikely to fire for the wrong skill and carries minimal conflict risk.	5 / 5
	Total	15 / 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/didomi/SKILL.md
Commit: f484c82

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