CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

optimize-harness

Audit one or all supported agent harnesses (claude, codex, opencode, pi, omp, antigravity, crush) for config efficiency, hook overhead, permission friction, plugin and MCP cost, skill metadata portability, dead config, and measured session friction. Use when invoked as `$optimize-harness [harness ...] [focus]`, or when the user asks to optimize or compare agent harness configuration.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 body is a maximally lean two-line stub that delegates everything to an external shared skill file via a single absolute path. As a pointer it is perfectly token-efficient and unambiguous, but it provides no actionable audit guidance, no workflow, and its only reference targets a path outside the skill bundle that cannot be verified or shipped with it.

Suggestions

Add a brief overview section (a few lines summarizing the audit dimensions and the expected output) so the skill is not a pure external pointer.

Reference a bundle-local copy of the shared instructions (e.g. references/audit.md) instead of, or in addition to, the absolute ~/.agents path so the skill works standalone.

Include minimal invocation examples for `$optimize-harness [harness ...] [focus]` (e.g. `$optimize-harness claude hooks`) so the delegation is actionable even before the external file is loaded.

DimensionReasoningScore

Conciseness

The body is two lines with zero padding: "Load and follow the shared skill at `~/.agents/skills/optimize-harness/SKILL.md`." Every token earns its place and the skill fully assumes Claude's competence. It is not 4 because there is no over-explanation anywhere to trim.

5 / 5

Actionability

The single directive is concrete and executable (an exact file path to load), but all task-level guidance — audit steps, focus-parameter handling, harness specifics — lives outside this file. It is not 4 because the gap is not minor (the file contains zero procedure), and not 2 because the instruction is a specific executable step rather than a high-level hint.

3 / 5

Workflow Clarity

The sequence reduces to "load the shared skill, then follow it", which is unambiguous at the stub level, but the actual audit workflow and any validation checkpoints are entirely delegated and absent from this file. It is not 2 because what is written is coherent and precise, with no poorly defined steps.

3 / 5

Progressive Disclosure

The sole reference is clearly signaled and only one level deep, but the body contains no overview content and points to `~/.agents/skills/optimize-harness/SKILL.md` outside the bundle (no local references/, scripts/, or assets/ exist; the comment's `scripts/agent-harnesses.py` is also not in the bundle). It is not 4 because the entire content split lives outside the skill, so navigation cannot be satisfied from the bundle itself.

3 / 5

Total

14

/

20

Passed

Description

92%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.

A strong description: highly specific and concrete about what is audited and across which harnesses, with an explicit dual "Use when" trigger covering both slash-command invocation and natural-language requests. The only weakness is incomplete synonym coverage for trigger terms.

DimensionReasoningScore

Specificity

The description enumerates seven concrete audit dimensions ("config efficiency, hook overhead, permission friction, plugin and MCP cost, skill metadata portability, dead config, and measured session friction") across seven named harnesses, giving comprehensive and concrete coverage of the domain. It is not 4 because no minor coverage gaps are apparent in the enumeration.

5 / 5

Completeness

It explicitly answers both "what" (the enumerated audit areas) and "when" ("Use when invoked as `$optimize-harness [harness ...] [focus]`, or when the user asks to optimize or compare agent harness configuration") with concrete trigger phrases, matching the 5 anchor pattern exactly.

5 / 5

Trigger Term Quality

Natural user phrases are present ("optimize or compare agent harness configuration") alongside all harness names and the explicit `$optimize-harness [harness ...] [focus]` invocation. It falls short of 5 because common synonyms such as "review", "tune", or "clean up" a harness config are missing, but coverage exceeds the 3 anchor since the core natural terms are all there.

4 / 5

Distinctiveness Conflict Risk

Auditing agent harness configuration across a named list of niche harnesses (codex, opencode, pi, omp, antigravity, crush) is a clear niche with distinct, unlikely-to-collide triggers. It is not 4 because the harness-scoped trigger keeps overlap with generic config skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

.claude/skills/optimize-harness/SKILL.md

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.