Archaeology

Investigates *why* Perseus code is the way it is by tracing its history across the several GitHub repos Perseus has lived in over its lifetime (khan-exercises → Khan/perseus → Khan/webapp → Khan/perseus). Use this skill whenever someone asks a code-archaeology or "why is it like this" question about Perseus — e.g. "why do we have both X and Y widgets?", "why is this implemented this way?", "when/why was this added?", "what's the history behind this file/function?", or hands you a commit, PR, or file and wants its origins explained. Also triggers on the explicit /archaeology command. This matters because Perseus's history bridges multiple repo moves (and predates React), so an ordinary `git blame` in the current checkout dead-ends at the 2022 "initial commit" squash — this skill knows how to bridge those gaps. Do NOT use it for general web research (use deep-research) or for understanding what current code *does* (just read the code).

khan Updated
sample of Perseus in use

File contents

khan/perseus commit 2ba42490c2

Frequently asked questions

npx get-skill add khan/archaeology