CtrlK
BlogDocsLog inGet started
Tessl Logo

inference-sh-cli

Run 150+ AI apps (image, video, LLM) via inference.sh CLI.

59

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/devops/cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 skill body is an efficient, highly actionable reference with a clean Search-Run-Parse workflow and excellent progressive disclosure via four real reference files, losing only a little on a missing failure-recovery loop and minor verbosity.

DimensionReasoningScore

Conciseness

The body is command-driven and lean, with each line earning its place; minor padding like 'raw output is hard to parse' and a few repetitive search examples keep it just below the fully lean anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready `infsh` commands with --json, concrete app IDs, and input JSON spanning image, video, upload, and search cases, matching the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

A clear numbered sequence (Search -> Run -> Parse) with prerequisites is present, but there is no explicit validate -> fix -> retry feedback loop on command failures, leaving it below the checkpoint-with-error-recovery anchor.

4 / 5

Progressive Disclosure

The body is a concise overview with a clear Reference Docs section signaling four one-level-deep references, all of which exist as real files in references/, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

18

/

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 clearly identifies the skill's domain and distinct niche via the inference.sh CLI, but lacks specific action verbs and any explicit 'when to use' trigger clause, capping completeness and trigger quality at the midpoint.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks to generate images or video, or mentions inference.sh, FLUX, Veo, or infsh.'

Replace generic categories with specific actions, e.g. 'Search the app catalog, run AI apps, and parse media URLs' instead of '(image, video, LLM)'.

Include natural user phrasings and synonyms (generate images, FLUX, Veo, video generation) as trigger terms alongside the brand name.

DimensionReasoningScore

Specificity

Names the domain ('Run 150+ AI apps') and two broad action categories ('image, video, LLM') but lists no specific actions like search, run, or parse, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

States a clear 'what' (run 150+ AI apps via inference.sh CLI) but provides no 'Use when...' trigger clause, so per the missing-trigger-guidance cap it lands at the 'clear what but when missing' anchor.

3 / 5

Trigger Term Quality

Includes relevant keywords ('AI apps', 'image, video, LLM', 'inference.sh CLI') but omits the natural verbs and synonyms users actually say ('generate images/video', 'FLUX', 'Veo'), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'inference.sh CLI' brand niche is distinct with minimal conflict risk, but triggers lean on the brand name rather than task phrasings, placing it just below the 'clear niche with distinct triggers' anchor.

4 / 5

Total

13

/

20

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
NousResearch/hermes-agent
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.