CtrlK
BlogDocsLog inGet started
Tessl Logo

plan-arbiter

Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, well-sequenced arbitration workflow with explicit verification gates and a concrete handoff template. It is concise and clear; the only weak spot is the absence of any executable command or code example for the most hands-on cases.

Suggestions

Add one concrete example of a finished decision memo (filled in) so the handoff format is unambiguous in practice.

Show a minimal subagent dispatch pattern for the 'Use subagents for independent review' guidance so that step is copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; it never explains concepts Claude already knows and every section (Normalize checklist, Cross-Review bullets, tie-break order, handoff template) earns its place in the context window.

5 / 5

Actionability

Provides concrete, actionable guidance (explicit Normalize extraction checklist, five-tier tie-break order, and a labeled handoff memo template), but as an instruction-only skill it lacks executable code or commands, leaving minor gaps for the most concrete cases.

4 / 5

Workflow Clarity

A clear five-step sequence (Collect, Normalize, Cross-Review, Decide, Handoff) with explicit verification gates ('Verification' field with tests/CI/deploy checks) and a feedback path ('Revise first' outcome) for error recovery.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and content appropriately inline; there are no bundle files to split out, so it is one level deep by design, with only minor room for tighter overview-level framing.

4 / 5

Total

18

/

20

Passed

Description

100%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 excellent: specific, comprehensive in trigger terms, complete in answering both what and when, and clearly distinct from other skills. It reads naturally as something a user would say when needing plan arbitration.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('compare, cross-review, merge, judge, choose, or arbitrate competing plans' and 'produce one recommended execution plan'), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly states what it does ('Turn competing plans into one executable direction') and when to use it via a clear 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms ('compare, cross-review, merge, judge, choose, or arbitrate') and concrete artifacts ('session IDs, transcripts, plan documents, PR descriptions') that a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (arbitrating competing multi-agent plans) with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

20

/

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
BuilderIO/skills
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.