Name: google-ad-manager
Rating: 60 (1 reviews)
Author: membranedev

google-ad-manager

Google Ad Manager integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Ad Manager 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/google-ad-manager/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 highly actionable with executable commands and a clear connection workflow including validation and error handling. Its main weaknesses are an unnecessary introductory paragraph explaining concepts Claude already knows and a broken "Step 2 / 1b" numbering scheme in the connection flow.

Suggestions

Remove or drastically shorten the opening paragraph describing what Google Ad Manager is and who uses it; Claude already knows this.

Fix the connection-flow numbering: either relabel sections as explicit Step 1 / Step 2 or replace the dangling "skip to Step 2" references with concrete section links.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven reference, but the opening paragraph explaining what Google Ad Manager is and who uses it is exactly the kind of background Claude already knows and the rubric penalizes.	3 / 5
Actionability	It provides copy-paste-ready bash commands across install, login, connection, action search/run, and proxy requests, plus a concrete flag table and a JSON input example covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state polling, clientAction handling, and an explicit poll-after-action feedback loop, but the "skip to Step 2" references point to an undefined Step 2 and the "1b" subheading has no matching "1a".	4 / 5
Progressive Disclosure	A single self-contained SKILL.md with clear, well-ordered section headers and no nested references; organization is solid though the file is somewhat dense with inline reference-like detail (proxy flags, clientAction schema).	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 well-scoped to a distinct product and includes both a what and a when clause, but its action vocabulary is generic and its trigger phrasing lacks synonyms or variations. Tightening the actions to concrete GAM entities and broadening the trigger terms would raise it.

Suggestions

Replace generic verbs with concrete Google Ad Manager operations, e.g. "Manage orders, line items, ad units, and creatives; pull reports."

Broaden the trigger terms to include natural variations users say, e.g. "Use when the user wants to manage ad inventory, orders, or reports in Google Ad Manager (GAM)."

Dimension	Reasoning	Score
Specificity	Names the Google Ad Manager domain and a few actions ("Manage data, records, and automate workflows"), but the actions are generic abstractions rather than concrete GAM operations like line items, orders, or reports.	3 / 5
Completeness	It states both what the skill does (integration, managing data/records, automating workflows) and when to use it ("Use when the user wants to interact with Google Ad Manager data"), though the triggers and actions could be more concrete.	4 / 5
Trigger Term Quality	The core natural term "Google Ad Manager" appears in a Use-when clause, but coverage is limited to a single phrasing and misses common variations like ad inventory, ad ops, GAM, or advertising.	3 / 5
Distinctiveness Conflict Risk	It is scoped to a specific named product with a product-specific trigger, giving it a clear niche and minimal overlap with 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/google-ad-manager/SKILL.md
Commit: f484c82

Reviewed: 5 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.