Name: display-video-360
Rating: 59.2 (1 reviews)
Author: membranedev

display-video-360

Display & Video 360 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Display & Video 360 data.

Quality

69%

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/display-video-360/SKILL.md

Quality

Content

72%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 CLI commands and a clean single-file structure, but it explains product background Claude already knows and lacks validation checkpoints for destructive/batch operations against the ad platform. Trimming the intro and adding verify steps would lift the weaker dimensions.

Suggestions

Remove the opening paragraph explaining what Display & Video 360 is and the "so you can focus on..." filler; assume Claude's competence and keep only integration-specific guidance.

Add a verification checkpoint before running actions (e.g., confirm the connection is READY and inspect the action's inputSchema/outputSchema before invoking it) to satisfy the destructive/batch feedback-loop requirement.

For proxy `membrane request` calls that mutate data (POST/PUT/PATCH/DELETE), add an explicit validate-then-retry or dry-run/confirm step to cap-safe the workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and a flags table, but the opening paragraph explains what Display & Video 360 is and includes filler like "so you can focus on the integration logic rather than auth plumbing" that Claude does not need.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection setup, action discovery/running, and proxying, plus a flags table and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based branching and polling, but there are no validation or verification checkpoints before running actions, and the proxy supports destructive methods (DELETE/PATCH) on ad-platform data without a verify/recover feedback loop.	3 / 5
Progressive Disclosure	It is a single well-organized SKILL.md under 50 lines of substantive content with clear section headers and no need for external references, meeting the bar for a simple skill.	5 / 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-targeted to a specific named product and includes an explicit trigger clause, but the capability list stays generic ("manage data, records, automate workflows") rather than naming concrete operations. Tightening specificity and adding trigger variations would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete operations the skill supports (e.g., "list and create campaigns, manage insertion orders and line items, pull reports") to improve specificity.

Add natural trigger variations beyond the single phrase (e.g., "Use when the user mentions DV360, Display & Video 360 campaigns, insertion orders, or programmatic ad buying").

Tie the when clause to specific record types (campaigns, line items, reports) so the trigger guidance is more explicit.

Dimension	Reasoning	Score
Specificity	Names the domain ("Display & Video 360 integration") and a couple of generic actions ("Manage data, records, and automate workflows") but the actions are abstract rather than the multiple concrete operations the skill supports; not comprehensive.	3 / 5
Completeness	It states both what the skill does ("Manage data, records, and automate workflows") and an explicit when clause ("Use when the user wants to interact with Display & Video 360 data"), though the when is somewhat generic.	4 / 5
Trigger Term Quality	The "Use when the user wants to interact with Display & Video 360 data" clause surfaces the natural product name, but offers only that one phrasing with no synonyms or variations users might say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Display & Video 360 gives it a clear niche with a distinct, low-conflict trigger unlikely to fire for unrelated 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/display-video-360/SKILL.md
Commit: f484c82

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