CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hermes-s6-container-supervision

Modify or debug s6 services in the Hermes Docker image.

Quality

73%

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 ./optional-skills/devops/hermes-s6-container-supervision/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is a strong operational reference: dense with project-specific facts, executable commands with expected outputs, and genuinely useful failure-mode diagnostics. Its main weaknesses are moderate verbosity in the architectural-history rationale and a couple of workflows missing explicit verification steps.

Suggestions

Add a verification step to the 'Add a new static service' recipe (e.g., check `s6-svstat` for the new service or `s6-rc -d list` after rebuild) so the workflow closes the loop.

Move the v1–v3 design history and the s6-overlay issue #477 rationale into a separate reference file (e.g., references/architecture-history.md) and keep a one-line pointer in SKILL.md.

Trim version- and date-specific details (s6-overlay v3.2.3.0, sample log timestamps) or consolidate them into a single 'environment facts' line to reduce token load.

DimensionReasoningScore

Conciseness

Nearly every section conveys project-specific mechanics Claude cannot know (the supervision tree, exit-code behavior, PATH quirks) with no padding about general Docker/s6 concepts. Minor trimming is possible — the 'Why Architecture B' rationale narrative and the v1–v3 history run long, and embedded version/date details (s6-overlay v3.2.3.0, log timestamps) add tokens without guidance value — so it sits at 4 rather than 5.

4 / 5

Actionability

Commands are copy-paste ready with expected outputs: `docker exec <c> /command/s6-svstat ...` with interpretation of all three output states, exact `s6-svc -u/-d/-t` invocations, exact file paths and function names (`S6ServiceManager._render_run_script`, `02-reconcile-profiles`), and a test harness command with expected result ('19 passed, 0 xfailed'). This is fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Recipes are clearly sequenced with most checkpoints present — the inspect/svstat recipe decodes expected outputs, the run-command recipe points at the test assertion to update, and pitfall sections give explicit error-recovery paths (crash loop → run `hermes -p <profile> setup`, missing slots → check reconciler log). A 5 is withheld because some workflows lack an explicit verify step, e.g., 'Add a new static service' ends at file creation without telling the reader to confirm the service came up.

4 / 5

Progressive Disclosure

As a single-file skill (no bundle files exist), it is well organized with clear sections — when-to-use, an architecture overview, a key-files table, recipes, and pitfalls — and zero nested references. Minor gaps keep it at 4: the 'Why Architecture B' historical rationale and the long pitfalls catalog are candidates for a separate reference file in a skill of this length, which would leave SKILL.md as a leaner overview.

4 / 5

Total

17

/

20

Passed

Description

57%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 short, accurate, and unambiguous about its niche, but it undersells the skill's scope and provides no explicit trigger guidance. Adding a 'Use when...' clause and naming one or two concrete capabilities (e.g., gateway service registration, boot-script reconciliation) would materially improve it.

Suggestions

Add an explicit 'when' clause, e.g.: "Use when a profile gateway isn't starting or surviving docker restart, when adding a static s6 service, or when editing cont-init.d boot scripts in the Hermes image."

Name the concrete actions the skill supports instead of the generic 'modify or debug' — e.g., register/unregister per-profile gateway services, add static supervised services, diagnose crash-looping services with s6-svstat.

Include natural user-facing trigger terms such as 'container', 'supervision', 'service won't start', and 'docker restart' so the description matches how users actually phrase these problems.

DimensionReasoningScore

Specificity

"Modify or debug s6 services" names the domain (s6, Hermes Docker image) and exactly two broad actions (modify, debug), matching the '1-2 concrete actions, not comprehensive' anchor. It falls short of 4 because it omits the specific operations the skill actually covers (register/unregister profile gateways, cont-init.d boot scripts, supervision diagnostics).

3 / 5

Completeness

The 'what' is clear ("Modify or debug s6 services in the Hermes Docker image") but there is no 'when' — no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Relevant keywords like "s6", "services", "Docker", and "debug" are present, but common natural variations a user would say are missing: "container", "supervision", "gateway not starting", "docker restart". Not 4 because coverage is thin with no synonyms or related phrasing beyond the two technical nouns.

3 / 5

Distinctiveness Conflict Risk

"s6 services in the Hermes Docker image" carves out a clear niche with distinct triggers (s6, Hermes, Docker image) that no generic skill would claim. Not 4 because the overlap risk with related skills (e.g., a general Docker skill) is negligible given the doubly-qualified domain.

5 / 5

Total

14

/

20

Passed

Validation

75%

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

Validation — 12 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/devops/hermes-s6-container-supervision/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.