CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

work-runners

Check macOS GHA runner status for the getditto org

Quality

77%

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 ./.agents/skills/work-runners/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tight, fully executable runbook: copy-paste-ready gh api commands, concrete output templates, and clearly sequenced steps with conditional reporting. The only minor gaps are the absence of any API-failure handling and hardcoded runner counts in the example output.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — it provides non-obvious facts ("Runner group ID 8 is the 'macOS' group in the getditto org") and exact output formats without padding. Minor trimmable instances remain, such as the redundant "# Check macOS GHA Runners" heading nested under "Command Template" and hardcoded runner counts ("34/34") in the sample output, keeping it below anchor 5.

4 / 5

Actionability

Both gh api commands with complete jq filters are copy-paste executable, and the report formats are fully specified down to the warning and clean-report variants. This matches anchor 5 ('fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

The sequence (fetch → report → optional detail) is clear with explicit conditional branches for offline runners and the all-online case, and the operation is read-only so the destructive/batch validation cap does not apply. It falls at anchor 4 rather than 5 because there is no guidance for handling API failures (auth, permissions, missing group) and the hardcoded '34' could mislead if the fleet size changes.

4 / 5

Progressive Disclosure

This is a short, single-purpose skill with no bundle files, and all content appropriately lives inline in well-organized sections. Per the rubric's simple-skill guidance, well-organized sections with no need for external references warrant anchor 5.

5 / 5

Total

18

/

20

Passed

Description

57%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 concise, specific to a well-defined niche, and clearly states what the skill does, but it lacks any 'when to use' trigger guidance and misses natural keyword variations like "GitHub Actions" or "self-hosted runners". Adding an explicit 'Use when...' clause with those synonyms would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks about macOS runners, GitHub Actions runner status, or CI capacity in the getditto org."

Include natural keyword variations and synonyms such as "GitHub Actions", "self-hosted runners", "CI", and "online/offline" so users' phrasing matches naturally.

Enumerate one or two more concrete capabilities (e.g., "counts online/offline/busy runners and flags offline machines") to strengthen specificity.

DimensionReasoningScore

Specificity

"Check macOS GHA runner status" names a concrete domain (macOS GHA runners, getditto org) and a single concrete action, matching the 'names domain and 1-2 concrete actions' anchor. It does not list several specific actions (e.g., counting online/offline/busy runners or reporting per-runner detail), so it falls short of anchor 4.

3 / 5

Completeness

The description clearly answers 'what' ("Check macOS GHA runner status for the getditto org") but contains no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is above anchor 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like "macOS", "GHA", "runner", "status", and "getditto" are present, but common variations and synonyms users might say ("GitHub Actions", "self-hosted runners", "CI", "online/offline") are missing. This matches anchor 3 ('some relevant keywords but missing common variations'), and not anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The scope is tightly pinned to "macOS GHA runner status for the getditto org" — a clear niche with distinct triggers and virtually no overlap risk with other skills. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk'), not anchor 4, since no plausible conflict with a closely related skill exists.

5 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phatblat/dotfiles

Path

.agents/skills/work-runners/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.