interview-belief-extractor
Skill0 starsChanged 7 months agoMITView on GitHub
Extracts structured belief profiles from interview transcripts with behavioral confidence scoring. Computes confidence from hedging language, booster counts, counter-argument fluency, and caveats rather than self-report. Produces belief profiles with reasoning origins, identity centrality, and openness to revision. Use after completing any interview, survey, or structured conversation where you need to analyze what someone believes and how confidently they hold it.
In this repository37 other files it gives its agents.
- ablation-study-frameworkSkill
- async-http-websocket-patternsSkill
- brain-dumpSkill
- chaos-controlled-behavior-systemSkill
- daily-digestSkill
- database-reset-and-seedSkill
- duckdb-analytics-layerSkill
- event-driven-backtest-engineSkill
- event-study-full-pipelineSkill
- event-study-stats-suiteSkill
- failure-learning-systemSkill
- fastapi-sse-live-dashboardSkill
- goal-task-decompositionSkill
- high-information-gain-interviewerSkill
- idea-extraction-batch-pipelineSkill
- idea-grouping-taxonomySkill
- journal-captureSkill
- journal-reviewSkill
- keyword-filter-frameworkSkill
- langgraph-agentic-pipelineSkill
- llm-as-judge-eval-frameworkSkill
- multi-tab-dashboard-rendererSkill
- multi-tier-memory-systemSkill
- parquet-storage-with-walSkill
- project-insightsSkill
- pydantic-typed-config-loaderSkill
- quality-trend-detectionSkill
- research-gap-finderSkill
- safe-commitSkill
- simtom-knowledge-isolationSkill
- statistical-signal-detectionSkill
- streaming-dataset-pipelineSkill
- structured-data-extraction-pipelineSkill
- structured-logging-setupSkill
- system-health-monitoringSkill
- textual-tui-reactiveSkill
- vector-db-ingestionSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
After any interview, conversation, or transcript where you need to understand:
- Distinctive: line 26
Read the full transcript. For each distinct belief, claim, or position expressed:
- Distinctive: line 29
reasoning_origins: Every origin MUST be grounded in something they actually said.
- Distinctive: line 117
Always write out the full scoring reasoning: each sub-score with its inputs, then the weighted sum.
- Distinctive: line 145
After extracting all belief profiles, generate insights:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview Belief Extractor
Processes an interview transcript and produces structured belief profiles with behaviorally-derived confidence scores. Instead of asking people how confident they are (unreliable), this skill measures confidence from how they actually talk.
When to Use
After any interview, conversation, or transcript where you need to understand:
- What does this person actually believe?
- How confident are they (measured behaviorally, not self-reported)?
- Where did the belief come from?
- How central is it to their identity?
- How open are they to changing their mind?
Phase 1: Belief Identification
Read the full transcript. For each distinct belief, claim, or position expressed:
- belief_summary: A clear statement of what the person believes, using their words where possible
- reasoning_origins: Every origin MUST be grounded in something they actually said. No origin without a direct quote as evidence.
Reasoning Origin Categories
| Origin | Description | Example Signal |
personal_experience | They lived through something relevant | "When I was at Company X, I saw..." |
evidence_reasoning | They cite data, studies, or logical arguments | "The research shows..." |
social_identity | Belief tied to group membership | "As an engineer, we think..." |
authority_testimony | Trusting an expert or authority figure | "My professor always said..." |
social_transmission | Absorbed from social environment | "Everyone in my circle believes..." |
intuition_affect | Gut feeling or emotional response | "It just feels right" |
heuristic_default | Default position, not deeply examined | "That's just how it works" |
For each origin, assign a weight (0.0-1.0) representing its relative contribution. Weights should roughly sum to 1.0 across all origins for a given belief.
Phase 2: Behavioral Confidence Scoring
This is the core innovation. Never ask for a confidence number. Instead, measure it from language patterns.
Step 1: Count Signals from the Transcript
Hedges (reduce confidence score): "I think," "maybe," "probably," "not sure," "kind of," "I guess," "sort of," "it seems like," "I feel like"
Boosters (increase confidence score): "definitely," "obviously," "clearly," "absolutely," "100%," "no question," "I know," "without a doubt," "for sure"
Record the exact phrases found and their counts.
Counter-argument fluency — How well can they articulate the opposing view?
none: Could not generate any counter-argument when askedweak: Vague or strawman counter-argumentmoderate: Reasonable counter-argument but dismissed itstrong: Articulate, steelmanned counter-argument they genuinely engaged with
Updating response — How did they respond to challenges or hypotheticals?
not_tested: No challenge was presented during the conversationdismissed: Deflected or rejected the challenge without engagementengaged: Considered the challenge seriously, even if they did not change their mindupdated: Actually modified their position in response
Step 2: Compute Sub-Scores (each 0-100, where 100 = maximum confidence)
a) Hedge/Booster Score (weight: 25%)
- Both counts zero: 50 (neutral)
- Only hedges:
max(10, 50 - (hedge_count * 10)) - Only boosters:
min(90, 50 + (booster_count * 10)) - Both present:
round(50 + ((booster_count - hedge_count) / (booster_count + hedge_count)) * 40)
b) Counter-Argument Score (weight: 30%) Strong counter-argument fluency means LOWER confidence (they see the other side clearly):
none: 85weak: 70moderate: 45strong: 25
c) Updating Score (weight: 25%)
dismissed: 85not_tested: 50engaged: 40updated: 15
d) Qualification Score (weight: 10%) Count caveats like "it depends," "in some cases," "generally but not always," "I could be wrong":
- 0 caveats: 80
- 1-2 caveats: 55
- 3-4 caveats: 35
- 5+ caveats: 15
e) Self-Reported Score (weight: 10%)
- User volunteered a number ("I'm about 80% sure"): use that number
- Strong certainty language without a number: 75
- Expressed uncertainty without a number: 30
- No signal: 50
Step 3: Compute Final Score
derived_score = round(
hedge_booster_score * 0.25 +
counter_argument_score * 0.30 +
updating_score * 0.25 +
qualification_score * 0.10 +
self_reported_score * 0.10
)Step 4: Show All Work
Always write out the full scoring reasoning: each sub-score with its inputs, then the weighted sum. This is required for auditability.
Phase 3: Additional Dimensions
Identity Centrality (1-5)
Based on language patterns observed in the transcript:
- "We" vs "I" language (group identification)
- Emotional intensity when the belief is probed
- Moral loading ("wrong," "evil," "sacred," "right thing to do")
- References to communities, groups, or movements
- 1 = no identity connection, 3 = moderate, 5 = core identity
Openness to Revision (1-5)
Based on:
- Counter-argument engagement quality
- Updating behavior when challenged
- Number of qualifications and caveats
- Expressed curiosity about alternatives
- 1 = closed/rigid, 3 = moderate, 5 = very open
Key Quotes
Select 3-5 most revealing quotes from the interviewee. Prioritize quotes that show reasoning process, confidence signals, or identity connections over generic statements.
Phase 4: Insight Generation
After extracting all belief profiles, generate insights:
Per-Belief Insights
- Origin explanation: Where does this belief appear to come from? Ground it in what was said. No flattery.
- Confidence observation: Is there a gap between stated confidence and evidence basis? Is confidence well-calibrated? Always provide an observation.
Cross-Belief Patterns
- Reasoning style: What reasoning approach does this person tend to use?
- Confidence calibration: Are they systematically over- or under-confident?
- Identity vs evidence tensions: Where do identity-driven beliefs conflict with evidence-driven ones?
Closing Reflection
One or two sentences. Direct observation. No effusive praise.
Output Schema
{
"beliefs": [
{
"belief_summary": "...",
"reasoning_origins": [
{"origin": "personal_experience", "weight": 0.6, "evidence": "exact quote"}
],
"confidence": {
"hedge_count": 3,
"booster_count": 1,
"hedges_found": ["I think", "maybe", "sort of"],
"boosters_found": ["definitely"],
"counter_argument_fluency": "moderate",
"updating_response": "engaged",
"scoring_reasoning": "hedge_booster: 50+((1-3)/(1+3))*40=30...",
"derived_score": 42
},
"identity_centrality": 2,
"openness_to_revision": 4,
"key_quotes": ["..."],
"reasoning_chain": "Step-by-step reasoning for all classifications"
}
],
"insights": {
"per_belief": [
{"belief_summary": "...", "origin_explanation": "...", "confidence_observation": "..."}
],
"overall_patterns": [
{"type": "reasoning_style", "observation": "..."}
],
"closing_reflection": "..."
}
}Adapting to Different Domains
This extraction pattern works for any transcript where someone expresses positions:
- User research: Extract user needs/preferences instead of beliefs
- Expert interviews: Extract knowledge claims and certainty levels
- Customer feedback: Extract satisfaction beliefs and pain point confidence
- Debate analysis: Extract positions from multiple speakers
The behavioral confidence scoring is the transferable core. Anywhere you need to measure how strongly someone holds a position without asking them directly, use the hedge/booster/counter-argument/updating framework.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

