CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-graph

Use when the user types /hep-graph or asks to create, list, inspect, or request a run of an Agentlas automation graph.

Quality

87%

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

The canonical home for this skill is hephaestus-graph in agentlas-ai/Agentlas-OS

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary instruction-only skill body: lean, fully executable, with a well-sequenced per-command workflow, explicit error and authority rules, and appropriate self-contained structure for its size. The only improvement vector is upstream (the description), not the body itself.

DimensionReasoningScore

Conciseness

Every line earns its place: a 2-line context preamble that establishes the requested-vs-executed distinction, a copy-paste CLI resolver, a terse argument-to-command map, and error-handling rules. No padding, no explaining concepts Claude already knows, no verbosity anywhere.

5 / 5

Actionability

Fully executable guidance: the bash block resolves the CLI with concrete fallback paths and a working install hint, and every command maps to an exact invocation (`"$CLI" graph list`, `graph show "<name>"`, `graph new "<request>"`, `graph run "<name>" -y` with `--input "<value>"`). Output expectations per command are specified, covering all cases the description promises.

5 / 5

Workflow Clarity

The run flow is explicitly sequenced with checkpoints: show the graph first, obtain any missing required input without inventing it, then run with -y; a single user run request is the authority. Error handling is defined ("On any non-zero exit, relay the exact refusal and stop; do not retry with a guess") and the interview flow for `new` specifies that the save confirmation is approval. Each sub-command's sequence is unambiguous.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external reference files, and no bundle files exist to link. The two sections ("Resolve the independent Agentlas CLI", "Commands") are well-organized, flat, and each fully delivers its content inline — matching the rubric's exception for short single-purpose skills.

5 / 5

Total

20

/

20

Passed

Description

70%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.

A strong, tight trigger-focused description with a clear niche and good natural phrasing, but it lacks an independent statement of what the skill does — the capabilities exist only inside the 'Use when' clause. Adding a leading capability sentence would complete it.

Suggestions

Prepend a 'what' sentence before the trigger clause, e.g., "Create, list, inspect, and request runs of Agentlas automation graphs via the Agentlas CLI; runs are picked up by Agentlas Desktop rather than executed here."

Add common user synonyms to the trigger clause — "show/view a graph", "display my graphs", "run my automation" — to broaden natural-term coverage.

Clarify the run semantics in the description itself (runs are requested, not executed) so users are not misled about outcomes.

DimensionReasoningScore

Specificity

The description names the domain ("Agentlas automation graph") and enumerates several concrete operations ("create, list, inspect, or request a run"). It falls just short of the comprehensive anchor because the actions are generic verbs with no detail about what each entails, and operations like showing a graph are only implied via "inspect".

4 / 5

Completeness

The 'when' is explicit and strong ("Use when the user types /hep-graph or asks to..."), but the 'what' is never independently stated — the skill's capabilities only appear embedded in the trigger clause, and nothing says what the skill actually does (e.g., that it drives the Agentlas CLI and only requests runs). This sits between the 'when-only' anchor (2) and the both-clearly-present anchor (4).

3 / 5

Trigger Term Quality

Good keyword coverage: the explicit slash command "/hep-graph" plus natural user phrasings around creating, listing, inspecting, and running a graph. Common synonyms such as "show", "view", "display", or "automation" variants are missing, keeping it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"Agentlas automation graph" is a distinct proprietary niche plus an unambiguous explicit command ("/hep-graph"), so the risk of triggering the wrong skill is minimal.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agentlas-ai/Agentlas-OS

Path

.agents/skills/hephaestus-graph/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.