CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

best-of-n

Generate a small set of independent candidate solutions in worktrees, judge them against one explicit rubric, and apply the winner only after PASS verification.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./crates/skills/assets/skills/best-of-n/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-sequenced, action-dense process guide with unusually strong verification gates for a batch operation. Its main weaknesses are the missing trigger guidance carried over from the description and a dangling reference to a workflow recipe file that is not actually shipped in the bundle.

Suggestions

Ship `operate_best_of_n.workflow.js` in the bundle (e.g. under scripts/) and reference it with an explicit relative path and link so the "checked-in recipe" claim is navigable rather than dangling.

Add a concrete judge-prompt template mirroring the candidate JSON example so the "Judge Once" phase is copy-paste ready, and include a one-line invocation example for the workflow recipe's `strategy: "search"` mode.

Tighten the closing caveat paragraph about runtime gates, which currently restates limitations that could be compressed into one sentence.

DimensionReasoningScore

Conciseness

The body is dense with operational guidance and never explains concepts Claude already knows (no definitions of worktrees, rubrics, or verification). A few sentences could still be tightened — the closing paragraph about the workflow recipe's limitations and the session-goal bullet — so it does not reach the every-token-earns-its-place level of anchor 5.

4 / 5

Actionability

Concrete guidance is strong: an executable JSON worker-launch contract, specific implement-candidate settings (`type: "implement"`, `worktree: true`, `write_authority: "worktree_write"`), N ranges (2–4 default 3; 2–16 for search), and a named recipe file. Minor gaps keep it from anchor 5: no judge-prompt template and no invocation example for `operate_best_of_n.workflow.js`.

4 / 5

Workflow Clarity

The four phases (Set The Tournament → Generate Independently → Judge Once → Integrate Only After PASS) are clearly sequenced with explicit validation checkpoints and error-recovery loops: replay on a clean baseline, runtime-run hard gates, "NONE is valid when every candidate fails", the stop-early rule, and revision-on-evaluator-change. This satisfies the batch-operation validation requirement rather than triggering its cap.

5 / 5

Progressive Disclosure

Section structure is good, but the body's only external reference — "The checked-in `operate_best_of_n.workflow.js` recipe" — is mentioned in prose without a path or link, and no such file exists anywhere in the bundle (no references/, scripts/, or assets/ directories). The reference is therefore not clearly signaled or navigable, matching anchor 3 rather than 4.

3 / 5

Total

16

/

20

Passed

Description

58%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 communicates a distinctive, concrete capability with a clear "what", but it completely lacks "when to use it" guidance and the natural trigger phrasing users would employ. Adding an explicit use-when clause with everyday synonyms would move it into the good-example range.

Suggestions

Add an explicit "Use when..." clause with concrete triggers, e.g. "Use when a task has several plausible approaches worth comparing, when the user asks to compare options or generate alternatives, or for high-stakes decisions where picking the best solution matters."

Include natural synonyms users would actually say — "compare", "options", "alternatives", "pick the best" — alongside the current process terms like "worktrees" and "PASS verification".

Briefly signal scope variants (proposal/review/research vs. code implementation) so the capability coverage reads as comprehensive rather than narrow.

DimensionReasoningScore

Specificity

The description lists three concrete actions — "Generate a small set of independent candidate solutions in worktrees", "judge them against one explicit rubric", and "apply the winner only after PASS verification". It falls short of anchor 5 because coverage has gaps: it omits proposal-vs-code variants, parallel generation, and failure handling.

4 / 5

Completeness

The "what" is clearly stated (generate, judge, apply winner), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Terms like "candidate solutions", "judge", and "winner" are relevant, but the natural phrases a user would actually say — "compare approaches", "options", "alternatives", "pick the best" — are absent, and "worktrees" / "PASS verification" are process jargon rather than user triggers. Not 4 because common variations and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The ensemble-comparison niche (independent candidates, rubric judging, worktree isolation) is clearly distinct from most skills, with only minor overlap risk against closely related review/verification skills. Not 5 because phrases like "apply the winner only after PASS verification" could plausibly collide with testing or code-review skills.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Hmbown/Codewhale

Path

crates/skills/assets/skills/best-of-n/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.