depot-github-runners

Configures Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners. Use when setting up or migrating GitHub Actions workflows to use Depot runners, choosing runner sizes (CPU/RAM), configuring runs-on labels, setting up ARM or Windows or macOS runners, troubleshooting GitHub Actions runner issues, configuring egress filtering, using Depot Cache with GitHub Actions, or running Dagger/Dependabot on Depot runners. Also use when the user mentions depot-ubuntu, depot-windows, depot-macos runner labels, or asks about faster/cheaper GitHub Actions runners. Not for Depot CI, the separate engine that reads .depot/workflows/ — that is the depot-ci skill.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

82%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 dense, highly actionable reference: executable labels, pricing, commands, and a troubleshooting table with minimal verbosity. Its main gap is the absence of explicit validation checkpoints in the Setup workflow, and some reference-grade tables could live in a bundle file to lighten the overview.

Suggestions

Add a validation checkpoint to Setup (e.g., confirm the Depot GitHub App is installed and the runner group permits the repo) before step 3 'Update runs-on', so migrations don't silently fail.

Trim the restated 'drop-in replacement — change the runs-on label' opening line, since that framing already appears in the frontmatter description.

Consider moving the full label/pricing tables into a references/ file and keeping only the most common sizes inline, reducing token load while preserving the overview.

Dimension	Reasoning	Score
Conciseness	Mostly lean and information-dense (pricing/label/troubleshooting tables, copy-paste YAML) with no padding about concepts Claude already knows; the only slack is the opening line re-stating the 'drop-in replacement' framing already in the description.	4 / 5
Actionability	Fully executable guidance throughout: exact `runs-on` labels with CPU/RAM/price, copy-paste migration YAML, `depot org show/list/switch` commands, ACL JSON examples, and a troubleshooting table with specific fixes — covers the common cases copy-paste ready.	5 / 5
Workflow Clarity	Setup is a clear numbered sequence and the Org Context Check + Common Mistakes + Troubleshooting tables provide error-recovery guidance, but there are no explicit validation checkpoints (e.g., confirm the GitHub App install or runner-group access before migrating).	4 / 5
Progressive Disclosure	Well-organized into clear section headers with one-level-deep, clearly signaled references (the sibling skill reference and two depot.dev doc URLs); the inline pricing/label tables are appropriate core reference data, though the skill is fairly long with most material inline.	4 / 5
	Total	17 / 20 Passed

Description

100%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 strong, third-person description that crisply states the capability, enumerates concrete use-case triggers, names the literal runner labels users will say, and explicitly fences off the related depot-ci skill. It hits every dimension of the rubric with little to trim.

Dimension	Reasoning	Score
Specificity	Names the domain and lists many concrete actions — 'choosing runner sizes (CPU/RAM)', 'configuring runs-on labels', 'setting up ARM or Windows or macOS runners', 'configuring egress filtering', 'using Depot Cache', 'running Dagger/Dependabot' — covering the skill comprehensively.	5 / 5
Completeness	Explicitly answers both 'what' ('Configures Depot-managed GitHub Actions runners as a drop-in replacement') and 'when' ('Use when setting up or migrating...', 'Also use when the user mentions...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — 'faster/cheaper GitHub Actions runners', 'GitHub Actions runner issues' — plus the concrete labels 'depot-ubuntu, depot-windows, depot-macos' as direct triggers, giving comprehensive keyword coverage.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche and actively disambiguates the sibling skill: 'Not for Depot CI, the separate engine that reads .depot/workflows/ — that is the depot-ci skill', minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: PostHog/posthog
Path: .agents/skills/depot-github-runners/SKILL.md
Commit: 130f3a1

Reviewed: 9 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.