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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

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 unusually actionable, well-sequenced ops runbook with strong validation and error-recovery guidance throughout. Its main weakness is monolithic structure: everything, including tangential Talon supervision details and secret mapping tables, lives inline in SKILL.md.

Suggestions

Move the Talon Rebuild section (SECRET_MAPPINGS table, key paths, codesign gotcha) into a separate reference file (e.g. references/talon.md) and link to it one level deep, keeping SKILL.md focused on the deploy workflow.

Relocate time-sensitive version details ("Talos v1.12.4 / k8s v1.35.0", v2.1.0) into a small environment/config note so the body stays stable as versions change.

Consider splitting the Common Gotchas table into a troubleshooting reference if the skill grows, or at minimum cross-link each gotcha to the section of the workflow where the failure occurs.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with essentially no explanation of concepts Claude already knows, but version-stamped details ("Talos v1.12.4 / k8s v1.35.0") and the ~60-line Talon rebuild section extend beyond the deploy core and could be trimmed.	4 / 5
Actionability	Every workflow is copy-paste ready: the publish script invocation, manual build/push/rollout commands with exact flags (--platform linux/arm64, --timeout=180s), verification commands, and the numbered Talon rebuild steps with file paths.	5 / 5
Workflow Clarity	Sequencing is explicit (Quick Deploy, a 7-step script breakdown, Post-Deploy Verification, Manual Steps fallback) with validation checkpoints (rollout status wait, pod health probe, joelclaw status/refresh) and a gotchas table providing error-recovery feedback loops.	5 / 5
Progressive Disclosure	The body is a single well-sectioned ~190-line file with no external reference files; content such as the Talon rebuild procedure and the SECRET_MAPPINGS table is inlined where a separate one-level-deep reference would fit better, matching the 'some structure, content that should be separate is inline' anchor.	3 / 5
	Total	17 / 20 Passed

Description

82%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 tightly scoped, third-person description that clearly states what the skill does and gives an explicit 'Use when' clause with concrete, natural triggers tied to a specific repo and cluster. The only gap is that it describes a single action rather than enumerating several capabilities.

Dimension	Reasoning	Score
Specificity	"Deploy the system-bus-worker to the joelclaw Kubernetes cluster from local machine" names the domain and one concrete action with precision, but does not enumerate several specific actions, so it falls short of the anchor-4 example listing multiple capabilities.	3 / 5
Completeness	It explicitly answers what ("Deploy the system-bus-worker to the joelclaw Kubernetes cluster from local machine") and when ("Use when syncing changes in packages/system-bus to k8s") with concrete trigger phrases, matching the top anchor; a weaker 'when' would only justify a 4.	5 / 5
Trigger Term Quality	"Use when syncing changes in packages/system-bus to k8s" supplies natural trigger terms including the "k8s" synonym and the repo path, but variants like "publish" or "push the worker image" are absent, matching good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	"system-bus-worker", "joelclaw", and "packages/system-bus" establish a clear niche with distinct triggers and minimal conflict risk against any generic deploy skill.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/sync-system-bus/SKILL.md
Commit: aa0116c

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.