oci-layer-composition

Use when understanding how packages flow into the final OCI image, when modifying layer assembly, or when debugging why files appear or are missing from the built image

Quality

49%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.opencode/skills/oci-layer-composition/SKILL.md

Quality

Discovery

22%

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 description is fundamentally incomplete as it only specifies when to use the skill without explaining what the skill actually does. While it includes some domain-specific terminology around OCI images and layer assembly, the lack of any concrete actions or capabilities makes it impossible for Claude to understand what this skill provides.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Traces package dependencies through build stages, analyzes layer composition, and identifies file origins in OCI images.'

Include common trigger term variations like 'container image', 'Docker image', 'build layers', or 'container build' to improve discoverability.

Restructure to lead with capabilities (what it does) followed by the existing 'Use when...' clause for proper completeness.

Dimension	Reasoning	Score
Specificity	The description lacks concrete actions entirely. It only describes 'when' scenarios without specifying what the skill actually does - no verbs like 'analyze', 'trace', 'debug', or 'inspect' are present.	1 / 3
Completeness	The description only addresses 'when' to use the skill but completely omits 'what' the skill does. There are no capabilities or actions described - only trigger scenarios.	1 / 3
Trigger Term Quality	Contains some relevant technical terms like 'OCI image', 'layer assembly', and 'packages' that users might mention, but these are fairly specialized. Missing common variations like 'container image', 'Docker', 'layers', or 'build artifacts'.	2 / 3
Distinctiveness Conflict Risk	The OCI image and layer assembly focus provides some distinctiveness, but 'debugging why files appear or are missing' is generic enough to potentially overlap with other debugging or file-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, actionable skill document that clearly explains a complex build system's layer composition. The workflow is well-documented with diagrams and tables, and the 'Common Mistakes' section provides excellent troubleshooting guidance. The main weakness is that it's somewhat verbose and monolithic - some reference material could be split out for better progressive disclosure.

Suggestions

Consider splitting the 'Common Mistakes' table and detailed element reference into a separate REFERENCE.md file, keeping SKILL.md focused on the core workflow

Remove some redundancy - the layer chain is explained in prose, ASCII diagram, AND table format; pick the two most effective representations

Dimension	Reasoning	Score
Conciseness	The content is comprehensive but includes some redundancy - the layer chain is explained multiple times in different formats (text, diagram, table), and some explanations could be tightened. However, it largely avoids explaining concepts Claude would already know.	2 / 3
Actionability	Provides concrete, specific guidance with exact file paths, YAML snippets, and clear instructions. The 'Adding a Package to the Image' section gives copy-paste ready examples, and the tables provide specific element names and their purposes.	3 / 3
Workflow Clarity	The layer chain is clearly sequenced with ASCII diagrams showing the flow. The 'Common Mistakes' table serves as validation guidance, and the document clearly explains when files get excluded and why, providing implicit checkpoints for debugging.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's a monolithic document (~250 lines) that could benefit from splitting detailed reference material (like the full element kinds table or common mistakes) into separate files. No external references are provided for deeper dives.	2 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: projectbluefin/dakota
Commit: f062bf8

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