CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-system-bus

Deploy the system-bus-worker to the joelclaw Kubernetes cluster from local machine. Use when syncing changes in packages/system-bus to k8s, especially because the GitHub Actions deploy job targets a non-existent self-hosted runner and cannot complete deploys automatically.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable deployment skill with excellent workflow clarity and concrete commands throughout. Its main weakness is length — the Talon rebuild section and restart safety details add significant bulk that could be split into separate files for better progressive disclosure. The troubleshooting table is exceptionally well-structured and practical.

Suggestions

Extract the Talon rebuild section (including SECRET_MAPPINGS and key paths) into a separate TALON.md file, referenced with a one-line link from the main skill.

Consider moving the Restart Safety (ADR-0156) explanation to a separate file or trimming it to just the critical rule about retries, since the detailed mechanics are supplementary context.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good use of tables and code blocks, but includes some content that could be trimmed — the Restart Safety section with its detailed explanation of Inngest retry mechanics and memoization is somewhat verbose for Claude, and the Talon rebuild section is extensive enough to warrant its own file. The SECRET_MAPPINGS table and Talon key paths add bulk that could be referenced externally.

2 / 3

Actionability

Excellent actionability throughout — every step has concrete, copy-paste-ready commands. The quick deploy path is a single command, manual fallback steps are fully executable with real paths and image names, and the Talon rebuild section provides a complete numbered sequence with exact commands. The troubleshooting table maps specific error messages to specific fixes.

3 / 3

Workflow Clarity

The primary workflow is crystal clear: one script handles everything with explicit steps enumerated (build → auth → push → apply → rollout → health probe). Manual fallback steps are clearly sequenced. The Talon rebuild has a numbered 6-step process with validation at the end. The deploy safety section explains what happens during failures with a clear retry flow diagram. Post-deploy verification steps serve as explicit validation checkpoints.

3 / 3

Progressive Disclosure

The skill has good structural organization with clear headers and sections, but it's quite long (~180 lines of substantive content). The Talon rebuild section, SECRET_MAPPINGS table, and restart safety details could reasonably be split into separate referenced files. The Key Paths table at the end references many files but the skill itself is monolithic. However, for a skill with no bundle files, the inline organization is reasonable.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that clearly identifies a specific deployment task, includes natural trigger terms covering both full names and abbreviations (Kubernetes/k8s), and explicitly states both what the skill does and when to use it. The additional context about why local deployment is necessary (broken GitHub Actions runner) adds valuable disambiguation. The description uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists a specific concrete action ('Deploy the system-bus-worker to the joelclaw Kubernetes cluster from local machine') and explains the context of why this is needed (GitHub Actions deploy job targets a non-existent self-hosted runner). Very specific to a particular deployment workflow.

3 / 3

Completeness

Clearly answers both 'what' (deploy system-bus-worker to joelclaw Kubernetes cluster from local machine) and 'when' ('Use when syncing changes in packages/system-bus to k8s, especially because the GitHub Actions deploy job targets a non-existent self-hosted runner'). Explicit 'Use when' clause is present with clear trigger conditions.

3 / 3

Trigger Term Quality

Includes highly relevant natural keywords: 'deploy', 'system-bus-worker', 'joelclaw', 'Kubernetes', 'k8s', 'packages/system-bus', 'GitHub Actions', 'self-hosted runner'. A user needing this skill would naturally use terms like 'deploy system-bus' or 'k8s deploy' which are well covered.

3 / 3

Distinctiveness Conflict Risk

Extremely specific to a particular service (system-bus-worker), a particular cluster (joelclaw), and a particular workaround scenario (non-existent self-hosted runner). Very unlikely to conflict with any other skill.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
joelhooks/joelclaw
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.