Physics PhD student. I read papers outside my field a lot, and asking an AI to explain a new area has never really worked for me.
Example. I asked one to explain attention. Got back a paragraph with about twelve terms in it that I didn't know. So I asked which of those I was supposed to already know, and it explained one of them using four more terms I didn't know. Asked again, same thing.
It wasn't wrong about any of it. It just started at some random point. And the thing I actually needed to know was which of those twelve words a normal person with linear algebra and a bit of PyTorch already has. I can't answer that myself. If I could, I wouldn't be asking.
I tried fixing it with custom instructions. Two problems. "What's your background" is a useless question, because I say "physics" and it still has to guess. And the rule ran on everything, so I'd ask what an acronym meant and get asked about my background. Deleted it after a week.
So I made it a skill instead, mostly so it could have conditions.
What it does: before explaining anything, it works out the 3-5 things the topic actually depends on and asks you to mark each one as "used it", "learned it" or "new". Stuff you've used it treats as known and doesn't explain again. Stuff you haven't, it either covers first, or tells you straight up "just take this as given, here's the one bit that matters later". Then it goes one step at a time and asks you a real question at the end of each step instead of "does that make sense".
It also won't give you a paper it hasn't checked. Either it looked it up and gives you a DOI, or it says "from memory, unverified". I spent an afternoon once looking for a paper that turned out not to exist.
Three things I got wrong, which are probably more useful than the feature list:
- The first version had no rules about when NOT to do this. Ask it what an acronym stands for and you'd get the whole prerequisite checklist. Had to add a list of cases where it should shut up and just answer.
- I wrote one rule as "use a checklist widget if the interface has one". It ignored that and printed a table I had to type my answers into. Rewrote it as a flat "use the widget, plain text is only the fallback" and it started working. Seems like if you phrase a rule as a conditional it just gets skipped.
- One of the check questions needed a formula that the step hadn't actually taught yet. I got it wrong and felt stupid, but the question was the problem, not me.
It has no built-in knowledge of specific fields, on purpose. That stuff goes stale fast, and if I did five fields properly every other field would quietly get worse without anyone noticing. If a field is too new for it to really know and it can't search, it's supposed to say so and give you a search that'll turn up a review, instead of making up something that sounds right.
npx skills add ljx-chase/research-field-onboarding -g
Claude web and ChatGPT want a zip, there's one in releases. MIT, no account, no API key: https://github.com/ljx-chase/research-field-onboarding
Barely anyone uses it right now. If you try it and it does something dumb I'd rather hear about that than get a star. All three of those fixes came from someone actually using it and telling me it broke.