CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

executor

Operate Rhys Sullivan's Executor under Joel's Central launchd service. Use when Joel mentions executor, executor daemon, task executor, Central Executor, /Users/Shared/joelclaw/data/executor, port 4788, port 4789, dashboard access, or executor database options.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/executor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A strong operational runbook: concrete, executable commands with a well-validated install/apply/verify workflow and meaningful safety rules. Its weaknesses are duplicated URL catalogs that waste tokens and a monolithic single-file layout that inlines reference-style material.

Suggestions

Deduplicate the URL lists: the raw-daemon and dashboard URLs appear in both 'Current Central Contract' and 'LAN And Tailnet Exposure' — state them once and reference that section.

Move the exhaustive health-check command catalog and URL tables into a references/ file (e.g. references/diagnostics.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

The 'Current Central Contract' service-shape list and the 'Database And State' expected-files list overlap in path detail; consolidate the path inventory into one place.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no launchd/SQLite tutorials), but the raw-daemon and dashboard URL catalogs are each listed twice (service shape vs. LAN/Tailnet exposure sections), which is more than minor trimmable over-explanation.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — install dry-run, contract checks, sudo apply, launchctl print, bounded curl health checks, and narrow diagnostic commands with exact paths and ports.

5 / 5

Workflow Clarity

The install/apply/verify sequence is explicit with validation checkpoints at each stage (check-contract.sh --runtime before apply, curl and verify-executor-runtime.sh after), plus an error-recovery path for missing passwordless sudo ("do not fake success. Report the actual file and dry-run results").

5 / 5

Progressive Disclosure

Sections are clearly headed and well-ordered, but this is a ~245-line single file with no bundle references; the exhaustive URL lists and health-check command catalogs are inlined where a reference file could carry them, so structure is present but content is not split.

3 / 5

Total

16

/

20

Passed

Description

73%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 distinctive, well-triggered description with an explicit 'Use when' clause and concrete trigger identifiers. Its main weakness is a thin 'what' — a single generic action verb rather than an enumeration of the skill's concrete capabilities.

DimensionReasoningScore

Specificity

"Operate Rhys Sullivan's Executor under Joel's Central launchd service" names a highly specific domain but only one concrete action (operate/supervise), matching the 'domain and 1-2 concrete actions' anchor rather than the several-actions anchors above.

3 / 5

Completeness

Both parts are present — a clear 'what' ("Operate... under Joel's Central launchd service") and an explicit 'when' ("Use when Joel mentions...") with concrete triggers — but the 'what' is a single action and could enumerate more of what operating entails, keeping it below the fully comprehensive anchor.

4 / 5

Trigger Term Quality

Good keyword coverage with natural synonyms ("executor", "executor daemon", "task executor", "Central Executor") plus concrete identifiers ("port 4788", "port 4789", "/Users/Shared/joelclaw/data/executor"), but a few natural terms surfaced in the body ("launchd wiring", "executor state/logs", "rhyssullivan/executor") are missing from the trigger list.

4 / 5

Distinctiveness Conflict Risk

Proper nouns ("Rhys Sullivan's Executor", "Central launchd service") and specific ports and paths give this a clear niche with essentially no overlap risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/executor/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.