CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-product-campaign

Generate a full multi-channel product campaign — hero visuals, social media assets, short ad video, and platform-specific crops for an end-to-end launch campaign.

Quality

78%

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 ./library/social/product-campaign/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 — exact models, prompts, commands, and a curl fallback make it near copy-paste executable — and appropriately concise for a self-contained skill. The main gap is the absence of validation/verification checkpoints in a batch generation workflow, plus small structural redundancies.

Suggestions

Add an explicit validation step after generation (e.g., confirm each asset exists and matches its target aspect ratio, and re-run or adjust the prompt on failed generations) before presenting the campaign set.

Fix the garbled sentence 'Submit a SINGLE the plan with all phases running in parallel' and consolidate the two Notes sections into one to remove structural duplication.

Remove the verbatim repetition of the description under the H1 title, or replace it with a one-line purpose statement, to trim redundant tokens.

DimensionReasoningScore

Conciseness

The body is a lean inputs table plus per-asset prompt/model/aspect-ratio specs with no explanations of concepts Claude already knows. Minor trim-able redundancy — the description is repeated verbatim as bold text under the H1, and there are two separate 'Notes' sections — keeps it at 4 rather than 5.

4 / 5

Actionability

Fully executable throughout: exact model IDs ('nano-banana-pro-edit', 'kling-v3.0-pro-image-to-video'), complete copy-paste prompts with {{input}} placeholders, a curl fallback with exact endpoint and headers, and 'muapi predict wait <request_id>' for polling. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Phases A-C are sequenced with explicit cross-step dependencies ('using output of step 1') and parallelization guidance, but this is a batch operation (five assets across parallel phases) with no validation or verification steps — no check that a generation succeeded or matches its target aspect ratio before presenting the set. Per the guidelines, missing validation in batch workflows caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed; all content is short, belongs inline, and sits in well-organized sections (Inputs / Steps / Notes / Trigger Keywords). The split 'Notes' / 'Notes for the Executing Agent' pair around a stray '---' separator is a minor organization gap, fitting 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

71%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 strong on specificity and distinctiveness, clearly stating what the skill generates across campaign channels. Its main weakness is the missing 'when to use' trigger clause, which caps completeness, and trigger-term coverage that relies on the body's keyword list rather than the description itself.

Suggestions

Add a 'Use when...' clause to the description (e.g., 'Use when the user asks for a product launch campaign, marketing campaign assets, or a full brand campaign across channels.') to raise completeness.

Fold one or two natural trigger variations ('marketing campaign', 'product launch') into the description text itself so keyword coverage does not depend on the body's Trigger Keywords section.

DimensionReasoningScore

Specificity

The description names the domain plus four concrete deliverables — 'hero visuals, social media assets, short ad video, and platform-specific crops' — matching the comprehensive-coverage anchor; coverage of campaign output types is complete with no minor gaps.

5 / 5

Completeness

The 'what' is explicit ('Generate a full multi-channel product campaign — hero visuals...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is clear rather than vague.

3 / 5

Trigger Term Quality

Natural phrases like 'product campaign', 'launch campaign', and 'social media assets' are present, but common variations users would say ('marketing campaign', 'brand campaign', 'product launch') appear only in the body's Trigger Keywords section, not the description itself — good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The multi-channel campaign framing with specific asset types carves a distinct niche, but there is minor overlap risk with closely related skills the body itself references (social-pack, ai-product-shot), fitting the 'mostly distinct' anchor rather than the clear-niche anchor.

4 / 5

Total

16

/

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.

Validation — 15 / 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

SamurAIGPT/Generative-Media-Skills

Path

library/social/product-campaign/SKILL.md

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.