CtrlK
BlogDocsLog inGet started
Tessl Logo

test-boost-module

Live-test a Harbor Boost module by sending a real prompt through llamacpp via pi and validating the output. Use when asked to test a boost module, verify a module works, check module behavior, QA a boost module, or confirm a module's effect on LLM output.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a tight, executable runbook with a clear multi-step workflow, explicit validation checklist, and useful troubleshooting feedback loops. Conciseness is the only sub-maximal dimension due to minor explanatory prose that could be trimmed.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence, with genuinely useful domain content like the prompt-strategy table and model-listing one-liner, but retains a few explanatory asides (the intro framing and inline flag glosses) that could be trimmed, so it is above the midpoint but not fully lean.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for the test run, the control run, model listing, and log inspection, with templated placeholders covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The numbered "Running the Test" sequence (read source, run with module, run control, compare) plus an explicit Validation Checklist and troubleshooting feedback loops (restart Boost and retry) match the top anchor for clear sequencing with validation and recovery.

5 / 5

Progressive Disclosure

With no bundle files, the skill is self-contained and well-organized into clear sections (Prerequisites, Picking a Test Model, The Command, Choosing the Right Prompt, Running the Test, Validation Checklist, Troubleshooting), which per the simple-skill guidance earns the top score.

5 / 5

Total

19

/

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 answers both what the skill does and when to use it, with a distinct Harbor Boost niche and good trigger-phrase coverage. Specificity is the only moderate dimension, as it names just a couple of concrete actions rather than a comprehensive list.

DimensionReasoningScore

Specificity

Names the domain (Harbor Boost module) and two concrete actions — "sending a real prompt through llamacpp via pi" and "validating the output" — but does not enumerate several specific actions, so it sits at the 1-2 concrete actions anchor rather than 4.

3 / 5

Completeness

It explicitly states both what ("Live-test a Harbor Boost module by sending a real prompt through llamacpp via pi and validating the output") and when (an explicit "Use when..." clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when asked to test a boost module, verify a module works, check module behavior, QA a boost module, or confirm a module's effect on LLM output" clause gives good natural-phrase coverage, but a few common synonyms are missing and there are no file-extension triggers, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

The Harbor/Boost/llamacpp niche is specific and the triggers are tied to boost modules and LLM output, giving it a clear distinct niche with minimal conflict risk against other skills.

5 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
av/harbor
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.