CtrlK
BlogDocsLog inGet started
Tessl Logo

setting-up-devbox

Starts, connects to, and troubleshoots a PostHog devbox, a remote Coder workspace for PostHog development that can also run the full stack, through `hogli devbox:*` commands. Use when asked to spin up or resume a devbox, open a shell or editor on it, run a command on it, mirror a local checkout to it (devbox:sync), run the PostHog app on it and share a link, clone, update, share, or free disk on a devbox, store gh or Claude Code tokens for it, or diagnose a failing devbox command (tailnet, DNS, Coder CLI version, SSH). Not for running the stack on the local machine or for changing the Coder template in posthog-cloud-infra.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 exceptionally operational, lean skill body with executable commands, a clear sequenced workflow, and real validation/feedback loops around destructive operations. The one gap is that two referenced bundle files are cited but missing from disk.

Suggestions

Create the referenced references/access-troubleshooting.md and references/sync.md (or remove the links) so the progressive-disclosure pointers resolve to real files.

If access-troubleshooting and sync detail is small, consider inlining the essentials and dropping the external references to make the skill self-contained.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific, non-obvious operational facts Claude would not know ('~/.hogli/bin is not on PATH', 'A non-login shell doesn't reliably load the shell profile', region/label naming, --start-app persistence) and never re-explains what a devbox, Coder, or PostHog is — every token earns its place.

5 / 5

Actionability

Provides copy-paste-ready, executable commands throughout — 'hogli devbox:start --start-app', 'hogli devbox:exec -- bash -lc "curl ..."', the 'coder list --output json | jq' health check — with exact flags, the URL template, and concrete coverage of new-vs-running and shell-vs-editor-vs-app cases.

5 / 5

Workflow Clarity

Opens with a tracked numbered checklist, then sequences each step (Check access → Set up → Start → Connect → Stop) with explicit validation: doctor's read-only reachability check first, a bounded poll loop keyed on 200/302 vs 000/502, and destructive-op guards (confirmation before -y, 'don't keep anything irreplaceable only on a box', stop the source stack before clone).

5 / 5

Progressive Disclosure

Good section structure with well-signaled one-level-deep references to references/access-troubleshooting.md and references/sync.md inline at the relevant steps, but the referenced files do not exist in the bundle, so the disclosure does not fully resolve.

4 / 5

Total

19

/

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 highly specific, well-triggered description that clearly states both what the skill does and when to use it, with an explicit out-of-scope boundary. Third-person voice is maintained throughout and there is no vague padding.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'Starts, connects to, and troubleshoots', 'spin up or resume', 'open a shell or editor', 'mirror a local checkout (devbox:sync)', 'run the PostHog app... and share a link', 'clone, update, share, or free disk', 'store gh or Claude Code tokens' — giving comprehensive coverage of specific capabilities rather than vague language.

5 / 5

Completeness

Explicitly answers 'what' ('Starts, connects to, and troubleshoots a PostHog devbox... through hogli devbox:* commands') and 'when' ('Use when asked to...') with concrete trigger phrases, plus an explicit 'Not for...' boundary clause.

5 / 5

Trigger Term Quality

Natural user phrasings are covered comprehensively — 'spin up or resume a devbox', 'open a shell or editor on it', 'run a command on it', 'mirror a local checkout', 'share a link', 'free disk', 'diagnose a failing devbox command (tailnet, DNS, Coder CLI version, SSH)' — the kinds of phrases a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (PostHog devbox / Coder workspace via hogli devbox:*) and the 'Not for running the stack on the local machine or for changing the Coder template' clause sharply reduces overlap with neighboring skills.

5 / 5

Total

20

/

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

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository
PostHog/posthog
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.