CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

goose-product-photos

Make product photos (studio, lifestyle or on a model) of a brand's real products with GooseWorks in this chat. Start brand work with brand_knowledge_browse and follow the next_step in every answer.

Quality

75%

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 ./skills/entry/goose-product-photos/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, dense instruction skill: concrete tool calls with parameters, a well-sequenced workflow gated on explicit customer confirmation and per-photo approval, and appropriate single-file structure. Its weaknesses are mild — occasional over-compressed phrasing, no error-recovery loop, and an unlabeled workflow section.

Suggestions

Rewrite the video make-command rule into two or three shorter sentences so its compression stops costing clarity.

Add a brief failure path, e.g. what to do when photos_generate fails or photos_read never reports ready.

Give the core workflow bullet list its own heading (e.g. "## Workflow") so it reads as a section rather than floating between the intro and Rules.

DimensionReasoningScore

Conciseness

Zero padding and no explanations of concepts Claude already knows — every bullet carries a rule ("Money is a credit number exactly as an answer gives it: never dollars or your own math"). Not 5 because a few sentences are over-compressed to the point of confusion (e.g., the video make-command rule), so brevity does not always preserve clarity.

4 / 5

Actionability

Gives concrete tool names and exact parameters for most steps ("photos_update: brand_id, the photo's output id and action 'approve' ... or 'archive'", "get its price first from the same call as a dry run"). Not 5 because media_upload and brand_update carry no parameter detail and the dry-run call mechanics are underspecified.

4 / 5

Workflow Clarity

A clear end-to-end sequence (brand_knowledge_browse → brand_read → offer → price → confirm → generate → photos_read until ready → approve/archive) with real checkpoints: paid work gated on the customer's yes to the credit total, a readiness poll, and per-photo keep/drop validation. Not 5 because there is no error-recovery guidance for failed generation or photos that never become ready.

4 / 5

Progressive Disclosure

No bundle files exist and the body is under 50 lines with no content that needs splitting, so the simple-skill allowance applies. Not 5 because organization has a minor gap: the core workflow bullet list sits unlabeled between the intro and the "## Rules" header rather than under its own heading.

4 / 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 specific and distinct, naming three concrete photo types and the GooseWorks context with natural trigger vocabulary. Its main weakness is the complete absence of when-to-use guidance, which caps completeness and limits its value for skill triggering.

Suggestions

Add an explicit trigger clause, e.g. "Use when the customer wants photos, shots, or images of their brand's physical products."

Broaden natural keyword coverage with synonyms users say, such as "product shots", "product images", or "photo shoot".

Optionally mention the pricing-preview and keep/drop approval capabilities to round out the "what" coverage.

DimensionReasoningScore

Specificity

Names several concrete, distinct deliverables ("studio, lifestyle or on a model" product photos of a brand's real products) plus a concrete workflow entry action ("Start brand work with brand_knowledge_browse"). Not 5 because the description omits notable capabilities like the pricing preview and the keep/drop approval flow; not 3 because more than 1-2 bare actions are explicitly listed.

4 / 5

Completeness

The "what" is clear ("Make product photos ... of a brand's real products with GooseWorks in this chat"), but there is no "Use when..." clause or equivalent trigger guidance — "Start brand work with brand_knowledge_browse" describes how, not when. Per the judging guidelines, a missing when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "product photos", "studio", "lifestyle", "on a model", "brand". Not 5 because common synonyms and variations like "product shots", "product images", or "photo shoot" are missing.

4 / 5

Distinctiveness Conflict Risk

"product photos ... of a brand's real products with GooseWorks in this chat" carves a fairly distinct niche with brand-specific triggers. Not 5 because there is minor overlap risk with generic image-generation or brand-content skills; not 3 because it is more specific than broad domain claims.

4 / 5

Total

15

/

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

gooseworks-ai/goose-skills

Path

skills/entry/goose-product-photos/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.