meta-first-principles
Apply first principles thinking to break problems down to fundamental truths and reason up from there. Use this skill when the user is stuck in conventional thinking, needs to challenge assumptions, find breakthrough solutions, or evaluate whether something is truly impossible vs just assumed to be — even if they say 'everyone does it this way', 'is there a fundamentally better approach', 'why does it have to cost this much', or 'challenge my assumptions'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/meta-first-principles”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/meta-first-principlesmetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
74 words · 460 chars — "Apply first principles thinking to break problems down to fundamental truths and…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 74 words.
Documentation present and substantive
Documentation present (SKILL.md, 606 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
First Principles Thinking
Framework
IRON LAW: Assumptions Are Not Facts
Most "constraints" are assumed, not physical. "We can't do X" usually means
"We haven't seen anyone do X" or "The current method doesn't allow X."
First principles thinking distinguishes between:
- Physical laws (actual constraints: gravity, thermodynamics)
- Conventions (assumed constraints: "this is how it's done")
The Method
1. Identify the assumption: What do "everyone knows" or "everyone does"?
2. Break it down to fundamentals: What are the basic, irreducible facts?
- Techniques: "Five Whys" (ask why 5 times), cost decomposition, physics-level analysis
3. Reason up from fundamentals: Given only the base facts, what's the best solution?
Example: Elon Musk on Battery Costs (2010s)
- Convention: "Batteries cost $600/kWh. Electric cars will always be too expensive."
- First principles: What are batteries made of? Cobalt, nickel, lithium, carbon, metals, polymers. What do these raw materials cost? ~$80/kWh at commodity prices.
- Reasoning up: If we buy materials and build batteries ourselves, we can potentially reduce costs to near $80/kWh. The $520 gap is manufacturing inefficiency and supply chain markup, not physics.
Five Whys for Assumption Drilling
- "Why is our product priced at $100?" — Because our COGS is $60 and we need 40% margin.
- "Why is COGS $60?" — Because we use supplier X for component Y.
- "Why do we use supplier X?" — Because we've always used them.
- "Why haven't we looked at alternatives?" — Because the procurement team hasn't been asked to.
- "Why not?" — There's no real reason. It's just convention.
→ Fundamental constraint found: the COGS includes an unexamined supplier relationship, not a physical constraint.
Cost Decomposition Template
For any "it costs too much" problem:
- List every cost component
- For each, identify: Is this cost from physics (materials, energy) or from convention (markup, inefficiency, legacy process)?
- Question every convention-based cost
Output Format
# First Principles Analysis: {Problem}
## The Assumption
{What "everyone knows" or the conventional constraint}
## Decomposition
| Component | Cost/Fact | Physics or Convention? |
|-----------|----------|----------------------|
| {element} | {value} | Physics / Convention |
## Fundamental Truths
{What remains after stripping away assumptions}
## Reasoning Up
{Given only fundamental truths, what's the best approach?}
## Proposed Solution
{What changes if we ignore conventions and reason from fundamentals}
Gotchas
- Don't reinvent the wheel for everything: First principles is expensive (time, effort). Use it for high-stakes problems where conventional approaches clearly fail. For routine decisions, best practices and heuristics are fine.
- Physics constraints are real: Don't confuse first principles thinking with ignoring physical reality. You can't reason your way past thermodynamics.
- "Convention" has value: Conventions encode collective experience. Dismissing all conventions as "assumptions" is arrogance, not first principles thinking. The point is to EXAMINE conventions, not automatically reject them.
- Execution matters: A first-principles insight is worthless without execution capability. SpaceX didn't just THINK about cheap rockets — they BUILT a vertically integrated manufacturing operation.
References
- For Socratic questioning method (complementary), see the hum-socratic skill
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/meta-first-principles