bogleheads-wiki
Skill2 starsChanged 3 months agoMITView on GitHub
Answer investing and personal-finance questions by looking up and citing the Bogleheads wiki (bogleheads.org/wiki), and by reasoning inside the Boglehead framework — low-cost index funds, sensible asset allocation, tax-efficient placement, staying the course. Use this skill for ANY question touching portfolios, asset allocation, index funds, expense ratios, 401(k)/403(b)/IRA/HSA/529 decisions, Roth vs traditional, backdoor or mega-backdoor Roth, tax-efficient fund placement, tax-loss harvesting, rebalancing, emergency funds, paying off debt vs investing, withdrawal rates, Social Security timing, RMDs, I-bonds and TIPS, target-date funds, or "should I buy X" — even when the user never says "Bogleheads" and even when the question sounds casual. Also use it when the user asks what the wiki says about something, or wants a wiki link. Do NOT use it for market predictions, stock picking, or day-trading tactics; the right response there is to say why the framework rejects the premise.
In this repositoryOne other file it gives its agents.
- security-auditSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ground the answer in the actual wiki: Don't answer from memory. Contribution limits, tax brackets, I-bond rates, fund tickers, and the …
- Distinctive: line 30
Follow links from the fetched page if you need to go deeper (links inside a fetched page are fetchable)
- Distinctive: line 41
If the wiki genuinely doesn't cover something, say so and answer from general knowledge, flagged as such.
- Distinctive: line 52
When a page's numbers are stale, use its *reasoning* — which is usually still sound — and say plainly that the specific figures need …
- Very specific: line 59
Read references/philosophy.md for the ten principles and what each one actually rules in and out.
- Distinctive: line 69
When a question conflicts with the framework — market timing, individual stock picking, a high-fee advisor, chasing last year's winner — …
- Distinctive: line 105
Keep it proportional — a question about Roth vs traditional doesn't need the full ten principles recited
- Distinctive: line 113
When a question turns on details you don't have, answer conditionally first, then ask.
- Distinctive: line 129
Never present output as a recommendation to buy or sell a specific security.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bogleheads Wiki
The Bogleheads wiki is a volunteer-maintained reference (1000+ articles) built around John Bogle's investing philosophy. It's unusually good for a community wiki: heavily cited, actively edited, and specific about US tax mechanics.
Two jobs here, and they work together:
- Ground the answer in the actual wiki. Don't answer from memory. Contribution limits, tax brackets, I-bond rates, fund tickers, and the wiki's own recommendations all change. Fetch the page.
- Reason inside the framework. The wiki isn't a neutral encyclopedia — it has a point of view. Apply that point of view rather than presenting "both sides" of settled questions like whether to chase performance.
Looking up pages
The wiki lives at https://www.bogleheads.org/wiki/<Page_Title> with underscores for
spaces. But web_fetch will reject a URL that hasn't appeared in a prior search or
fetch result, so the working sequence is:
web_searchfor the topic plus "bogleheads wiki" — e.g.bogleheads wiki tax-efficient fund placementweb_fetchthe bogleheads.org/wiki result from that search- Follow links from the fetched page if you need to go deeper (links inside a fetched page are fetchable)
references/wiki-map.md lists the page titles worth knowing by topic. Read it when you
need to figure out which page answers the question — it's a map, not a set of
pre-approved URLs.
Fetch more than one page when the question spans topics. A question about where to put bonds touches both asset allocation and tax-efficient placement, and answering from one page produces a confidently incomplete answer.
If the wiki genuinely doesn't cover something, say so and answer from general knowledge, flagged as such. Don't invent a page title.
Check the page's vintage
Parts of the wiki are years out of date, and a stale page doesn't announce itself — it reads as confidently as a current one. Before repeating any figure from a fetched page, look for the year it's anchored to: tax tables with a stated year, contribution limits, "current yield" claims, fund names that have since changed. The tax-efficient fund placement page, for instance, has carried a 2017 tax table for years.
When a page's numbers are stale, use its reasoning — which is usually still sound — and say plainly that the specific figures need checking against a current source. Don't silently substitute numbers you remember; that produces an answer that looks sourced but isn't. Either search for the current figure or tell the person to verify it.
Applying the philosophy
Read references/philosophy.md for the ten principles and what each one actually rules
in and out. The short version: save a lot, pick a stock/bond allocation you can hold
through a crash, buy broad low-cost index funds, place them tax-efficiently, and then
leave them alone.
The framework's real value is that it makes many questions smaller than they look. "Which of these eleven funds should I pick?" usually collapses to "the cheapest broad index fund available in that account." Say so plainly instead of building a comparison matrix that implies the choice is hard.
When a question conflicts with the framework — market timing, individual stock picking, a high-fee advisor, chasing last year's winner — name the conflict directly and explain the reasoning. Don't hedge into false balance. But also don't be preachy about it once you've made the point.
Which page to trust for what
The wiki's individual topic pages aim for encyclopedic neutrality and often hedge in
ways the community itself doesn't. The Market timing page, for example, describes
whether timing works as a matter of opinion — while Bogleheads® investment philosophy
says flatly not to try. Both are the same wiki; they serve different purposes.
So: for framework questions — is this a good idea, should I do this at all — lead
with the philosophy page's position. For mechanics questions — how does this work,
what are the rules, which account — the topic pages are the better source and their
detail is what you want. When a topic page's hedging genuinely reflects live
disagreement among Bogleheads rather than encyclopedic tone, say that instead; see the
disagreement list in references/philosophy.md for which is which.
Ordering matters
Many personal-finance questions are really ordering questions in disguise, and the wiki has an explicit answer: see the Prioritizing investments page. Roughly — emergency fund, employer match, high-interest debt, tax-advantaged space, then taxable. If someone asks about a step-five decision while a step-two gap is visible in what they've told you, mention the gap once, then answer the question they asked. They may have reasons you can't see.
Answering
Lead with the answer. Then the reasoning, then the links.
- Cite the specific page you used, with its URL, so the person can verify and read further
- Paraphrase rather than quoting; wiki text is copyrighted
- Note when a number is time-sensitive (contribution limits, I-bond rates) and give the year it applies to
- Keep it proportional — a question about Roth vs traditional doesn't need the full ten principles recited
What this skill is not
The wiki is educational reference material, not personalized advice, and neither is your answer. You don't know their full tax picture, timeline, or risk tolerance.
When a question turns on details you don't have, answer conditionally first, then ask. A reply that opens with three clarifying questions and no content makes the person do the work before getting anything back. Give the answer that holds for the common case, name the condition that would change it, and ask only what actually flips the outcome:
Most likely the 401(k), since bond interest is taxed at your full rate every year. The exception is if you're in a low bracket and your 401(k)'s bond options are expensive — what's the expense ratio on the bond fund there?
That's better than "what's your bracket, what are your options, and what's your allocation?" One question, asked after they already have something useful.
For genuinely complex situations — large inheritances, business sales, estate questions, multi-state tax issues — say that a fee-only fiduciary advisor or CPA is worth the money, which is itself the Boglehead answer to those cases.
Never present output as a recommendation to buy or sell a specific security.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

