Name: cookie-information
Rating: 59.2 (1 reviews)
Author: membranedev

cookie-information

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/cookie-information/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 a highly actionable, well-sequenced guide to driving Cookie Information through the Membrane CLI, with concrete commands and a clear connection state-machine; its main weaknesses are mild conciseness padding and inlined reference-style content that could live in separate files.

Suggestions

Remove the redundant 'Popular actions' section (it repeats the action-list command from 'Searching for actions') and the filler line 'Use action names and parameters as needed.'.

Tighten the opening SaaS-intro paragraph to the minimum context Claude needs, or move it under a short 'Overview' that the rest of the workflow does not depend on.

Consider moving the full action tree and the proxy-flags table into a one-level-deep reference file (e.g. REFERENCE.md) linked from SKILL.md to improve progressive disclosure.

Add an explicit validation/check step before running mutating actions (Update Consent Banner, Update Data Subject Request, Start Scan), e.g. confirm the target record via a Get before the Update.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and a flag table, but it includes some padding ('Use action names and parameters as needed.', a redundant 'Popular actions' section that repeats the already-shown action-list command) and a product-intro paragraph that could be trimmed, so it is mostly efficient but could be tightened rather than fully lean.	3 / 5
Actionability	Guidance is fully executable and copy-paste ready: concrete 'membrane' commands with '--json' flags, a worked '--input' JSON example, a 'connection ensure' URL example, and a complete proxy-flags table covering the common request cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced (install → login → connection ensure → poll for READY → branch on CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR → search → run) with state-driven checkpoints and a polling feedback loop; it stops short of 5 because destructive/update operations (Update Consent Banner, Start Scan) have no explicit validation-before-proceeding step.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers with no nested references and no bundle files to mismanage; it does not reach 5 because, at ~165 lines, the full action tree and the proxy-flags reference table are inlined in SKILL.md rather than split into one-level-deep reference files.	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 correctly includes both a 'what' and an explicit 'Use when...' trigger and names a distinct SaaS, but its capability list is generic ('manage data, records') and it lacks the natural user keywords (cookie consent, GDPR, privacy) that would drive reliable triggering.

Suggestions

Replace 'Manage data, records, and automate workflows' with the concrete capabilities from the body, e.g. 'Get and update consent banners, run consent statistics, handle data subject requests, and scan websites for cookie compliance'.

Add natural trigger keywords users actually say, e.g. 'Use when the user wants to manage cookie consent, handle GDPR/CCPA privacy compliance, or run website cookie scans.'

Use third-person action voice consistently and drop filler like 'integration' to tighten the opening phrase.

Dimension	Reasoning	Score
Specificity	Names the Cookie Information domain and a few verbs ('Manage data, records, and automate workflows'), but the actions are generic/abstract ('data', 'records') rather than the concrete API capabilities (consent banner, scan, data subject request) the body reveals, so it does not reach the 'several specific actions' bar of 4.	3 / 5
Completeness	It explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Cookie Information data'); the trigger clause is present (so not capped at 3) but the 'what' is vague and the 'when' could be more specific, which keeps it below 5.	4 / 5
Trigger Term Quality	It surfaces 'Cookie Information' and 'data', but omits the natural phrases a user would actually say ('cookie consent', 'GDPR/CCPA compliance', 'cookie banner', 'privacy'), so keyword coverage has relevant terms but is missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS 'Cookie Information' with a targeted trigger ('interact with Cookie Information data') gives it a clear niche with only minor overlap risk against generic data-management 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/cookie-information/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.