CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-photo-pack-generator

Generate a pack of professional or aesthetic photos from a single reference image while preserving the exact identity of the person.

Quality

60%

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/photo-pack-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 presents a clear, well-sequenced six-step workflow with concrete identity-lock guardrails, but it is weakened by verbatim repetition of the identity rules across three sections, an execution example whose flags don't match the actual script, and the absence of any output-validation step for a batch generation operation.

Suggestions

State the identity-lock rules once in a single section and reference it from the workflow steps, removing the near-verbatim duplicates in Step 4 and Guardrails.

Fix the Step 6 command to use only flags scripts/generate-pack.sh actually supports (--image or --image-url, --category, --model, --num, --view, --json, --likeness) and document those options in the body.

Add a validation checkpoint after generation — e.g., instruct the agent to inspect each output image for identity drift and regenerate failures — so the batch workflow includes a feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain-specific guidance with no explanation of concepts Claude already knows, but the identity rules are repeated nearly verbatim in three places ("Preserve the exact facial identity from the reference image", "Identity must remain identical to the reference photo" appear in Core Principles, Step 4, and Guardrails). This fits anchor 3 (mostly efficient but could be tightened) better than 2, since the padding is redundancy of novel guidance rather than unnecessary explanation.

3 / 5

Actionability

There is concrete guidance (a bash example, a negative-prompt list, a scene example, a category table), but the Step 6 example passes an "--identity-lock true" flag that scripts/generate-pack.sh does not support (unknown flags are silently discarded), and the script's real interface (--image-url, --model, --view, --json, --likeness) is undocumented in the body. Anchor 3 (concrete but incomplete, missing key details) fits; 4 would require the example to be fully aligned with the executable script.

3 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced (grounding, vision analysis, category selection, prompt construction, negative prompt, execution), but this is a batch operation ("--num 5" image pack) with no validation or verification checkpoint on the outputs — e.g., checking identity fidelity or handling failed generations. Per the judging guidelines, a batch skill without validation is capped at 3 even though the sequence itself is well laid out.

3 / 5

Progressive Disclosure

Sections are organized and the referenced bundle file (scripts/generate-pack.sh) exists, but the body does not surface the script's usage surface (its supported options and defaults) and category prompt templates are embedded inside the script rather than clearly signposted from SKILL.md. Anchor 3 (some structure, references present but not clearly signaled) fits better than 4.

3 / 5

Total

12

/

20

Passed

Description

53%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 communicates a clear, fairly distinctive capability but stops at a mid-level specification. It lacks any "when to use" trigger guidance and misses the natural terms users would say when needing identity-preserving photo packs.

Suggestions

Append a "Use when..." clause naming concrete trigger phrases, e.g. "Use when the user wants multiple themed photos (LinkedIn, dating, cinematic) generated from one picture of themselves while keeping their face identical."

Include natural trigger terms and synonyms users would actually say — headshots, professional portraits, LinkedIn photos, dating profile pictures, AI photo pack — to improve trigger matching.

Name the supported style categories (professional, lifestyle, fantasy, retro) in the description to raise specificity from 1-2 actions to a fuller action inventory.

DimensionReasoningScore

Specificity

"Generate a pack of professional or aesthetic photos from a single reference image while preserving the exact identity of the person" names the domain plus two concrete actions (generate photo pack, preserve identity), matching the 1-2 concrete actions anchor. It falls short of 4 because it does not list several distinct actions (e.g., style categories, editing capabilities) and is not vague enough for 2.

3 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Anchor 3 (clear what, when missing) fits better than 4, which requires an explicit 'when'.

3 / 5

Trigger Term Quality

"photos", "reference image", and "identity" are relevant keywords, but common natural phrases users would say — "headshots", "LinkedIn photo", "portrait", "AI photos of me" — are missing. Some relevant keywords without variations/synonyms matches anchor 3, not 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"preserving the exact identity of the person" from "a single reference image" carves a distinct niche versus generic image-generation skills, with only minor overlap risk against closely related photo-generation skills. Anchor 4 fits; 5 would require clearer distinct trigger phrases, which are absent.

4 / 5

Total

13

/

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/photo-pack-generator/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.