CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

satellite-rig

Set up and repair thin joelclaw satellite Machines such as blaine/Dark-Tower. Use when adding joelclaw CLI, Typesense access, session search/capture, Central relay, or satellite health on non-Panda machines. Triggers: satellite, blaine, Dark-Tower, setup joelclaw on another machine, Typesense access on satellite, joelclaw satellite health.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/satellite-rig/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 lean, well-written policy/safety contract that respects token budget completely, but it provides almost nothing executable: no commands, paths, or concrete procedure steps for setup, repair, or verification. As an instruction-only skill its guidance stops at the conceptual level, which is the main quality gap.

Suggestions

Add concrete executable anchors: the actual path or invocation of the 'satellite bootstrap/repair installer', the location of the topology/placement contract and endpoint resolver, and example commands for the verification checks (reachability, CLI availability, capture admission, outbox progress, backup receipts).

Convert the prose into a short numbered workflow (verify identity → run installer → validate health/capture/backup → report) with explicit validation checkpoints and a stop-and-report feedback loop for destructive diffs.

Add section headers (e.g. 'Safety rules', 'Verification', 'Reporting') so the safety constraints and operational steps are scannable, and either link or name-with-path the external contracts the body references.

DimensionReasoningScore

Conciseness

The body is ~350 words of dense prose with zero padding and no explanation of concepts Claude already knows; every sentence adds domain-specific constraints the model could not infer. This matches anchor 5 ('every token earns its place') and is clearly better than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

The guidance is high-level throughout: "Use the repository's satellite bootstrap/repair installer after inspecting its live help", "Discover Central URLs from the endpoint resolver" — no commands, file paths, script names, or executable steps are given, so a reader cannot execute anything concrete from this text. It is slightly above anchor 1 (it does enumerate concrete verification areas like capture admission, outbox progress, and backup receipts) but fits anchor 2's 'high-level hints but missing the specific steps to execute'.

2 / 5

Workflow Clarity

A rough sequence is implied (read topology contract → verify identities → run installer → verify health/capture/backup → report) and stop conditions exist ("Stop on an unexpected target or destructive diff"), but the steps are prose-implicit rather than listed and validation checkpoints are named as categories rather than executable checks. Since the skill involves repair of live machines (destructive risk) with only vague verification, it cannot exceed 3 per the destructive-operation cap.

3 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files, so no file splitting is required, but it lacks section headers and cites unnamed resources ("the current topology/placement contract", "the scoped session evidence contract", "the endpoint resolver") without paths or links, so navigation is not well signaled. This fits anchor 3 ('some structure, references present but not clearly signaled') better than the well-organized anchor-5 case.

3 / 5

Total

13

/

20

Passed

Description

87%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 a strong example: it states a clear what and an explicit when, with concrete capability areas and domain-specific trigger phrases. The only notable weakness is that the 'Triggers:' list is redundant with the 'Use when' clause rather than broadening keyword coverage with synonyms.

DimensionReasoningScore

Specificity

"Set up and repair thin joelclaw satellite Machines" names the domain and verbs, and the when-clause enumerates concrete capability areas ("joelclaw CLI, Typesense access, session search/capture, Central relay, or satellite health") with a named example host (blaine/Dark-Tower). It falls short of anchor 5 because the action verbs cover only setup/repair and leave minor gaps in coverage, but it is well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

It clearly answers "what" ("Set up and repair thin joelclaw satellite Machines such as blaine/Dark-Tower") and explicitly answers "when" with concrete trigger phrases ("Use when adding joelclaw CLI, Typesense access, ... on non-Panda machines"), matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Phrases like "setup joelclaw on another machine", "Typesense access on satellite", and "joelclaw satellite health" are natural things a user would say. However, the explicit "Triggers:" list largely duplicates the "Use when" clause rather than adding synonyms or variations, leaving a few natural terms uncovered, which matches anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous ("thin joelclaw satellite Machines such as blaine/Dark-Tower ... on non-Panda machines") with triggers specific to this domain, so it is clearly distinguishable from other skills with minimal conflict risk. It is not merely 'somewhat specific' as at anchor 3; no other generic skill would trigger on these terms.

5 / 5

Total

18

/

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/satellite-rig/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.