CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-studio-image

Geracao de imagens humanizadas via Google AI Studio (Gemini). Fotos realistas estilo influencer ou educacional com iluminacao natural e imperfeicoes sutis.

48

Quality

51%

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/ai-studio-image/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 content is strong on concrete commands and has a well-sequenced workflow, but is undermined by duplicated overview sections and generic boilerplate padding, hardcoded user-specific Windows paths that break portability, a missing referenced file (api-reference.md), and absent validation steps for batch generation. It is a mid-range skill body: actionable in intent but needing a cleanup pass to be token-efficient and fully trustworthy.

Suggestions

Remove the duplicated '## Ai Studio Image — Especialista Em Imagens Humanizadas' section and the generic Best Practices / Common Pitfalls / Related Skills boilerplate, which add no domain-specific value.

Replace hardcoded 'C:\Users\renat\skills\ai-studio-image\' paths with relative paths (e.g. 'scripts/generate.py') so commands are portable and copy-paste ready.

Fix the reference list: either create 'references/api-reference.md' or remove the dangling entry, and move the detailed template/humanization-layer tables into the existing reference files.

DimensionReasoningScore

Conciseness

The body has several padded or duplicated sections: the overview text appears twice ('## Overview' and '## Ai Studio Image — Especialista Em Imagens Humanizadas' repeat the same description), and generic template filler like 'Provide clear, specific context about your project' under Best Practices and 'Complementary skill for enhanced analysis' under Related Skills adds no value. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than anchor 3, since the redundancy and boilerplate go beyond isolated tightening opportunities.

2 / 5

Actionability

Commands are concrete and complete with flags, e.g. 'python ...\scripts\generate.py --prompt "..." --mode influencer --format square --model gemini-2-flash-exp', plus a model cost table and troubleshooting table. It falls short of anchor 5 only because every command hardcodes the author's machine-specific path 'C:\Users\renat\skills\ai-studio-image\' (and the API-key example block is malformed), so commands are not copy-paste ready as-is.

4 / 5

Workflow Clarity

The 5-step workflow (identify mode → format → humanize prompt → generate → present/iterate) is clearly sequenced, but there are no validation checkpoints (e.g. verifying the API key or output before proceeding), and the batch generation feature ('--variations 4') has no verification step, which caps workflow clarity at 3 per the batch-operation guideline. It does not drop to 2 because the sequence itself is well defined with decision tables.

3 / 5

Progressive Disclosure

A references section points to 'references/setup-guide.md' and 'references/prompt-engineering.md' (both real, one level deep), but the third listed reference 'references/api-reference.md' does not exist in the bundle, and substantial detail (full template tables, the five humanization layers) is inlined in SKILL.md. This fits anchor 3 ('some structure but could be better organized') rather than anchor 4, whose 'references mostly clear' expectation is undermined by the broken reference.

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 and fairly distinctive 'what' (humanized realistic photo generation via Google AI Studio/Gemini) but completely omits any 'when to use' guidance and lacks the natural trigger phrases a user would say. It sits at the midpoint of the rubric: specific enough to identify the domain, but not actionable as a standalone trigger.

Suggestions

Add an explicit trigger clause, e.g. 'Use quando o usuario pedir para gerar/criar imagens ou fotos realistas, fotos estilo influencer, ou imagens para material educacional.'

Include natural user-facing synonyms such as 'gerar imagem', 'criar foto', 'foto realista', and 'imagem de IA' to improve trigger term coverage.

List the concrete capabilities (modes, formats, templates, batch generation) to lift specificity from one action to several.

DimensionReasoningScore

Specificity

The description names the domain ('Geracao de imagens humanizadas via Google AI Studio (Gemini)') and one concrete action (generate images) plus style attributes ('estilo influencer ou educacional', 'iluminacao natural e imperfeicoes sutis'), but offers only a single action rather than several specific ones. It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') and not anchor 4, which requires a list of several distinct actions.

3 / 5

Completeness

The 'what' is clear (generate humanized realistic photos via Google AI Studio/Gemini), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It cannot score 4 because the 'when' is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

Terms like 'imagens humanizadas', 'fotos realistas', and 'influencer' are relevant, but common natural phrases users would actually say ('gerar imagem', 'criar foto', 'foto de IA') are absent. This fits anchor 3 ('some relevant keywords but missing common variations or synonyms'), not anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

Naming the specific tool ('Google AI Studio (Gemini)') and the distinctive niche ('imagens humanizadas', 'estilo influencer ou educacional') makes it mostly distinct, though it could overlap with closely related general image-generation skills. It fits anchor 4 rather than anchor 5 because the trigger terms are not distinctive enough to fully eliminate overlap with generic image-generation skills.

4 / 5

Total

13

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
sickn33/agentic-awesome-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.