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

Blog Docs Log in Get started

criteo

Criteo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Criteo 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/criteo/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 content is well-structured, executable, and respects Claude's competence with concrete membrane CLI commands and a clearly sequenced connection flow. Its main weaknesses are minor: a few verbose asides, placeholder-filled examples, and absent verification steps on the action-run/proxy paths.

Suggestions

Add explicit validation/verification guidance after running actions or proxy requests (e.g., checking the output field or error state) to strengthen workflow clarity.

Trim contextual asides such as the retargeting definition and the 'focus on the integration logic rather than auth plumbing' phrasing to tighten conciseness.

Show at least one fully self-contained command with real-looking sample values instead of bare CONNECTION_ID/QUERY placeholders to push actionability toward copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, a compact flag table, and short prose, with only minor over-explanation (e.g., the retargeting intro line and the 'focus on the integration logic rather than auth plumbing' aside) that could be trimmed.	4 / 5
Actionability	It provides concrete, executable membrane commands with flags and JSON examples for connecting, listing, running, and proxying actions; the remaining gap is the use of undefined placeholders (CONNECTION_ID, QUERY) rather than fully self-contained examples, keeping it just below copy-paste-ready 5.	4 / 5
Workflow Clarity	The connection setup flow is clearly sequenced with explicit state branches (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the action-run and proxy-request paths lack explicit verification steps, leaving minor validation gaps.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in a single SKILL.md with clear, well-signaled section headers and no nested or broken references; it is well-organized, though some API/proxy detail could conceivably live in a separate reference file.	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 is concise, names a distinct niche, and includes an explicit 'Use when' trigger, but its action verbs are generic ('manage data, records, automate workflows') rather than concrete. Trigger term coverage relies almost entirely on the brand name and lacks natural variations.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Criteo-specific actions such as 'manage campaigns, audiences, budgets, and reports' to raise specificity.

Broaden trigger terms beyond the brand name by adding natural phrases a user might say, e.g. 'ad campaigns, retargeting audiences, or Criteo reports'.

Sharpen the 'when' clause to reference concrete scenarios (e.g. 'Use when managing Criteo ad campaigns, audiences, or budgets') rather than the generic 'interact with Criteo data'.

Dimension	Reasoning	Score
Specificity	The description names the Criteo domain and a few action verbs ('Manage data, records, and automate workflows'), but those verbs are generic rather than concrete, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor while leaning slightly below it.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Criteo data'), but the when clause is generic, fitting the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Criteo' and 'interact with Criteo data' provide relevant domain keywords but miss common natural variations, synonyms, or file extensions, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Criteo is a specific named advertising platform and the trigger ('Criteo data') is a distinct brand name, giving it a clear niche with minimal conflict risk against other skills.	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/criteo/SKILL.md
Commit: f484c82

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