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.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%

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

A well-structured, actionable skill body that walks through a live integration test with executable commands, a control comparison, an explicit validation checklist, and targeted troubleshooting. It stays lean and assumes competence throughout.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what llamacpp, Boost, or modules are conceptually, and each section (prerequisites, command, prompt table, troubleshooting) earns its tokens.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands such as 'harbor launch --workflow <module_name> --model "<base_model_id>" pi -p --no-tools --no-session "<prompt>"' and a complete curl one-liner, with placeholders clearly marked.	3 / 3
Workflow Clarity	A clear numbered sequence (read source → run with module → run control → compare) with explicit validation checkpoints, a comparison/feedback loop, and a validation checklist with troubleshooting error→fix guidance.	3 / 3
Progressive Disclosure	No bundle files exist, so the single-purpose skill relies on well-organized inline sections and one-level-deep pointers to source files ('services/boost/src/modules/<name>.py'); per the simple-skills note this is appropriate.	3 / 3
	Total	12 / 12 Passed

Description

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.

A strong, concise description that pairs concrete tool-specific actions with an explicit, well-varied 'Use when' trigger clause. It is distinguishable from other skills and avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to specific tools — 'Live-test a Harbor Boost module by sending a real prompt through llamacpp via pi and validating the output' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what it does (live-test via llamacpp/pi, validate output) and when to use it via a clear 'Use when...' clause with multiple triggers.	3 / 3
Trigger Term Quality	Covers natural terms users would say — 'test a boost module, verify a module works, check module behavior, QA a boost module' — giving good variation beyond a single keyword.	3 / 3
Distinctiveness Conflict Risk	The niche (Harbor Boost module testing) and its triggers are specific enough that it is unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: av/harbor
Path: .agents/skills/test-boost-module/SKILL.md
Commit: ed20a18

Reviewed: about 14 hours 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.