CtrlK
BlogDocsLog inGet started
Tessl Logo

vertex-ai-media-master

Execute automatic activation for all google vertex ai multimodal operations operations. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

39

Quality

38%

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 ./plugins/productivity/003-jeremy-vertex-ai-media-master/skills/vertex-ai-media-master/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%

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

The body is well-structured with good progressive disclosure and a solid error-handling table, but it is instruction-only with no executable code, leaving its steps abstract rather than copy-paste ready. Workflow checkpoints for batch generation are also underdeveloped.

Suggestions

Add executable code or concrete commands for at least the core flows (client init, an image-generation request, a video-analysis request) so guidance is copy-paste ready.

Insert explicit validation checkpoints in the workflow (e.g. verify API response, check safety-filter flags, confirm asset integrity) with a fix-and-retry loop before delivery.

Move volatile specifics (exact model IDs, quota numbers) into the existing references file so the body stays lean and age-resistant.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of beginner-concept filler, but it embeds time-sensitive specifics (model versions, quota figures) in prose steps that could be tightened, and the prose-only steps add length without executable value.

2 / 3

Actionability

Steps are abstract directions ('Initialize the Vertex AI client', 'Construct the generation request with explicit parameters') with no executable code or commands anywhere, and the examples lack runnable snippets.

1 / 3

Workflow Clarity

A clear 7-step numbered sequence exists with a helpful error table, but batch media-generation operations lack explicit validate-then-fix-then-retry checkpoints until a vague final 'Validate results', capping the score at 2.

2 / 3

Progressive Disclosure

Sections are well organized and a real one-level-deep reference to references/core-capabilities.md is clearly signaled alongside curated external docs, giving easy navigation.

3 / 3

Total

8

/

12

Passed

Description

35%

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 a generic auto-activation stub: it names the platform but no concrete actions, and its trigger clause is boilerplate that provides no real activation guidance. It conveys a weak 'what' and an effectively absent 'when'.

Suggestions

Replace the boilerplate trigger clause with concrete natural phrases a user would say, e.g. 'Use when generating images with Imagen, analyzing video with Gemini, or composing audio with Lyria on Vertex AI.'

List specific concrete actions instead of repeating 'operations' (e.g. 'Generate images, analyze video, compose audio tracks, and automate marketing campaign assets').

Adopt third-person active voice and remove the redundant 'operations operations' duplication for clarity.

DimensionReasoningScore

Specificity

Names the domain ('google vertex ai multimodal operations') but lists no concrete actions, repeating the vague word 'operations' twice rather than stating e.g. generate images, analyze video, or compose audio.

2 / 3

Completeness

A weak 'what' is present but the 'when' is only implied via generic boilerplate rather than an explicit 'Use when...' clause naming real triggers, capping completeness at 2.

2 / 3

Trigger Term Quality

The trigger guidance ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose') is pure boilerplate with no natural keywords a user would actually say.

1 / 3

Distinctiveness Conflict Risk

The Vertex AI multimodal niche is specific enough to avoid broad conflicts, but the generic 'operations' phrasing keeps it from being sharply distinct.

2 / 3

Total

7

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.