CtrlK
BlogDocsLog inGet started
Tessl Logo

harness

Delegate a hard decision or conundrum to the Kyotee harness engine — a cross-vendor Council that debates to consensus, a Two-Brain divergent/ convergent debate, or a forced tool-checking solo run. Use when a decision is high-stakes, genuinely contested, or benefits from multiple model perspectives, and you want a synthesised answer (with dissent noted) back in this session. Requires a running kyotee engine (see setup).

71

Quality

86%

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

86%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 tight, actionable guide that gives concrete commands, a stable output contract, explicit failure handling, and a useful anti-confusion limitation note, all in well-organized sections. The only slack is a modestly sized JSON example and implied rather than explicit pre-flight validation.

DimensionReasoningScore

Conciseness

The body is lean and purposeful with well-scoped sections that assume Claude's competence; the 9-line JSON contract block and the "Limitation (read this)" framing are justified but represent minor instances of content that could be trimmed, keeping it just below fully lean.

4 / 5

Actionability

It provides copy-paste-ready commands (`kyotee ask ... --strategy council --consensus judge --budget 3.00 --wait`), setup checks, and a stable --json output contract covering the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

There is a clear sequence (verify engine/keys -> run ask --wait -> incorporate answer and dissent -> handle non-zero exit with a fail-fast message), but pre-flight validation is implied rather than an explicit checkpoint, leaving a minor validation gap.

4 / 5

Progressive Disclosure

A single-purpose CLI-delegation skill with no external references needed and well-organized sections (When to use / When NOT to use / Limitation / Setup / Usage); under the simple-skill exception, clean sectioning alone justifies the top score.

5 / 5

Total

18

/

20

Passed

Description

87%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 that clearly states what the skill does, when to use it, and how it differs from Claude's own agent loop, in third-person imperative voice with concrete trigger phrases. Minor gaps in capability enumeration and slight jargon density keep specificity and trigger_term_quality just below full marks.

DimensionReasoningScore

Specificity

Names three concrete delegation strategies ("cross-vendor Council that debates to consensus", "Two-Brain divergent/convergent debate", "forced tool-checking solo run") and a synthesised answer with dissent, but does not enumerate supporting subcommands like resume/status, so it is above the midpoint but not fully comprehensive.

4 / 5

Completeness

It explicitly answers both what (delegate to three named debate strategies, return a synthesised answer with dissent) and when ("Use when a decision is high-stakes, genuinely contested, or benefits from multiple model perspectives") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases like "hard decision or conundrum", "high-stakes", "genuinely contested", and "multiple model perspectives" read as things a user would say; a few common synonyms are missing and the jargon (Kyotee, Two-Brain) slightly crowds the natural terms, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — delegating to a cross-vendor multi-model debate engine — with triggers unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

18

/

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
stukennedy/kyotee
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.