Conf Preference Elicitation
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill conf-preference-elicitationgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/conf-preference-elicitation ~/.claude/skills/conf-preference-elicitationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Conference Preference Elicitation
The instinct when personalizing a schedule is to interview the attendee — ask them to rate every theme, list their goals, fill out a form. That is the wrong shape. With a good latent structure underneath (the theme map), a *couple* of well-chosen questions capture most of the signal; the literature shows large personalization gains after only two. The agent's intelligence belongs in **which question to ask next**, not in **how many** to ask. A person will answer three sharp, concrete questions gladly and resent ten vague ones — and the ten vague ones model them *worse*.
So this skill does the opposite of a survey. It holds the person's preferences as an **uncertainty region** over the themes, and at each step asks the one question that would **shrink that region the most**. It asks by **showing concrete contrasting talks** ("would you go to A or B?") and reading the latent dimension off the pick, because what people choose is truer than what they say they like. It deliberately spends some questions **exploring** themes it cannot yet place the person in, rather than only **confirming** the obvious. And it treats fighting **selection bias** as a hard requirement, not a nicety: if it only ever shows popular, central talks, it learns a narrowed caricature of the person and never surfaces the niche session they would have loved — so it deliberately offers outliers.Details
- Skill name
conf-preference-elicitation- Repository
- lyndonkl/claude
- Path
skills/conf-preference-elicitation/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Conf Preference Elicitation skill do?
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it
How do I install the Conf Preference Elicitation skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Conf Preference Elicitation popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Deliberation Debate Red Teaming
200lyndonkl/claude
Challenges plans, designs, and decisions from multiple adversarial perspectives to surface blind spots, hidden assumptions, and vulnerabilities before they cause real damage. Use when testing plans or decisions for blind spots, need adversarial review before launch, validating strategy against worst-case scenarios, building consensus through structured debate, identifying attack vectors or vulnerabilities, or when groupthink or confirmation bias may be hiding risks.
Burp Suite
213TerminalSkills/skills
Test web application security with Burp Suite. Use when a user asks to intercept HTTP traffic, test for web vulnerabilities, fuzz API endpoints, analyze authentication flows, or perform manual web application pentesting.
Dependency Updater
213TerminalSkills/skills
Audit project dependencies for outdated packages, security vulnerabilities, and breaking changes. Use when someone asks to "check for outdated packages", "audit dependencies", "find vulnerable dependencies", "plan dependency upgrades", "detect breaking changes", or "update npm packages safely". Analyzes package.json/lock files, cross-references changelogs, and produces ordered upgrade plans.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.