CtrlK
BlogDocsLog inGet started
Tessl Logo

orbstack-best-practices

Patterns for OrbStack Linux VMs and Docker on macOS. Covers orbctl/orb commands, machine lifecycle, cloud-init, networking, file sharing, and SSH access. Must use when working with OrbStack, orbctl commands, or Linux VMs on macOS.

88

2.10x
Quality

82%

Does it follow best practices?

Impact

99%

2.10x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable, concise command reference that excels at executable guidance, but it is a monolithic single file with no progressive disclosure to deeper references and lacks validation checkpoints around its destructive operations.

Suggestions

Add explicit validation/confirmation steps before destructive commands like `orb delete` and `orb reset` (e.g., verify the machine name, confirm data loss) to lift workflow clarity above the destructive-operation cap of 3.

Split large subtopics (Kubernetes, Docker integration, cloud-init examples) into separate reference files under ./references/ and link to them from SKILL.md to add genuine progressive disclosure.

De-duplicate command examples that recur across sections (machine creation, push/pull) to tighten the token budget.

DimensionReasoningScore

Conciseness

Mostly lean command reference that assumes Claude's competence and avoids concept explanation, but some command groups (create, push/pull) are restated across sections and could be trimmed.

4 / 5

Actionability

Dense, copy-paste-ready executable commands and config examples throughout, covering common cases from machine creation through networking, Docker, and Kubernetes.

5 / 5

Workflow Clarity

Content is organized by topic with rough sequencing in Machine Lifecycle, but destructive operations ("orb delete myvm", "orb reset" which "deletes everything") lack explicit validation or confirmation checkpoints, capping the score at 3.

3 / 5

Progressive Disclosure

Well-organized section headers aid navigation, but at ~330 lines all content is inlined in one file with no bundle references; substantial subtopics (Kubernetes, Docker integration, cloud-init) that could live in separate reference files are not split out.

3 / 5

Total

15

/

20

Passed

Description

92%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 clearly states both capabilities and usage triggers with concrete, product-specific terms. Minor improvement possible by adding synonyms like "Docker Desktop replacement" or "containers on Mac".

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete capability areas — "orbctl/orb commands, machine lifecycle, cloud-init, networking, file sharing, and SSH access" — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what ("Patterns for OrbStack... Covers...") and when ("Must use when working with OrbStack, orbctl commands, or Linux VMs on macOS") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms ("OrbStack", "orbctl commands", "Linux VMs on macOS") that users would actually say, but missing common synonyms like "Docker Desktop alternative" or "containers".

4 / 5

Distinctiveness Conflict Risk

OrbStack is a distinct, narrowly-named product with trigger terms unlikely to match other skills, giving minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.