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.
92
88%
Does it follow best practices?
Impact
100%
2.77xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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 strong, well-crafted skill description that clearly identifies a specific deployment task, names the exact service and target cluster, and provides explicit trigger conditions including the rationale for manual deployment. The description is concise yet comprehensive, with natural trigger terms and a clear 'Use when' clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists a specific concrete action: deploying the system-bus-worker to a named Kubernetes cluster (joelclaw) from local machine. It also explains the context of why this is needed (GitHub Actions deploy job targets a non-existent self-hosted runner). | 3 / 3 |
Completeness | Clearly answers both 'what' (deploy system-bus-worker to joelclaw Kubernetes cluster from local machine) and 'when' (when syncing changes in packages/system-bus to k8s, especially because GitHub Actions deploy job cannot complete). The 'Use when' clause is explicit. | 3 / 3 |
Trigger Term Quality | Includes highly specific natural keywords a user would say: 'deploy', 'system-bus-worker', 'joelclaw', 'Kubernetes', 'k8s', 'packages/system-bus', 'GitHub Actions', 'self-hosted runner'. These are precise terms that match real user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific to a particular service (system-bus-worker), a particular cluster (joelclaw), and a particular workflow context (GitHub Actions failure). Very unlikely to conflict with any other skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 concrete commands and clear workflows. Its main weakness is length — the Talon rebuild section and restart safety details add significant content that could be split into referenced files, improving both conciseness and progressive disclosure. The troubleshooting table and key paths sections are well-structured and valuable.
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.
Trim the 'Restart Safety' section to 2-3 sentences summarizing the key rule (never set retries: 0) and link to ADR-0156 for the full explanation, removing the flow diagram and long-running steps discussion.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but includes some sections that could be trimmed — the 'Restart Safety' explanation is quite detailed for something Claude can infer, and the Talon rebuild section adds significant length for what could be a separate file. The SECRET_MAPPINGS table and detailed restart safety flow diagram add bulk. | 2 / 3 |
Actionability | Excellent actionability throughout — every step has concrete, copy-paste-ready commands. The quick deploy is a single script invocation, manual fallback steps are fully executable with real paths and commands, and the troubleshooting table maps specific errors to specific fixes. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: the script handles 7 numbered steps with built-in validation (rollout wait + health probe). Manual fallback steps are clearly ordered. The post-deploy verification section provides explicit validation commands. The Talon rebuild section has a clear 6-step sequence with verification at the end. | 3 / 3 |
Progressive Disclosure | The skill starts with a quick deploy section which is good progressive disclosure, but the Talon rebuild section (adding secrets, changing supervision) is substantial enough to warrant its own file. The SECRET_MAPPINGS table and Talon key paths could be in a referenced TALON.md. References to ADRs are well-signaled but the inline content is heavy for a single SKILL.md. | 2 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- joelhooks/joelclaw
- Commit
03f0a59
- 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.