CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-multi-angle-shots

Generate a complete set of multi-angle product shots — front, side, back, top-down, and 45-degree perspective — for comprehensive product visualization.

Quality

70%

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/visual/multi-angle-shots/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-structured, mostly actionable recipe with fully specified prompts and models, but it lacks validation/retry checkpoints for the batch of five parallel generations and uses abbreviated command syntax. Small fixes — a success-check step, full CLI flag syntax, and consistent model selection across angles — would raise it substantially.

Suggestions

Add a validation step after generation: check each of the 5 results succeeded (e.g. via muapi predict status) and retry any failed angle before presenting the grid — the rubric caps batch workflows without validation at 3.

Write the invocations as complete commands (e.g. `muapi image generate --model ai-product-photography --prompt "..." --aspect-ratio 1:1`) instead of the parenthetical model= shorthand.

Fix the garbled opener ("Submit a single the plan") and reconcile the inconsistent per-angle model choices (steps 1-3 and 5 use different models for what should be one visually coherent set).

DimensionReasoningScore

Conciseness

The body is lean — input table, five prompt templates, and brief notes with no explanations of concepts Claude already knows. Minor trimming is possible: the description is repeated verbatim as a bold line under the heading, and "comprehensive product visualization"-style padding appears twice. Not a 5 because of that duplication; not a 3 because there is no real over-explanation.

4 / 5

Actionability

Concrete guidance throughout: full copy-paste-ready prompts, model IDs, and aspect ratios per shot, plus an executable curl fallback with polling instructions. It falls short of 5 because the primary invocations are written in abbreviated pseudo-command form ("`muapi image generate` (model=`ai-product-photography`)") rather than complete copy-paste command lines with flags for prompt and aspect ratio.

4 / 5

Workflow Clarity

The sequence is clear (five parallel generations, then presentation and follow-up offers), but there are no validation checkpoints — nothing instructs checking that each generation succeeded or retrying failed angles, and per the rubric a batch operation without validation is capped at 3. The opening line "Submit a single the plan with all angles in parallel" is also garbled, adding ambiguity. Not a 2 because the per-shot steps are well defined.

3 / 5

Progressive Disclosure

There are no bundle files and none are needed; content is appropriately inline for a skill of this size, with well-labeled sections (Inputs, Steps, Notes, Trigger Keywords, Notes for the Executing Agent). It misses 5 due to minor organization gaps: two separate 'Notes' sections, a stray trailing '---', and the ~64-line body sitting just past the under-50-lines simple-skill threshold.

4 / 5

Total

15

/

20

Passed

Description

58%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.

A clear, specific 'what' statement with enumerated deliverables, but the description is missing any 'use when' trigger guidance, which caps completeness and weakens trigger-term quality. Adding an explicit trigger clause with natural user phrases would lift the two heaviest-weighted dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants product images from multiple angles, a full product photo set, or mentions 360/all-sides product views."

Weave natural synonyms into the description body (multi-angle, all sides, product photo set, 360 product views) instead of leaving them only in the body's Trigger Keywords section.

Align the enumerated angles with what the skill actually generates (the body's fifth shot is a low-angle hero shot, not a 45-degree perspective) to avoid over-claiming.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables — "front, side, back, top-down, and 45-degree perspective" — anchored to a clear action ("Generate a complete set of multi-angle product shots"). It stays below a 5 because it describes a single generation action with specific outputs rather than multiple distinct concrete actions, and the angles listed don't perfectly match the body's actual shots (hero/low-angle vs '45-degree perspective').

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which per the judging guidelines caps completeness at 3. It is not a 4 because the 'when' is entirely absent rather than merely weakly implied, and not a 2 because the 'what' half is strong.

3 / 5

Trigger Term Quality

It contains a few relevant natural terms ("multi-angle product shots", "product visualization") but no trigger guidance and few synonyms or variations users would say (e.g. 'product photography set', 'all sides', '360'). This sits at the 'some relevant keywords but missing common variations' anchor, not 4 ('a few natural terms missing' would require broader coverage) nor 2 (which implies only generic keywords).

3 / 5

Distinctiveness Conflict Risk

The multi-angle product-shot niche is fairly distinct (enumerated angles, product photography context), with only minor overlap risk against generic product-photography or single-image generation skills. It falls short of 5 because without any 'when' guidance, a broader 'product photography' request could plausibly trigger it.

4 / 5

Total

14

/

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/visual/multi-angle-shots/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.