Name: adroll
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

adroll

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

Quality

67%

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with clear executable commands and a well-structured connection workflow with proper state handling and error recovery paths. The main weakness is some unnecessary introductory content explaining what AdRoll is and minor verbosity that could be trimmed. The popular actions table and proxy section add good reference value inline.

Suggestions

Remove the opening paragraph explaining what AdRoll is — Claude already knows this, and the skill description in frontmatter covers it.

Consider condensing the 'AdRoll Overview' hierarchy section, which adds minimal actionable value in its current form.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what AdRoll is ('marketing platform that helps businesses run advertising campaigns...') is unnecessary context Claude already knows. The AdRoll Overview section with the hierarchy is minimal but adds little value. The Membrane CLI setup and auth flow sections are reasonably efficient but could be tightened.	2 / 3
Actionability	The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Input/output expectations are clearly specified (e.g., --json flag, output field, state values).	3 / 3
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), polling instructions with --wait flag, and clear next steps for each state. The overall flow from install → auth → connect → discover → run is well-structured with validation checkpoints.	3 / 3
Progressive Disclosure	The content is reasonably well-organized with clear sections, but it's somewhat monolithic for its length (~150 lines of substantive content). The popular actions table and proxy request details could potentially be in separate reference files. However, there are no bundle files, and the content isn't excessively long, so the inline approach is acceptable but not ideal.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 names the platform (AdRoll) and includes an explicit 'Use when' clause, which is good structurally. However, the capabilities described are extremely generic ('manage data, records, and automate workflows') and could apply to virtually any SaaS integration, failing to convey what AdRoll-specific actions are supported. It needs concrete, domain-specific actions and richer trigger terms.

Suggestions

Replace generic 'manage data, records, and automate workflows' with specific AdRoll actions like 'manage ad campaigns, create audience segments, pull retargeting performance reports, configure conversion tracking'.

Add natural trigger terms users would say, such as 'retargeting', 'ad campaigns', 'display ads', 'audience segments', 'ad performance metrics'.

Enhance distinctiveness by specifying AdRoll's niche (e.g., 'retargeting and digital advertising platform') to differentiate from other marketing/ad integrations.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to AdRoll. It doesn't mention specific capabilities like managing ad campaigns, tracking conversions, managing audiences, or pulling performance reports.	1 / 3
Completeness	It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with AdRoll data) with an explicit 'Use when' clause, though both parts are quite generic.	3 / 3
Trigger Term Quality	It includes 'AdRoll' as a key trigger term which is specific, but lacks natural variations users might say such as 'ad campaigns', 'retargeting', 'ad performance', 'audience segments', or other AdRoll-specific terminology.	2 / 3
Distinctiveness Conflict Risk	'Manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills. The only distinguishing element is the 'AdRoll' name, which helps but the rest of the description could apply to almost any SaaS integration.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: membranedev/application-skills
Path: skills/adroll/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.