CtrlK
BlogDocsLog inGet started
Tessl Logo

packaging-zig-projects

Use when packaging a project that uses the Zig build system, when an element needs zig fetch/build with offline dependency caching, or when adding Zig dependencies to an existing element

80

Quality

74%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.opencode/skills/packaging-zig-projects/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

72%

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 has strong trigger terms and distinctiveness for Zig-specific use cases, but is structured backwards - it only explains when to use the skill without first stating what the skill does. Adding a capability statement before the 'Use when' clause would significantly improve clarity.

Suggestions

Add a capability statement before the trigger clause, e.g., 'Packages Zig projects, manages build dependencies, and configures offline caching for the Zig build system.'

Expand the 'what' portion to list specific concrete actions like 'configure build.zig files', 'cache dependencies offline', 'resolve Zig package dependencies'.

DimensionReasoningScore

Specificity

Names the domain (Zig build system) and mentions some actions (zig fetch/build, offline dependency caching, adding dependencies), but doesn't comprehensively list concrete actions like 'configure build.zig', 'manage build artifacts', or 'resolve transitive dependencies'.

2 / 3

Completeness

The description is entirely a 'Use when...' clause explaining when to use it, but lacks a clear 'what does this do' statement. It doesn't explain what the skill actually does (e.g., 'Packages Zig projects and manages dependencies').

2 / 3

Trigger Term Quality

Includes natural keywords users would say: 'Zig build system', 'zig fetch', 'build', 'offline dependency caching', 'Zig dependencies', 'element'. These are terms a developer working with Zig would naturally use.

3 / 3

Distinctiveness Conflict Risk

Very specific niche targeting Zig build system packaging with clear triggers like 'zig fetch', 'Zig dependencies', and 'offline dependency caching'. Unlikely to conflict with general build or packaging skills.

3 / 3

Total

10

/

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 high-quality, actionable skill for a complex packaging scenario. It excels at providing concrete, executable guidance with clear workflows and excellent troubleshooting support. The main weakness is length—some content could be split into reference files, and there's minor redundancy in repeated environment variable exports across code blocks.

Suggestions

Consider extracting the full element template and common mistakes table into separate reference files (e.g., TEMPLATE.md, TROUBLESHOOTING.md) to reduce the main skill's length

Consolidate the repeated ZIG_GLOBAL_CACHE_DIR and ZIG_LIB_DIR exports into a single setup block or note that they should be set once at the start of build-commands

DimensionReasoningScore

Conciseness

The skill is comprehensive but includes some redundancy (e.g., repeating ZIG_GLOBAL_CACHE_DIR export in multiple code blocks, explaining the same concepts in multiple sections). Some explanations could be tightened, though most content is necessary for this complex topic.

2 / 3

Actionability

Excellent actionability with fully executable YAML configurations, complete shell commands, and a copy-paste ready element template. The code examples are concrete and specific, including exact flag explanations and real-world patterns.

3 / 3

Workflow Clarity

Clear three-stage build process with explicit sequencing (setup cache → populate HTTP deps → place git deps). Includes validation guidance, error handling patterns, and a comprehensive troubleshooting table with symptoms and fixes.

3 / 3

Progressive Disclosure

Content is well-organized with clear sections, but this is a monolithic document that could benefit from splitting detailed reference material (like the full element template and common mistakes table) into separate files. References to external files (bluefin/ghostty.bst) are mentioned but inline content is heavy.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
projectbluefin/dakota
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.