CtrlK
BlogDocsLog inGet started
Tessl Logo

apikey-image-gen

Generate or edit images through Hermes Web UI using the selected/requested profile's configured API-key image provider from config.yaml.

60

Quality

72%

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 ./packages/skills/apikey-image-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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 with an executable curl template and exact request/response examples, and the single-action workflow is clear with explicit error handling. The main weaknesses are a verbatim sentence repeated across three mode sections and a monolithic structure with no progressive offloading of reference material.

Suggestions

De-duplicate the per-mode provider note: state the provider-override behavior once (e.g. under Request Fields) and reference it from each mode instead of repeating the full sentence three times.

Consider moving the full request-field reference table into a references/ file (e.g. REQUEST_FIELDS.md) and linking to it, so the main body stays a concise overview.

DimensionReasoningScore

Conciseness

The body is mostly lean and reference-style without explaining basic concepts, but the sentence 'If provider, provider_name, or custom_provider is present, the server calls the requested provider's base URL instead.' is repeated verbatim across all three mode sections, which is avoidable token waste.

2 / 3

Actionability

Provides a fully executable curl template with real token/base-URL resolution logic and concrete JSON payloads, plus exact JSON request bodies per mode and a documented request-field table — copy-paste ready.

3 / 3

Workflow Clarity

For this single-action API skill the flow is unambiguous: numbered resolution orderings for base URL, token, and profile, followed by explicit error handling (stop and report on 401/403/connection failure) and response-code interpretation with corrective user guidance.

3 / 3

Progressive Disclosure

Content is well organized into clear sections (Modes, Request Fields, Curl Template), but it is a 194-line monolithic SKILL.md with no bundle files and no offloading of reference material; the request-field table and curl template are inline rather than split out.

2 / 3

Total

10

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 concise and concrete, naming specific actions and a distinctive mechanism, but it omits an explicit 'when to use' trigger clause and lacks breadth of natural trigger terms. Adding a 'Use when...' clause with common phrasings would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to generate or edit images, create an image from a reference image, or modify an existing image.'

Broaden natural trigger terms to include 'image generation', 'image editing', 'create image', and 'AI image' so the skill matches more user phrasings.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Generate or edit images') tied to a specific mechanism (Hermes Web UI via the profile's configured API-key image provider from config.yaml), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers 'what' (generate/edit images through Hermes Web UI's configured provider) but has no explicit 'Use when...' trigger clause; per the judging guidelines a missing trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes core natural verbs users would say ('generate', 'edit', 'images') but misses common variations like 'create image', 'AI image', 'picture', or 'image generation/editing', so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The narrow mechanism (configured API-key image provider from config.yaml via Hermes Web UI) defines a clear niche that is unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
EKKOLearnAI/hermes-studio
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.