CtrlK
BlogDocsLog inGet started
Tessl Logo

google-campaign-manager

Google Campaign Manager 360 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Campaign Manager 360 data.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google-campaign-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 highly actionable with concrete, executable Membrane CLI commands and a well-sequenced connection workflow with state-based validation. It loses points mainly on a duplicated discovery section, light product-definition padding, and inconsistent step numbering.

Suggestions

Merge the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list`, to remove the duplicated command.

Fix the step numbering: introduce a labeled '1a'/'Step 1' or relabel the 'Step 2' reference so the connect → poll → act flow is unambiguous.

Trim or relocate the opening paragraph defining Campaign Manager 360, since Claude can infer the product's purpose; lead instead with the integration workflow.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes an opener explaining what Campaign Manager 360 is and repeats the action-list command in both 'Searching for actions' and 'Popular actions'. This matches the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor; it is not 4 due to the duplicated discovery command and product-definition padding.

3 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection, polling, action search/run, and proxying (e.g. `membrane connection ensure "https://campaignmanager.google.com/" --json`), matching the 'mostly executable guidance; concrete code or commands with minor gaps' anchor. It is not 5 because placeholders (CONNECTION_ID, actionId, QUERY intent) require substitution and the common-case examples are not fully fleshed out.

4 / 5

Workflow Clarity

The connect-to-poll-to-act flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop ('Keep polling until state is no longer BUILDING'). This matches the 'clear sequence with most checkpoints present; minor validation gaps' anchor; it is not 5 because the numbering is incoherent (a '1b' without '1a', and a 'Step 2' that is not clearly labeled).

4 / 5

Progressive Disclosure

The body is a single self-contained file with well-organized sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) and no external references needed, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor. It is not 5 because of the duplicated 'Popular actions'/'Searching for actions' content and minor section-numbering inconsistencies.

4 / 5

Total

15

/

20

Passed

Description

57%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 clearly names a specific product and answers both 'what' and 'when', but its action list is generic and its trigger terms lack synonyms and concrete use-case phrasing. Stronger, more specific triggers and concrete actions would raise the score.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete ones such as 'create and manage campaigns, placements, and Floodlight activities, and pull reports'.

Add natural trigger synonyms users actually say, e.g. 'Use when the user mentions Campaign Manager 360, DCM, DoubleClick, floodlight activities, or ad serving reports'.

Make the 'when' clause more specific by tying it to concrete tasks (reporting, campaign setup, creative assignments) instead of 'interact with data'.

DimensionReasoningScore

Specificity

The description names the domain ("Google Campaign Manager 360 integration") but its actions — "Manage data, records, and automate workflows" — are generic rather than concrete, matching the anchor where actions are minimal or generic. It does not reach 3 because the listed actions are not specific concrete operations like 'create campaigns' or 'pull reports'.

2 / 5

Completeness

It states both the 'what' ("Manage data, records, and automate workflows") and the 'when' ("Use when the user wants to interact with Google Campaign Manager 360 data"), matching the anchor where both are present but the 'when' could be more explicit. It is not 5 because the trigger phrase is generic ('interact with data') rather than concrete.

4 / 5

Trigger Term Quality

It includes the product name "Google Campaign Manager 360" and terms like "data" and "workflows", but misses common variations or synonyms users say (DCM, DoubleClick Campaign Manager, ad reports, floodlight). This matches the 'some relevant keywords but missing common variations' anchor; it is not 4 because natural synonyms are largely absent.

3 / 5

Distinctiveness Conflict Risk

Naming a specific Google product ("Google Campaign Manager 360") gives it a clear niche with minimal conflict risk, matching the 'mostly distinct; minor overlap risk' anchor. It is not 5 because it could still overlap with adjacent Google advertising skills (e.g. Google Ads) given the generic 'interact with data' trigger.

4 / 5

Total

13

/

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.