CtrlK
BlogDocsLog inGet started
Tessl Logo

cross-critique

Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structured pros and cons, then synthesize. Use this skill whenever you have multiple independent proposals or opinions on a contested decision — architecture tradeoffs, code review disagreements, design choices, competing root-cause theories — and want sharper analysis than you'd produce by synthesizing alone. Pairs naturally with the council and research skills; reach for it liberally whenever proposals diverge.

64

Quality

76%

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 ./.agents/skills/cross-critique/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable instruction skill with a clear workflow and template. The main weakness is moderate verbosity in the motivational prose that could be trimmed without losing clarity.

Suggestions

Trim the 'Why this matters' section to one or two sentences — the rationale that independent authors hold deeper context is largely inferable and adds token weight.

Tighten the 'When to use it' prose into a tighter list; the 'Don't bother when…' paragraph restates trigger guidance already in the description.

Make the critique-round validation slightly more explicit, e.g. a one-line checkpoint after circulating proposals confirming each author returned both pros and cons before synthesizing.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete stepwise guidance, but the 'Why this matters' section and several rationale-heavy prose passages explain motivation Claude could infer and could be tightened.

3 / 5

Actionability

Provides concrete, executable instructions (label/anonymize proposals, ask for both pros and cons per alternative, request a revise-yes/no and a ranked confidence) plus a copy-paste final-answer template, with only minor mechanical gaps in how proposals are shuttled between subagents.

4 / 5

Workflow Clarity

A clearly sequenced three-step process (assemble, circulate-and-critique, synthesize) with a feedback loop for thin critiques; read-only by design so no destructive-operation cap applies, but validation checkpoints are somewhat implicit.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clearly signaled sections, self-contained, and easy to navigate with no nested references — appropriate for a sub-100-line process skill.

5 / 5

Total

16

/

20

Passed

Description

82%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 both capability and trigger conditions with concrete, natural phrasing. The only notable issue is second-person voice in the trigger clause, which costs a specificity point.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions — 'circulating each subagent's independent proposal to the other authors', 'asking for structured pros and cons', 'synthesize' — matching the score-4 anchor, but reduced by 1 for second-person voice ('Use this skill whenever you have…').

3 / 5

Completeness

Explicitly answers both what ('Run a second round on a contested question by circulating… asking for structured pros and cons, then synthesize') and when ('Use this skill whenever you have multiple independent proposals or opinions on a contested decision') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'architecture tradeoffs', 'code review disagreements', 'competing root-cause theories', and 'proposals diverge' give good keyword coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (second-round cross-critique) and explicitly distinguishes itself from the council and research skills, giving minimal conflict risk.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
warpdotdev/common-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.