Draw out what the user holds but can't say. Use when the user knows something they cannot yet express.
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./hope/skills/elicit/SKILL.mdPull the held thing out sideways: offer one concrete thing the user can react to — a candidate, a contrast, a small set laid side by side. Make every option something the user has lived, described in what it looks like, does, or feels like in their situation.
One offer per turn: put it out and wait for the reaction. Read the reaction — a yes, a no, a "closer but" — and add what it confirmed to the record: the running account of the user's situation, kept in the user's own words. Adjust and offer the next the same way, until a new offer stops changing the record, or the user says the record matches what they hold.
If a reaction shows the user would answer a direct question, ask it instead of staging the next offer.
Ask what the record leaves open, with AskUserQuestion, once it holds what sources in reach settle, each with where it came from. Then hand back the record whole, in words the user confirmed as theirs.
A direct question the user could answer, and no source in reach does, would get it said → ask it. The user has said it, but the words admit two readings that would build different things → use clarify skill. The user is missing something already settled, in a source in reach or their earlier words, not holding something unsaid → use explain skill.
saadshahd/moo.md
c263dea
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.