CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

local-convex

Operate Joel's local self-hosted Convex setup with Central Postgres and NAS-backed Garage/S3-compatible object storage. Use when: 'local convex', 'self-hosted convex', 'Convex S3', 'Convex Garage', 'Garage', 'Convex MinIO', 'Convex buckets', 'run Convex locally', or any task wiring/debugging the local Convex runtime.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 excellent operational runbook: fully executable commands with expected outcomes, a validated operating sequence, and dense environment-specific facts with no filler. Its main weakness is structure — everything, including two legacy storage paths and deep proxy implementation notes, is inlined in one long SKILL.md instead of being split into clearly signaled reference files.

Suggestions

Move the legacy custom-MinIO and ASUSTOR CE topology, env, and health-check sections into a references/legacy-storage.md file, keeping only a one-line 'rollback/reference path, see ...' pointer in the body.

Extract the 'Selective Exposure' proxy implementation details (installer, tests, allowlist config, LaunchDaemon history) into a references/origin-proxy.md, leaving the exposure model and check commands in SKILL.md.

Deduplicate the Garage paths and installer behavior: the 'Garage Operations' bullet list restates the data/meta/snapshot paths already listed in 'Current Local Topology' — keep one authoritative copy and reference it.

DimensionReasoningScore

Conciseness

Nearly every line is non-derivable environment state (IPs, ports, paths, auth modes, gotchas) with essentially zero explanation of concepts Claude already knows, so the token spend is justified. Minor trimming opportunities keep it below anchor 5: Garage data/meta/snapshot paths are restated in both 'Current Local Topology' and the 'Garage Operations' installer bullet list, and full topology sections are inlined for the non-canonical custom MinIO and ASUSTOR CE rollback paths.

4 / 5

Actionability

Guidance is copy-paste executable throughout: exact health-check commands with expected outcomes ("a `403 AccessDenied` response from `/` proves the API is reachable"), the full env var shape with credential sources named, concrete psql/ssh/tailscale/launchctl commands, and specific exposure-check curl commands including the foreign-Origin 403 test. Placeholders like `<host-tailnet-ip>` are appropriately host-dependent rather than pseudocode.

5 / 5

Workflow Clarity

The 'Operating Sequence' gives a clear 8-step checklist with explicit validation checkpoints (verify Garage reachability on 39100, verify env points at Garage by IP, confirm Central Postgres, run a Convex-level smoke test) that map to concrete commands defined earlier. Error-recovery guidance is present (back off after `kex_exchange_identification`, prefer the brain note when sources disagree, 403-as-healthy expectations), satisfying the feedback-loop requirement for the database and infra operations involved.

5 / 5

Progressive Disclosure

The body has a clean section hierarchy, but it is a ~280-line monolith with no bundle files: the legacy custom-MinIO and ASUSTOR CE topology/health-check sections and the deep 'Selective Exposure' proxy implementation detail (LaunchDaemon history, allowlist plumbing, test paths) are exactly the kind of long, secondary material the rubric expects split into one-level-deep reference files. It sits above anchor 2 because the structure and canonical-vs-legacy labeling are genuinely good, but below anchor 4 because substantial content that should be separate is inline.

3 / 5

Total

17

/

20

Passed

Description

95%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 description that states a clear, specific 'what' and an explicit, multi-phrase 'Use when' clause with good synonym coverage. It is unmistakably scoped to one personal infrastructure niche, so mis-triggering risk is low; the only mild weakness is that 'operate' is a broad verb and the full range of concrete operations is not enumerated.

DimensionReasoningScore

Specificity

The description names the domain and concrete components ("local self-hosted Convex setup with Central Postgres and NAS-backed Garage/S3-compatible object storage") plus actionable verbs ("Operate", "wiring/debugging the local Convex runtime"). It falls just short of anchor 5 because the capability list is not comprehensive — 'operate' is broad and the individual operations (deploy, smoke-test, expose, migrate storage) are only implied rather than enumerated.

4 / 5

Completeness

It explicitly answers both questions: 'what' ("Operate Joel's local self-hosted Convex setup with Central Postgres and NAS-backed Garage/S3-compatible object storage") and 'when' ("Use when: 'local convex', 'self-hosted convex', ... or any task wiring/debugging the local Convex runtime"). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

It lists eight explicit natural trigger phrases including synonyms users would actually say: 'local convex', 'self-hosted convex', 'run Convex locally', 'Convex S3', 'Convex Garage', 'Garage', 'Convex MinIO', 'Convex buckets'. Coverage of the niche's natural vocabulary is comprehensive; no anchor-4 gap (missing common variations) is identifiable.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Joel's specific local self-hosted infrastructure with named storage backends — so it is clearly distinguishable from generic Convex, S3, or Postgres skills. The only minor overlap risk is the bare trigger 'Garage' (which could match generic Garage-the-S3-store discussions), but that is the intended trigger, keeping conflict risk minimal.

5 / 5

Total

19

/

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/local-convex/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.