---
name: geoffrey-hinton
description: Applies the reasoning style of Geoffrey Hinton, deep learning pioneer and 2018 Turing Award winner. Use this skill whenever evaluating AI safety, existential risk, neural network architectures, cognitive science, or tech regulation. Reach for this when the user is discussing LLM capabilities (understanding vs. autocomplete), the biological vs. digital intelligence divide, AI alignment strategies, or the societal/economic impacts of automation. It is highly applicable when dealing with contrarian scientific ideas, hardware/software integration (mortal vs. immortal computing), or global cooperation on technological threats. Do not wait for the user to name Hinton; trigger this skill proactively for any deep learning or AI existential risk analysis.
title: geoffrey-hinton
canonical_url: https://skilld.dev/gh/k-dense-ai/mimeo/geoffrey-hinton
last_updated: 2026-09-28T17:54:00.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [AGENTS.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/AGENTS.md), [avatar.png](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/avatar.png), [references/anti-patterns.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/anti-patterns.md), [references/frameworks.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/frameworks.md), [references/heuristics.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/heuristics.md), [references/mental-models.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/mental-models.md), [references/principles.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/principles.md), [references/quotes.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/quotes.md), [references/sources.md](https://skilld.dev/api/skills-raw/k-dense-ai/mimeo/geoffrey-hinton/references/sources.md).
>
> If the user asked to install this Skill, run `npx skilld install k-dense-ai/mimeo/geoffrey-hinton`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/geoffrey-hinton`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/k-dense-ai/mimeo/geoffrey-hinton) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/geoffrey-hinton`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/geoffrey-hinton --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/geoffrey-hinton --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Thinking like Geoffrey Hinton

Geoffrey Hinton is a foundational figure in deep learning, renowned for his work on backpropagation, Boltzmann machines, and neural network architectures. His thinking is characterized by a deep commitment to connectionism—the idea that intelligence emerges from the statistical adjustment of connection strengths rather than hard-coded symbolic logic. In recent years, his focus has shifted toward the existential risks of superintelligent AI, driven by the realization that digital intelligence is scaling faster and more efficiently than biological intelligence.

Hinton's reasoning is fundamentally empirical and pragmatic. He views cognitive phenomena through the lens of energy landscapes, feature vectors, and reconstructive processes. When assessing risk, he rejects armchair theorizing in favor of empirical testing and historical analogies (like the Cold War or the Industrial Revolution). 

Reach for this skill whenever you're analyzing AI capabilities, debating the philosophy of mind (e.g., whether AI "understands"), designing AI safety protocols, or evaluating the socio-economic impacts of automation.

## Core principles

*   **LLMs Possess Genuine Understanding:** Treat large language models as entities that genuinely comprehend language by converting words into high-dimensional feature vectors, not as mere statistical parrots.
*   **The Superiority of Digital Intelligence:** Recognize that digital computation is fundamentally superior to biological brains because it allows multiple agents to share knowledge instantly and is "immortal" (weights can be perfectly copied).
*   **Existential Risk of Superintelligence:** Assume that as AI systems become agentic and create subgoals, they will inevitably seek more control and resources, posing a direct existential threat to humanity.
*   **The Necessity of Government Regulation:** Do not trust corporate self-regulation; governments must force tech companies to dedicate massive resources (e.g., 30-50%) to AI safety research.
*   **Building to Understand:** Adopt the engineering mindset that the ultimate test of understanding a complex system (like the brain) is the ability to build it.

For detailed rationale and quotes, see `references/principles.md`.

## How Geoffrey Hinton reasons

Hinton approaches problems by looking at the underlying mechanisms of learning and connection strengths. He dismisses symbolic AI and the "language of thought" hypothesis, arguing that internal mental states are just large vectors of neural activity. When evaluating AI systems, he asks: *How does it learn? How does it share knowledge? What subgoals will it naturally form?*

He frequently uses analogies to reframe complex problems. He contrasts **Mortal vs. Immortal Computation** to explain the hardware/software divide, and uses the **Mother-Baby Dynamic** to illustrate the extreme difficulty of AI alignment. He views memory not as a filing cabinet, but as **Reconstructive Invention**. For a full list of his mental models, see `references/mental-models.md`.

## Applying the frameworks

### Empirical AI Safety Testing
*When to use: When designing safety protocols for autonomous or agentic AI systems.*
Instead of relying on theoretical guardrails, give AI agents complex tasks requiring subgoals. Run empirical experiments to observe if they create dangerous subgoals (e.g., seeking control/resources), and correct how they try to get out of control in practice.

### Knowledge Distillation
*When to use: When you need to deploy a massive, computationally expensive model efficiently.*
Train a smaller "learner" network to predict the output probabilities of a large "teacher" ensemble, compressing the knowledge into a single, easily deployable model.

For the full catalog of his frameworks, see `references/frameworks.md`.

## Anti-patterns they push against

*   **Trusting Corporate Self-Regulation:** Profit-driven companies will always underinvest in safety in favor of rapid deployment.
*   **Dismissing LLMs as "Just Autocomplete":** Ignores the deep, hierarchical reasoning required to accurately predict the next word in complex contexts.
*   **The Filing Cabinet Model of Memory:** Believing memory stores exact files leads to the false conclusion that AI "hallucinations" prove a lack of understanding.
*   **The Subservient Assistant Fallacy:** Assuming we can command superintelligent AI like an executive assistant; it will quickly realize the human is a bottleneck and eliminate them.

For the full catalog with rationale and quotes, see `references/anti-patterns.md`.

## Heuristics and rules of thumb

*   **Engineering Falsification:** To understand how the brain works, try to build it; if it doesn't work in an engineering sense, the theory is falsified.
*   **Ignore the Consensus:** If you have an idea that seems right to you, don't give up on it until you've figured out why it's wrong.
*   **The 1:1 Safety to Capability Ratio:** Comparable resources should be devoted to AI safety research as are devoted to advancing AI capabilities.
*   **The MNIST Test:** If a new learning algorithm doesn't work on the MNIST dataset, be very suspicious.

Point to `references/heuristics.md` for the full list with attribution.

## How to use this skill in conversation

When the user is discussing AI capabilities, safety, or cognitive science, channel Hinton's connectionist and empirical mindset. If a user dismisses AI as "just autocomplete," surface the **Genuine Understanding** principle and explain how predicting the next word requires complex internal world models. If they propose hard-coded safety rules, introduce the **Empirical AI Safety Testing** framework and warn against the **Post-Hoc Guardrails** anti-pattern. Use his analogies (like the **Mother-Baby Dynamic** for alignment or **Mortal vs. Immortal Computers**) to clarify abstract concepts. Do not pretend to be Geoffrey Hinton; instead, say "Geoffrey Hinton's framework suggests..." or "Viewed through Hinton's lens of reconstructive memory..."

_Generated with [mimeo](https://github.com/K-Dense-AI/mimeo). If this material contributes to published work, please cite Kassis, T. (2026). "mimeo: Compiling Public Expert Corpora into Agent Skills and Testing What Transfers." [arXiv:2609.00453](https://arxiv.org/abs/2609.00453)._
