CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

garage

Operate Joel's Garage S3-compatible object storage on three-body. Use for Garage, Convex Garage, Garage S3, three-body Garage, port 39100, Garage buckets, and MinIO-to-Garage migration.

Quality

84%

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

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.

An exemplary operational runbook: every command is concrete and executable, environment-specific facts (IPs, ports, paths, bucket names) are recorded precisely, and destructive operations carry explicit authorization and redaction rules. The Operating Sequence includes real verification checkpoints including a workload-level smoke test. Remaining weaknesses are minor: a few duplicated facts across sections and no explicit failure-handling branch in the main sequence.

Suggestions

Deduplicate repeated facts — state 'Garage does not support anonymous S3 access; 403 from / is expected' once (Gotchas) and reference it from Health Checks, and list the installer path once (Canonical Sources) to tighten conciseness toward a 5.

Add a short failure branch to the Operating Sequence (e.g. 'If reachability or the smoke fails: check Gotchas, back off SSH before retrying, re-verify with redaction-safe checks before changing state') to complete the validation feedback loop.

Consider moving the health-check command catalog into a references/ file, keeping only the two canonical checks inline, to improve progressive disclosure now that the single file has grown past 200 lines.

DimensionReasoningScore

Conciseness

The body is dense with facts Claude cannot know (tailnet IP, ports 39100/39000/29990, bucket names, NAS paths, SSH-brittleness rules) and explains no general concepts — every section is operational. It falls short of 5 only through minor duplication: the installer path appears twice (Current Topology and Canonical Sources), and 'Garage does not support anonymous S3 access; 403 AccessDenied' is stated verbatim in both Health Checks and Gotchas. This fits 'Efficient; minor instances of over-explanation that could be trimmed' (4); it is clearly above 3 because there is no padded explanation, only repetition of already-earned facts.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: the read-only SSH probe (`ssh -o BatchMode=yes -o ConnectTimeout=8 joel@three-body 'uptime; pwd'`), network health checks (`nc -vz -w 5 100.67.156.41 39100`), redaction-safe env checks with exact awk patterns, `sudo docker compose ps/logs` commands, the complete Convex env shape with concrete values, and the smoke script invocation `./smoke-self-hosted-convex.sh`. This matches the 5 anchor ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases') and is above 4 because the commands cover the common health-check, env-validation, and smoke-test cases comprehensively rather than with minor gaps.

5 / 5

Workflow Clarity

The 'Operating Sequence' is a clear numbered 7-step flow with explicit verification checkpoints (verify reachability on 39100, validate the redacted env shape, confirm the runtime env endpoint, run the Convex smoke, verify the export ZIP contains 'custom-garage' and the endpoint), and risky operations are guarded ('Do not delete buckets or objects without explicit authorization and a backup/recovery note', 'Inspect first. Summarize risk before changing service state'). It is not a 5 because the sequence lacks an explicit failure-feedback loop — no instruction for what to do when a checkpoint fails — though partial recovery guidance exists elsewhere ('Back off after kex_exchange_identification...', 'If sources disagree, prefer the brain project note, then verify live state'), so it sits at 'Clear sequence with most checkpoints present; minor validation gaps' (4) rather than 3, which would require missing checkpoints or absent validation for destructive operations.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so this is a single-file skill; scoring reflects the actual structure. Section organization is strong and navigable (When To Use, Current Topology, Canonical Sources, Safety, NAS Access Rules, Health Checks, Buckets, Env Shape, Operating Sequence, Gotchas), and external pointers (brain project note, compose file, redacted env) are one level deep and clearly signaled in a dedicated Canonical Sources section with a precedence rule. It is not a 5 because the under-50-lines exception does not apply (~210 lines) and some content — notably the multi-command health-check catalog and the secret-redaction listings — is inline reference material that could be split into a references file, fitting 'Good structure; most content is appropriately placed; minor organization gaps' (4) rather than 3, since the inline content is operational essentials rather than a misfiled API dump.

4 / 5

Total

17

/

20

Passed

Description

81%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, explicit trigger-oriented description: it answers what and when clearly, uses third-person imperative voice, and covers an unusually rich set of natural trigger terms including port and host identifiers. The main weakness is that the capability statement is a single generic verb ('Operate') with no concrete actions, leaving the reader to infer what the skill actually does from the trigger list.

Suggestions

Expand the capability statement with 2-3 concrete actions, e.g. 'Operate Joel's Garage S3-compatible object storage on three-body: run health checks, provision and verify Convex buckets, wire Convex S3 env, and perform MinIO-to-Garage migration.'

Keep the 'Use for...' trigger list as-is — it is the description's strongest asset; the fix is to the 'what', not the 'when'.

DimensionReasoningScore

Specificity

The only stated action is "Operate Joel's Garage S3-compatible object storage on three-body" — the domain is named precisely, but 'Operate' is a single generic verb with no concrete sub-actions (no mention of what operating entails, e.g. provisioning buckets, wiring env, running smoke checks as actions rather than trigger words). This matches 'Names the domain but actions are minimal or generic' (2) rather than 3, since the remaining phrases are triggers ('Use for Garage, Convex Garage...') rather than descriptions of actions the skill performs.

2 / 5

Completeness

It explicitly answers both questions: what ("Operate Joel's Garage S3-compatible object storage on three-body") and when ("Use for Garage, Convex Garage, Garage S3, three-body Garage, port 39100...") with concrete trigger phrases. This is structurally identical to the 5 anchor example ('Extract text and tables from PDF files... Use when working with PDF files or when the user mentions...'), and clearly above 4 because the 'when' clause is explicit and enumerates specific triggers rather than being merely adequate.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive for this niche and includes synonyms and concrete identifiers users would naturally say: "Garage", "Convex Garage", "Garage S3", "three-body Garage", "port 39100", "Garage buckets, keys, env wiring, smoke tests, or MinIO-to-Garage migration". This matches the 5 anchor ('comprehensive coverage of natural terms including synonyms') — port numbers and host-specific variants function like file extensions do in the exemplar.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and mostly distinct — 'three-body', '39100', and 'MinIO-to-Garage migration' are highly specific — but terms like 'Garage buckets, keys' and the MinIO mention create minor overlap risk with a generic S3/MinIO skill (the body confirms separate `minio`, `local-convex`, and `three-body` skills exist in this environment). This fits 'Mostly distinct; minor overlap risk with closely related skills' (4); it is not a 5 because the migration/keys phrasing could plausibly route a user to the adjacent MinIO skill.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/garage/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.