CtrlK
BlogDocsLog inGet started
Tessl Logo

buildstream-element-reference

Use when writing, editing, or reviewing BuildStream .bst element files — provides variable names, element kinds, source kinds, command hooks, systemd paths, and layer structure

95

Quality

93%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 an excellent skill description that follows best practices. It leads with explicit 'Use when' guidance, specifies the exact file type and tool (BuildStream .bst), and enumerates concrete capabilities. The description is concise yet comprehensive, using third person voice and domain-specific terminology that users would naturally use.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities: 'variable names, element kinds, source kinds, command hooks, systemd paths, and layer structure' - these are all concrete, actionable items the skill provides.

3 / 3

Completeness

Explicitly answers both what ('provides variable names, element kinds, source kinds, command hooks, systemd paths, and layer structure') and when ('Use when writing, editing, or reviewing BuildStream .bst element files') with clear trigger guidance upfront.

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'BuildStream', '.bst element files', 'writing', 'editing', 'reviewing'. The file extension '.bst' and product name 'BuildStream' are exactly what users would mention.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with specific technology focus (BuildStream, .bst files) that is unlikely to conflict with other skills. The combination of the tool name and file extension creates a clear, narrow niche.

3 / 3

Total

12

/

12

Passed

Implementation

87%

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

This is an excellent reference skill that maximizes information density through well-structured tables and minimal prose. It provides concrete, project-specific details (variable names, paths, element kinds, source kinds) that Claude cannot infer. The skill appropriately positions itself as a lookup reference and delegates workflow guidance to specialized skills.

DimensionReasoningScore

Conciseness

Extremely efficient use of tokens with dense tables, minimal prose, and no explanation of concepts Claude would already know. Every section provides project-specific information that cannot be inferred.

3 / 3

Actionability

Provides concrete variable names, exact paths, specific command patterns with install examples, and real element file references. The systemd integration section gives copy-paste ready install commands.

3 / 3

Workflow Clarity

The layer chain section shows element flow clearly, but this is primarily a reference document rather than a workflow guide. It appropriately defers to other skills for actual workflows (packaging-pre-built-binaries, packaging-rust-cargo-projects, etc.).

2 / 3

Progressive Disclosure

Excellent structure with clear section headers, well-organized tables, and appropriate cross-references to related skills (packaging-pre-built-binaries, packaging-zig-projects, packaging-go-projects) without nesting. Content is appropriately scoped as a quick-reference.

3 / 3

Total

11

/

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.