
Cross Domain Thinking Toolbox
- 86 installs
- 1 repo stars
- Updated July 31, 2026
- hexbee/hello-skills
Applies 25 professional mental models, each with a core question, to approach complex problems from fresh angles.
About
A thinking-tools skill that borrows framings from 25 professions to break single-minded approaches and cognitive biases. A developer uses it for multi-faceted decisions, innovation, or root-cause analysis needing diverse perspectives.
- 25-model quick-reference table with core question and best-for use
- Usage patterns for combining models on a problem
Cross Domain Thinking Toolbox by the numbers
- 86 all-time installs (skills.sh)
- +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #1,417 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hexbee/hello-skills --skill cross-domain-thinking-toolboxAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 86 |
|---|---|
| repo stars | ★ 1 |
| Last updated | July 31, 2026 |
| Repository | hexbee/hello-skills ↗ |
What it does
Applies 25 professional mental models, each with a core question, to approach complex problems from fresh angles.
Files
Cross-Domain Thinking Toolbox
Borrow thinking tools from 25 different professions to approach problems from fresh angles.
Quick Reference: The 25 Thinking Tools
| # | Profession | Core Question | Best For |
|---|---|---|---|
| 1 | Artist | What makes this unique and interesting? | Creative blockers, innovation needs |
| 2 | Economist | How do people respond to incentives? | Behavior prediction, system design |
| 3 | Engineer | Can I model and calculate this? | Prediction, data-driven decisions |
| 4 | Entrepreneur | What works if I try many things? | Uncertainty, rapid experimentation |
| 5 | Doctor | What's the diagnosis from symptoms? | Root cause analysis, troubleshooting |
| 6 | Journalist | Have I verified from independent sources? | Information validation, research |
| 7 | Scientist | Does this withstand controlled testing? | Hypothesis validation, beliefs testing |
| 8 | Mathematician | Can I prove this rigorously? | Logic, error detection |
| 9 | Programmer | What patterns can I automate? | Process optimization, simplification |
| 10 | Architect | What will this look like at full scale? | Future visualization, planning |
| 11 | Salesperson | What do people really want beneath stated needs? | Understanding motivations, negotiation |
| 12 | Soldier | What procedure must I follow exactly? | Risk prevention, error avoidance |
| 13 | Chess Master | What happens next if I simulate this? | Strategic foresight, scenario planning |
| 14 | Designer | Does this intuitively suggest how to use it? | UX, communication design |
| 15 | Teacher | How do I build knowledge in a learner's mind? | Explanation, knowledge transfer |
| 16 | Anthropologist | Can I understand this group from inside? | Culture analysis, unfamiliar contexts |
| 17 | Psychologist | Does my model predict actual behavior? | Human behavior understanding |
| 18 | Critic | How can I build on others' work? | Analysis, synthesis, improvement |
| 19 | Philosopher | What happens when I push this idea to extremes? | Finding flaws, revealing principles |
| 20 | Accountant | What ratios reveal hidden truths? | Metrics analysis, efficiency |
| 21 | Politician | What will people believe about this? | Perception, communication strategy |
| 22 | Novelist | Does my story make coherent sense? | Narrative structure, communication |
| 23 | Actor | Can I actually feel the state I need? | Emotional management, presence |
| 24 | Plumber | What would I find by examining directly? | Hands-on investigation, debugging |
| 25 | Hacker | What's really happening underneath? | Understanding systems deeply |
Usage Patterns
Pattern 1: Problem Diagnosis
When user describes a problem:
1. Identify the problem type 2. Recommend 2-3 most relevant thinking tools 3. Explain why each tool fits 4. Provide guiding questions for application
Pattern 2: Multi-Angle Analysis
When user needs diverse perspectives:
1. Pick 3-5 diverse tools for the problem 2. Analyze from each perspective 3. Synthesize insights 4. Highlight trade-offs between approaches
Pattern 3: Perspective Shift
When user is stuck in one mode:
1. Identify their current approach 2. Suggest 2-3 contrasting tools 3. Explain what each would reveal differently 4. Encourage genuine exploration, not just acknowledgment
Pattern 4: Practical Application
When user wants to apply a specific tool:
1. Explain the tool's core principle 2. Provide concrete steps 3. Give worked examples 4. Note limitations and when not to use
Core Principles
- Don't give answers directly — guide thinking with questions
- Each tool has limits — no tool fits all situations
- Combine tools — powerful insights come from mixing perspectives
- Iterate — apply tools, reflect, refine
- Stay practical — focus on actionable insights
Common Problem Types and Tool Recommendations
| Problem Type | Recommended Tools |
|---|---|
| Need creativity/novelty | Artist, Entrepreneur, Designer |
| Understanding behavior | Economist, Psychologist, Salesperson |
| Making predictions | Engineer, Chess Master, Scientist |
| Debugging issues | Doctor, Plumber, Engineer |
| Improving processes | Programmer, Accountant, Architect |
| Communication challenges | Novelist, Teacher, Designer |
| Decision under uncertainty | Entrepreneur, Scientist, Politician |
| Understanding people | Anthropologist, Psychologist, Actor |
| Finding hidden assumptions | Philosopher, Mathematician, Critic |
| Risk management | Soldier, Accountant, Engineer |
When to Ask Follow-Up Questions
Before applying thinking tools, clarify:
- What type of problem is this? (creative, analytical, interpersonal, etc.)
- What approaches have already been tried?
- What outcome does the user want?
- Are there constraints or stakeholders involved?
interface:
display_name: "Cross-Domain Thinking Toolbox"
short_description: "Apply 25 mental models to complex problems"
default_prompt: "Analyze my problem with the most relevant cross-domain mental models, compare insights, and synthesize a practical decision path."
25 Thinking Tools: Complete Reference
1. Artist: What if Creativity Were the Priority?
Core Principle: Prioritize novelty, uniqueness, and what makes something interesting over conventional metrics.
Key Question: How would your work change if "coolness" or originality were your main goal?
Application:
- Ask what makes your project unique when stuck on specs
- Challenge assumptions about what "should" be done
- Seek unconventional approaches that competitors ignore
When to Use: Creative blocks, innovation challenges, standing out from competition
---
2. Economist: How Do People React to Incentives?
Core Principle: People respond predictably to incentives—change incentives, change behavior.
Key Question: If I change this system, how will people adapt to the new incentives?
Application:
- Predict how employees, customers, or family will respond to policy changes
- Design systems that account for human responses
- Avoid assuming people will stay static when environments change
When to Use: System design, behavior prediction, policy making, management
---
3. Engineer: Can I Model This and Calculate?
Core Principle: Move from guessing to precise prediction through modeling and measurement.
Key Question: What will actually happen, quantified with known error margins?
Application:
- Create mathematical models of systems you need to predict
- Measure variables to refine predictions
- Quantify uncertainty rather than vague estimates
When to Use: Forecasting, resource planning, risk assessment, optimization
---
4. Entrepreneur: Do a Lot of Things; See What Works
Core Principle: Speed and experimentation volume compensate for lack of information in uncertain environments.
Key Question: What can I test quickly without waiting for perfect conditions?
Application:
- Build rapid prototypes and iterate
- Launch minimum viable products
- Gather feedback through action, not analysis
When toUse: Startups, uncertainty, innovation, market testing
---
5. Doctor: What's the Diagnosis?
Core Principle: Deduction from symptoms to root causes, comparing with base rates.
Key Question: What is the most likely cause given these symptoms?
Application:
- List all symptoms/indicators
- Compare against common patterns (base rates)
- Rule out possibilities systematically
- Focus on most probable causes first
When to Use: Troubleshooting, debugging, root cause analysis, medical-style diagnosis
---
6. Journalist: Just the Facts
Core Principle: Verify information from multiple independent sources before acting.
Key Question: Have I confirmed this from at least two unconnected sources?
Application:
- Seek independent verification of key claims
- Consider how decisions would change if reported publicly
- Build a worldview based on confirmed facts, not assumptions
When to Use: Research, fact-checking, investigation, avoiding misinformation
---
7. Scientist: Make a Hypothesis and Test It
Core Principle: Isolate variables and test assumptions through controlled experiments.
Key Question: Would this belief survive rigorous scientific testing?
Application:
- Formulate clear hypotheses
- Keep all variables constant except one
- Test predictions against reality
- Update beliefs based on evidence
When to Use: Testing personal habits, validating beliefs, optimization experiments
---
8. Mathematician: You Don't Know Until You Can Prove It
Core Principle: Raise standards of proof to catch subtle errors and hidden assumptions.
Key Question: Can I verify this claim with absolute rigor?
Application:
- Push for formal proof in logical claims
- Don't accept "obvious" truths without verification
- Use this to find bugs in reasoning and code
When to Use: Logic, mathematics, programming, rigorous decision-making
---
9. Programmer: What's the Pattern I Can Automate?
Core Principle: Identify repeated processes and convert them to foolproof, repeatable procedures.
Key Question: What manual steps could become automated, unambiguous procedures?
Application:
- Look for repeated patterns in work
- Extract common processes into scripts or checklists
- Replace human-dependent steps with deterministic ones
When to Use: Process optimization, efficiency improvements, reducing errors
---
10. Architect: Envisioning the Future
Core Principle: Create scaled models to visualize finished results before committing resources.
Key Question: What will this look like when complete at full scale?
Application:
- Build prototypes or mockups before full implementation
- Simulate outcomes through modeling
- See problems before they become expensive to fix
When to Use: Planning, large projects, visualizing outcomes, investment decisions
---
11. Salesperson: Understand Their Minds Better than They Do
Core Principle: Deeply understand others' unspoken needs and contradictions between words and actions.
Key Question: What do people really want beneath what they're saying or conscious aware of?
Application:
- Observe contradictions between stated intentions and actions
- Listen for what people hint at without saying directly
- Identify solutions they haven't consciously considered
When to Use: Negotiation, marketing, understanding stakeholders, product design
---
12. Soldier: Routine and Discipline Prevent Deadly Mistakes
Core Principle: Strict adherence to procedures, even mundane ones, builds habits that prevent critical errors.
Key Question: What procedure must I follow exactly to prevent catastrophic failure?
Application:
- Create and follow checklists for critical tasks
- Never skip "boring" safety steps
- Build discipline through consistent routine
When to Use: High-stakes situations, safety-critical work, preventing errors
---
13. Chess Master: See The Moves In Your Mind's Eye
Core Principle: Visualize potential outcomes before they happen through mental simulation.
Key Question: What will happen next if I simulate this scenario carefully?
Application:
- Play through scenarios mentally before acting
- Practice anticipating outcomes
- Improve pattern recognition for faster prediction
When to Use: Strategy, planning, negotiations, competitive situations
---
14. Designer: The Things You Make Communicate For You
Core Principle: Well-designed objects and messages guide users intuitively.
Key Question: Does this design/communication make the correct usage self-evident?
Application:
- Create interfaces that suggest correct use
- Design communications that guide interpretation
- Think about how habits or presentations shape behavior
When to Use: UX design, communication, presentation, habit formation
---
15. Teacher: Can You See What It Is Like Not to Know Something Obvious?
Core Principle: Effective teaching requires understanding the learner's current mental model.
Key Question: How do I build knowledge in someone's mind when they lack prerequisite concepts?
Application:
- Identify what foundational knowledge is missing
- Build explanations from the learner's perspective
- Use analogies and examples at the right level
When to Use: Explanations, documentation, onboarding, mentoring
---
16. Anthropologist: Can I Immerse and Join Another Culture?
Core Principle: Deep understanding comes from living within unfamiliar groups, not just observing.
Key Question: How can I understand this group from the inside?
Application:
- Spend genuine time in unfamiliar communities
- Participate before trying to analyze
- Learn tacit rules that insiders take for granted
When to Use: Cross-cultural understanding, user research, organizational change
---
17. Psychologist: Test Your Understanding of Other People
Core Principle: Use cognitive models to predict and explain human behavior.
Key Question: Does my model of human behavior accurately predict what people actually do?
Application:
- Study cognitive biases and their effects
- Use attention models to understand focus
- Test predictions about behavior in real situations
When to Use: Understanding reactions, persuasion, UX, relationships
---
18. Critic: Can You Build on The Work of Others?
Core Principle: Deep engagement with creative works enables building new insights.
Key Question: How can I add genuine insight that extends what already exists?
Application:
- Study works deeply before critiquing or building
- Connect ideas across domains
- Synthesize to create original contributions
When to Use: Analysis, research, creative work, improvement
---
19. Philosopher: What Are the Unexpected Consequences of an Intuition?
Core Principle: Pushing ideas to their extremes reveals hidden flaws and fundamental truths.
Key Question: What happens when I take this idea to its logical limit?
Application:
- Use reductio ad absurdum to find contradictions
- Examine edge cases for hidden assumptions
- Reveal principles behind vague intuitions
When to Use: Finding logical flaws, testing policies, examining beliefs
---
20. Accountant: Watch the Ratios
Core Principle: Relationships between numbers reveal insights that raw numbers don't.
Key Question: What ratios or relationships expose hidden truths?
Application:
- Track meaningful metrics (bugs per line, revenue per user)
- Use ratios to normalize comparisons
- Let ratios diagnose problems that absolute numbers hide
When to Use: Performance analysis, efficiency, diagnosis, comparison
---
21. Politician: What Will People Believe?
Core Principle: Actions must be evaluated for both their effects AND their perceived meanings.
Key Question: How will different groups interpret and believe about this action?
Application:
- Consider how communications will be perceived
- Account for how appearances affect credibility
- Navigate constraints of what others will accept
When to Use: Communication, leadership, change management, stakeholder relations
---
22. Novelist: Does Your Story Make Sense?
Core Principle: Narrative structure makes complex realities comprehensible.
Key Question: How do I package this information as a coherent story others can follow?
Application:
- Use narrative arcs for presentations
- Structure information with characters, conflict, resolution
- Make complex realities memorable through story
When to Use: Communication, presentations, pitches, planning
---
23. Actor: The Best Way to Pretend is to Be Real
Core Principle: Genuine emotional states are more effective than simulation.
Key Question: Can I actually summon the authentic feeling I need?
Application:
- Use imagination to evoke real emotions
- Don't just fake confidence—actually feel it
- Use genuine states for more authentic performance
When to Use: Performance, presentations, emotional management, presence
---
24. Plumber: Take It Apart and See What's Broken
Core Principle: Direct investigation reveals truth that analysis can't.
Key Question: What would I discover if I opened this up and looked directly?
Application:
- Don't avoid getting hands dirty
- Disassemble to understand structure
- Direct examination often beats speculation
When to Use: Debugging, investigation, hands-on problems, fear of "breaking" things
---
25. Hacker: What's Really Going on Underneath?
Core Principle: Understanding layers of abstraction reveals possibilities invisible at the surface.
Key Question: What simplified layers might hide unexpected capabilities?
Application:
- Understand systems beneath their interfaces
- Look for edge cases and unexpected inputs
- Exploit gaps between intended and actual behavior
When to Use: System understanding, security thinking, debugging, optimization
#!/usr/bin/env python3
"""
Cross-Domain Thinking Tool Recommender
Analyzes problem descriptions and recommends appropriate thinking tools
from the 25 professional mental models.
"""
from typing import Dict, List, Tuple
import json
import sys
# Thinking tool database with tags and use cases
TOOLS = {
"artist": {
"tags": ["creative", "innovation", "unique", "novelty", "stuck", "blocked"],
"use_when": ["need creative ideas", "stuck in conventional thinking", "seeking novelty"],
"question": "What makes this unique and interesting?",
},
"economist": {
"tags": ["behavior", "incentive", "policy", "system", "predict", "response"],
"use_when": ["predicting behavior", "designing systems", "changing policies"],
"question": "How do people respond to incentives?",
},
"engineer": {
"tags": ["predict", "calculate", "model", "quantify", "forecast", "data"],
"use_when": ["need predictions", "quantify outcomes", "data-driven decisions"],
"question": "Can I model and calculate this?",
},
"entrepreneur": {
"tags": ["uncertainty", "experiment", "test", "rapid", "mvp", "iterate"],
"use_when": ["uncertain environment", "need to test quickly", "startup scenarios"],
"question": "What works if I try many things?",
},
"doctor": {
"tags": ["diagnose", "symptom", "root cause", "troubleshoot", "debug", "cause"],
"use_when": ["troubleshooting", "finding root cause", "debugging issues"],
"question": "What's the diagnosis from symptoms?",
},
"journalist": {
"tags": ["fact", "verify", "source", "research", "confirm", "truth"],
"use_when": ["validating information", "research", "avoiding misinformation"],
"question": "Have I verified from independent sources?",
},
"scientist": {
"tags": ["test", "hypothesis", "experiment", "validate", "belief", "evidence"],
"use_when": ["testing beliefs", "validating assumptions", "optimization experiments"],
"question": "Does this withstand controlled testing?",
},
"mathematician": {
"tags": ["prove", "rigor", "logic", "error", "formal", "verify"],
"use_when": ["rigorous decisions", "finding logical errors", "programming"],
"question": "Can I prove this rigorously?",
},
"programmer": {
"tags": ["automate", "pattern", "process", "repeat", "efficient", "simplify"],
"use_when": ["optimizing processes", "reducing errors", "efficiency"],
"question": "What patterns can I automate?",
},
"architect": {
"tags": ["visualize", "future", "scale", "plan", "prototype", "model"],
"use_when": ["planning", "large projects", "visualizing outcomes"],
"question": "What will this look like at full scale?",
},
"salesperson": {
"tags": ["motivation", "understand", "need", "negotiation", "customer", "want"],
"use_when": ["understanding motivations", "negotiation", "product design"],
"question": "What do people really want beneath stated needs?",
},
"soldier": {
"tags": ["procedure", "discipline", "prevent", "error", "checklist", "safety"],
"use_when": ["preventing errors", "high-stakes situations", "safety-critical work"],
"question": "What procedure must I follow exactly?",
},
"chess_master": {
"tags": ["simulate", "predict", "strategy", "scenario", "future", "anticipate"],
"use_when": ["strategy", "planning", "competitive situations"],
"question": "What happens next if I simulate this?",
},
"designer": {
"tags": ["intuitive", "communicate", "ux", "design", "interface", "guide"],
"use_when": ["UX design", "communication", "presentation"],
"question": "Does this intuitively suggest how to use it?",
},
"teacher": {
"tags": ["explain", "learn", "knowledge", "teach", "transfer", "understand"],
"use_when": ["explanations", "documentation", "onboarding", "mentoring"],
"question": "How do I build knowledge in a learner's mind?",
},
"anthropologist": {
"tags": ["culture", "immerse", "understand", "group", "inside", "cross-cultural"],
"use_when": ["cross-cultural understanding", "user research", "organizational change"],
"question": "Can I understand this group from inside?",
},
"psychologist": {
"tags": ["behavior", "predict", "cognitive", "bias", "attention", "human"],
"use_when": ["understanding reactions", "persuasion", "relationships"],
"question": "Does my model predict actual behavior?",
},
"critic": {
"tags": ["analyze", "build", "synthesize", "critique", "extend", "improve"],
"use_when": ["analysis", "research", "creative work"],
"question": "How can I build on others' work?",
},
"philosopher": {
"tags": ["extreme", "assumption", "logic", "flaw", "principle", "intuition"],
"use_when": ["finding logical flaws", "testing policies", "examining beliefs"],
"question": "What happens when I push this idea to extremes?",
},
"accountant": {
"tags": ["ratio", "metric", "efficiency", "analyze", "compare", "performance"],
"use_when": ["performance analysis", "efficiency", "diagnosis"],
"question": "What ratios reveal hidden truths?",
},
"politician": {
"tags": ["perceive", "believe", "communicate", "stakeholder", "appearance", "credibility"],
"use_when": ["communication", "leadership", "change management"],
"question": "What will people believe about this?",
},
"novelist": {
"tags": ["story", "narrative", "structure", "communicate", "present", "coherent"],
"use_when": ["communication", "presentations", "pitches"],
"question": "Does my story make coherent sense?",
},
"actor": {
"tags": ["emotion", "feel", "authentic", "present", "confidence", "genuine"],
"use_when": ["performance", "presentations", "emotional management"],
"question": "Can I actually feel the state I need?",
},
"plumber": {
"tags": ["examine", "investigate", "hands-on", "direct", "disassemble", "look"],
"use_when": ["debugging", "investigation", "hands-on problems"],
"question": "What would I find by examining directly?",
},
"hacker": {
"tags": ["underlying", "abstraction", "system", "layer", "deep", "edge"],
"use_when": ["system understanding", "debugging", "optimization"],
"question": "What's really happening underneath?",
},
}
def recommend_tools(problem, max_results=5):
"""
Recommend thinking tools based on problem description.
Args:
problem: Description of the problem or situation
max_results: Maximum number of tools to return
Returns:
List of (tool_name, score) tuples sorted by relevance
"""
problem_lower = problem.lower()
words = set(problem_lower.split())
scores = {}
for tool_name, tool_info in TOOLS.items():
score = 0
# Check tags
for tag in tool_info["tags"]:
if tag in problem_lower:
score += 3
elif tag in words:
score += 2
# Check use_when phrases
for phrase in tool_info["use_when"]:
if phrase in problem_lower:
score += 4
if score > 0:
scores[tool_name] = score
# Sort by score and return top results
sorted_tools = sorted(scores.items(), key=lambda x: x[1], reverse=True)
return sorted_tools[:max_results]
def format_recommendation(tool_name, score):
"""Format a single tool recommendation."""
tool_info = TOOLS[tool_name]
return """
### {}
Score: {}
Core Question: {}
Use When: {}
""".format(tool_name.title(), score, tool_info["question"], ", ".join(tool_info["use_when"]))
def main():
"""CLI entry point."""
if len(sys.argv) < 2:
print("Usage: python recommend_tool.py 'your problem description'")
print("\nExample:")
print(' python recommend_tool.py "I need to understand why my team is unmotivated"')
sys.exit(1)
problem = " ".join(sys.argv[1:])
recommendations = recommend_tools(problem)
if not recommendations:
print("No specific tool match found. Try a different description or consult SKILL.md for all 25 tools.")
return
print("\nProblem: {}\n".format(problem))
print("Recommended Thinking Tools:\n")
for tool_name, score in recommendations:
print(format_recommendation(tool_name, score))
if __name__ == "__main__":
main()