Individual skill
first-principles-analyzer
Deconstructs problems down to fundamental truths and foundational constraints rather than reasoning by analogy or convention.
skills/reasoning/first-principles-analyzer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,201 bytesSKILL.mdcore · 1,896 bytesexamples/example.mddoc · 1,109 bytes
Read excerpt
## Purpose
Strip away industry cargo-culting, legacy conventions, and reasoning-by-analogy to rebuild solutions strictly from fundamental constraints (physics, math, raw computing limits, core business rules).
## When to Use
- When existing solutions are bloated, expensive, or overly complex because "that is how everyone does it."
- When rethinking an architectural component or feature from the ground up.
- When evaluating whether an established best practice actually applies to your specific constraints.
## What to Analyze
1. **Identify the Core Objective**: What is the non-negotiable end goal in one sentence?
2. **Catalog Received Assumptions**: List every assumption inherited from typical stacks, standard patterns, or prior systems.