etf-compare
Skill9 starsChanged 6 months agoMITView on GitHub
Side-by-side ETF comparison. Use when the user wants to compare two or more ETFs, decide between ETFs covering the same space, or understand the difference between similar funds.
In this repository16 other files it gives its agents.
- etf-portfolioSkill
- etf-screenSkill
- etf-sectorSkill
- stock-analystSkill
- stock-balance-sheetSkill
- stock-earningsSkill
- stock-filingSkill
- stock-managementSkill
- stock-moatSkill
- stock-monitorSkill
- stock-portfolioSkill
- stock-red-flagsSkill
- stock-screenSkill
- stock-sectorSkill
- stock-thesisSkill
- stock-valuationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Run a side-by-side comparison of the ETFs provided.
- Distinctive: line 27
If overlap >70%: flag — owning both is redundant
- Distinctive: line 43
If the user provides more than 2 ETFs, run the comparison as a ranked table and eliminate the weakest option first with a clear explanation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Run a side-by-side comparison of the ETFs provided. Structure:
1. WHAT EACH ONE IS One sentence per ETF: strategy, index tracked, issuer.
2. SIDE-BY-SIDE SCORECARD
| Metric | [ETF 1] | [ETF 2] |
| AUM | ||
| Expense ratio | ||
| # of holdings | ||
| Top holding (% weight) | ||
| Top 10 as % of portfolio | ||
| 1yr return | ||
| 3yr annualized | ||
| Beta vs S&P 500 | ||
| Avg daily volume |
3. OVERLAP ANALYSIS
- What % of holdings do they share?
- If overlap >70%: flag — owning both is redundant
- Where they diverge: what does one own that the other doesn't?
4. WHAT YOU'RE ACTUALLY CHOOSING BETWEEN
- Is this a cost decision? (same exposure, different fee)
- Is this a conviction decision? (different index methodology = different bet)
- Is this a liquidity decision? (one trades much more thinly)
- Is this a tax decision? (different distribution behavior)
5. FACTOR DIFFERENCES Which ETF loads more heavily on: growth / value / momentum / quality / size? Under what market conditions does each outperform the other?
6. VERDICT: WHICH ONE AND WHY Give a clear recommendation. If the answer is genuinely "it depends," explain on what — don't hedge without a reason.
If the user provides more than 2 ETFs, run the comparison as a ranked table and eliminate the weakest option first with a clear explanation.
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.

