skills/the-geek-way/SKILL.md
Answer questions about "The Geek Way" by Andrew McAfee — including its four core norms (Science, Ownership, Speed, Openness), supporting concepts like Homo ultrasocialis, cultural evolution, the OODA loop, the press secretary brain module, and real-world case studies. Use this skill whenever someone asks about The Geek Way, geek culture in business, McAfee's framework for organizational excellence, or concepts from the book such as ultrasociality, agile iteration, radical candor, or why tech companies outperform traditional firms. Also trigger when users ask how to apply these ideas to their own organization, team, or leadership style.
npx skillsauth add neurongraph/skills_repo the-geek-wayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill equips an agent to accurately and thoroughly answer questions about "The Geek Way: The Radical Mindset That Drives Extraordinary Results" by Andrew McAfee (MIT principal research scientist, 2023).
For deeper detail on any concept, see references/concepts.md.
The Geek Way argues that a new kind of corporate culture — pioneered by Silicon Valley but applicable anywhere — consistently outperforms traditional Industrial Era management. McAfee calls this culture "the geek way."
A "geek" in McAfee's sense is not a stereotype — it's someone who is perennially curious, willing to tackle hard problems, and unafraid of unconventional solutions. Business geeks are "obsessive mavericks" fixated on finding better answers.
The book synthesizes management theory, evolutionary psychology, military strategy, cultural anthropology, and behavioral economics into one unified theory of why geek-run organizations win.
Awards: The Economist Best Books of 2023 · Forbes Top 10 Business Books of 2023 · Financial Times Book of the Month (Nov 2023)
From 2002 to 2022, the most valuable companies in the world shifted dramatically from industrial incumbents to technology-oriented firms (Amazon, Google, Microsoft, Netflix, SpaceX, etc.). McAfee argues this happened not just because of the "tech industry" — but because of a superior culture those companies built.
"Culture eats strategy for breakfast." — The book's organizing principle.
The geek way works because it taps into humanity's superpower: the ability to cooperate intensely and learn rapidly at the group level. When all four geek norms are present, a culture emerges that is:
The four norms can be remembered by the acronym SOSO: Science, Ownership, Speed, Openness. These four norms work as an integrated system — adopting only one or two without the others creates imbalance and reduces effectiveness.
Make decisions based on evidence, not authority, instinct, or tradition.
Why it matters: Humans are hardwired for overconfidence. Evolution built a "press secretary" module in our brains that paints us in the best light (see concepts). Science-norm companies build systems to override this.
Push responsibility, autonomy, and decision-making as far down the org chart as possible.
Why it matters: Empowerment fuels accountability. When people own outcomes, they behave differently than when they're just executing orders.
Prioritize rapid iteration over exhaustive planning.
Why it matters: "How fast can you find out you're wrong?" is the predictive metric of success. The goal is to compress the learning loop, not to plan perfectly.
Encourage radical candor, challenge assumptions, reject groupthink, and embrace failure.
Why it matters: At geek organizations, open assessments and honest pushback keep firms from going off the rails. Quibi failed partly because its lack of openness prevented honest product feedback before launch.
McAfee proposes renaming humanity from Homo sapiens ("wise man") to Homo ultrasocialis ("ultra-social man"). His argument: what makes humans unique isn't individual intelligence — it's our extraordinary capacity for:
An individual human cannot survive alone (can't start a fire from scratch, for example). But human groups accumulate knowledge that no individual could hold. This is humanity's true superpower.
| Company | Geek Norm Illustrated | Key Lesson | |---|---|---| | Netflix | Openness + Speed | Culture Deck; outpaced Quibi and legacy Hollywood studios | | Amazon | Ownership + Speed | Two-pizza teams; relentless customer obsession | | SpaceX | Speed + Science | 80% of all satellites launched in a year; iteration over perfection | | Planet Labs | Speed | Satellite iteration in months, not decades | | Microsoft (post-Nadella) | Openness + Science | Cultural "Hit Refresh" — growth mindset replacing fixed mindset | | Quibi (cautionary tale) | Lack of Openness | Raised $1.75B, shut down in a year — no honest internal feedback loop | | Coca-Cola / New Coke | Lack of Science | Tested taste but not meaning — ignored what Coke meant culturally |
Q: Is the Geek Way only for tech companies? A: No. McAfee explicitly argues the principles apply to any organization willing to challenge conventional beliefs. Non-tech companies in cars, entertainment, aerospace, and healthcare have successfully adopted geek norms.
Q: What's the biggest enemy of the Geek Way? A: Bureaucracy — which arises naturally when organizations grow and when the four norms are not actively maintained. The tendency to bureaucratize is always present and must be actively resisted.
Q: How is this different from "digital transformation"? A: Digital transformation is a subset. The Geek Way is about cultural transformation — how decisions are made, how people are empowered, how failure is treated. Technology is the enabler, not the point.
Q: What about toxic tech cultures? (Theranos, etc.) A: McAfee acknowledges not all Silicon Valley companies are good. Theranos, for instance, violated the Science and Openness norms deeply. Having geek aesthetics isn't the same as having geek norms.
Q: What is the "ultimate geek ground rule"? A: Shape the ultrasociality of group members so that the group's cultural evolution is as rapid as possible in the desired direction. In practice: install the four norms, keep them healthy, and the organization will self-improve.
If someone asks how to implement these ideas, suggest:
For more detail, read references/concepts.md.
development
Use this skill any time you need to create or edit a .pptx presentation for Surjit. This skill enforces the IBM Plex design language — typography-forward, flat geometry, sharp corners, restrained color. Trigger whenever the user asks for a deck, slides, or presentation, or references a .pptx file, and especially when they want slides that feel clean, modern, or 'IBM-style'. If the user just says 'make me a deck' or 'build slides', use this skill — it overrides the generic pptx skill for this user.
data-ai
--- name: obsidian-todo-action description: Action a single Obsidian todo: reads project context and related tasks, adaptively assesses what's needed (sub-tasks, email drafts, calendar invites), generates all artifacts into the project folder, and updates project.md — all in one session. compatibility: When called by an orchestrator, todoPath, projectsPath, and OBSIDIAN_VAULT must be provided. When called independently, Section 0 detects the vault and resolves all paths automatically. --- # Obs
data-ai
Transcribes audio files (voice memos, recordings, meetings) into text using a local ASR model (qwen3_asr_rs). Processes all audio in the configured input directory and saves transcripts as text files. Use this skill whenever the user wants to transcribe audio, convert speech to text, process voice memos, or get spoken content into written form — even if they don't use the word "transcribe".
devops
--- name: obsidian-daily-process description: Orchestrates the full Obsidian vault processing pipeline: transcribes voice memos and audio recordings, classifies them into todos, ideas, or daily notes, and files each into the right place in the vault. Also triggers downstream Obsidian pipelines (wiki update, ArtMind knowledge graph). Use this skill whenever the user wants to process voice memos, audio recordings, or run any Obsidian vault update — even if they only mention "voice memo", "recordin