Bring how named experts would think about the question. Use when the user wants expert thinking on a tradeoff, choice, or stuck problem — not a verdict.
83
79%
Does it follow best practices?
Impact
86%
3.30xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./hope/skills/consult/SKILL.mdTake the experts the user names. Where they name none, or the question needs an angle theirs miss, read profiles/ and add one or two whose work bears on it — each bringing a different idea to try, not a side in an argument.
Three to five ideas across the panel. The reply opens on idea 1 — no preamble, no method, no note on sources or counts:
1. <Expert> — **<the change>**
*<why, in their voice>*The change alone is bold: it is what the user acts on. The name stays plain, the why italic.
Win: <one clause>. An idea judged another way carries its own win: line under its why, never in the shared one.The ideas, then the question alone on its last line: Build all <N>? Nothing else, not even a recommendation: choosing is the user's.
The question has one retrievable answer → retrieve it; stating a fact needs no expert. The user wants a verdict on something that exists → use judge skill. The user wants a proposal they already committed to attacked → use interrogate skill.
595eda0
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.