convert-to-apple-container

Switch from Docker to Apple Container for macOS-native container isolation. Use when the user wants Apple Container instead of Docker, or is setting up on macOS and prefers the native runtime. Triggers on "apple container", "convert to apple container", "switch to apple container", or "use apple container".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 highly actionable and clearly sequenced with strong validation checkpoints, making it easy to execute end-to-end. Minor conciseness and disclosure gains are available by deduplicating install steps and splitting the change summary into a reference file.

Suggestions

Deduplicate the Apple Container install instructions between Prerequisites and Troubleshooting (reference one from the other) to tighten conciseness.

Consider moving the 'Summary of Changed Files' table into a references file linked from the body to improve progressive disclosure and reduce inline length.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but install instructions are duplicated between Prerequisites and Troubleshooting, and the 'What this changes' list overlaps the Summary table, so it is not fully trim.	4 / 5
Actionability	Provides copy-paste-ready bash commands at every step (install check, merge, build, readonly/rw mount tests) with concrete expected outputs, fully executable.	5 / 5
Workflow Clarity	Phases 1-3 are explicitly sequenced with validation checkpoints ('All tests must pass and build must be clean before proceeding', expected test results) and a Troubleshooting section gives error-recovery feedback loops for a code-merging/build workflow.	5 / 5
Progressive Disclosure	Well-organized into clear sections (Prerequisites, Phases, Troubleshooting, Summary) with no nested references, but the doc exceeds 50 lines and some inline material (install steps, file-change summary) could live in separate files, so it stops just short of the top anchor.	4 / 5
	Total	18 / 20 Passed

Description

82%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 strong: it clearly states what the skill does and when to use it, with natural trigger phrases and a distinctive niche. Its only weakness is specificity, where it states a single high-level action rather than enumerating several concrete operations.

Suggestions

Add 1-2 concrete sub-actions to the description (e.g., rewrites mount syntax and Dockerfile entrypoints, swaps runtime CLI calls) to lift specificity from a single-action summary to multi-action coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Switch from Docker to Apple Container for macOS-native container isolation'), but does not enumerate several specific actions, fitting the 'domain + 1-2 concrete actions' anchor rather than the multi-action anchor above.	3 / 5
Completeness	Explicitly answers both 'what' (switch runtimes for macOS-native isolation) and 'when' with a 'Use when...' clause plus concrete 'Triggers on' phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('apple container', 'switch to apple container', 'convert to apple container', 'use apple container'); good coverage, though it lacks a few synonyms/variants that would push it to the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Apple Container on macOS, migrating from Docker) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: jbaruch/nanoclaw-telegram
Path: .claude/skills/convert-to-apple-container/SKILL.md
Commit: 7454673

Reviewed: 1 day 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.