CtrlK
BlogDocsLog inGet started
Tessl Logo

carbon-ads

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

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/carbon-ads/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, giving executable membrane commands and a clear connection-readiness workflow with polling checkpoints. It is held back only by minor over-explanation and reference-style content that could live in separate files.

DimensionReasoningScore

Conciseness

The body is mostly lean CLI commands and a tight flags table, but the opening paragraph explaining what Carbon Ads is and the 'Agent Types' aside explain things Claude largely already knows.

4 / 5

Actionability

It provides copy-paste-ready membrane commands for install, auth, connection, action search/run, and proxying, plus a concrete flags table covering the common request cases.

5 / 5

Workflow Clarity

There is a clear install→authenticate→connect→search→run sequence with explicit state-check polling (READY/BUILDING/CLIENT_ACTION_REQUIRED) as a feedback loop, though post-action verification is only implicit.

4 / 5

Progressive Disclosure

Content is organized into well-labeled sections with no nested references and no bundle files present, but reference-style material (the proxy flags table, popular actions) is inlined rather than split out.

4 / 5

Total

17

/

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 identifies the Carbon Ads niche and includes an explicit Use-when clause, satisfying both what and when. Its main weakness is generic action verbs and sparse natural trigger terms rather than concrete, Carbon Ads-specific operations.

Suggestions

Replace generic verbs with concrete Carbon Ads actions, e.g. 'Serve creatives, manage campaigns, and pull account reports.'

Add natural trigger terms users would say, such as 'ads', 'campaigns', 'creatives', or 'ad network'.

Make the Use-when clause more specific, e.g. 'Use when the user wants to manage Carbon Ads campaigns or creatives.'

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Carbon Ads domain with a few actions, but the actions are generic (manage, automate) rather than concrete Carbon Ads operations like serving creatives or pulling campaign reports.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Carbon Ads data"), but the when clause is generic rather than tied to concrete triggers.

4 / 5

Trigger Term Quality

"Carbon Ads" and "data"/"records" are relevant keywords, but natural user phrases and synonyms (e.g., ads, campaigns, creatives, ad network) are missing, so coverage is only partial.

3 / 5

Distinctiveness Conflict Risk

The "Carbon Ads" niche is clearly named with a distinct trigger, so overlap with other skills is low; only the generic 'data/records/workflows' phrasing keeps it from a 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.