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.
93
Quality
89%
Does it follow best practices?
Impact
99%
2.10xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (OrbStack on macOS), lists specific capabilities (orbctl commands, machine lifecycle, cloud-init, networking, file sharing, SSH), and provides explicit trigger guidance. The description uses proper third-person voice and includes natural keywords users would actually use when working with this tool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'orbctl/orb commands, machine lifecycle, cloud-init, networking, file sharing, and SSH access' - these are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Patterns for OrbStack Linux VMs and Docker on macOS. Covers orbctl/orb commands, machine lifecycle...') AND when ('Must use when working with OrbStack, orbctl commands, or Linux VMs on macOS'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'OrbStack', 'orbctl', 'orb commands', 'Linux VMs', 'macOS', 'Docker', 'SSH access', 'cloud-init' - good coverage of both tool names and common user terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting OrbStack specifically on macOS - unlikely to conflict with generic Docker or VM skills due to explicit tool naming and platform specification. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive reference for OrbStack that excels in conciseness and actionability. Every command is executable and the content assumes Claude's competence. The main weaknesses are the lack of explicit validation checkpoints in multi-step workflows and the monolithic structure that could benefit from progressive disclosure to separate reference files.
Suggestions
Add explicit validation steps after cloud-init creation (e.g., 'Verify: orb -m myvm cloud-init status --long' before proceeding)
Include a verification step after Docker daemon config changes (e.g., 'Verify: docker info | grep -A2 Registry')
Consider splitting detailed sections (Kubernetes, Docker Integration, Cloud-Init) into separate .md files with brief summaries and links in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Docker or VMs are. Every section provides direct commands and examples without padding. Tables are used effectively for reference data. | 3 / 3 |
Actionability | Fully executable commands throughout with copy-paste ready examples. Cloud-init YAML is complete, Docker commands are specific, and troubleshooting provides exact solutions. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Commands are well-organized by category, but multi-step workflows lack explicit validation checkpoints. For example, cloud-init creation doesn't specify a verify-then-proceed pattern, and Docker config changes mention 'Apply with orb restart docker' but don't include verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but it's a monolithic document (~250 lines) that could benefit from splitting detailed sections (Kubernetes, Docker Integration, Cloud-Init) into separate reference files with a leaner overview in the main skill. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- 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.