edgar-financials
Skill3 starsChanged 35 days agoMITView on GitHub
Analyze SEC filings and financial statements. Each skill directory has skill.yaml (patterns and examples) and sharp-edges.yaml (common mistakes to avoid). Every object has .docs for API reference:
In this repository33 other files it gives its agents.
- llms.txtllms.txt
- alpha-zooSkill
- breadth-chart-analystSkill
- canslim-screenerSkill
- factor-mining-pandaaiSkill
- backtesting-bias-avoidanceSkill
- backtest-reviewSkill
- data-quality-auditSkill
- paper-reproSkill
- pine-backtesterSkill
- stats-test-pickerSkill
- vectorbt-backtestSkill
- vectorbt-optimizeSkill
- akquantSkill
- ashare-pre-st-filterSkill
- cninfo-disclosureSkill
- ctp-apiSkill
- ptrade-strategy-writingSkill
- quant-buddySkill
- ssquant-futuresSkill
- tdxquantSkill
- tqsdk-tradingSkill
- wencai-screenerSkill
- defillama-dataSkill
- defillama-flowsSkill
- defillama-yieldsSkill
- perp-funding-basisSkill
- pine-debuggerSkill
- pine-developerSkill
- llmquant-equitiesSkill
- llmquant-macroSkill
- llmquant-riskSkill
- openquant-tradingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 39
Every object has .docs for API reference:
≈ “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
<!--
Imported from: https://github.com/dgunning/edgartools
Source Path: edgar/ai/skills/core/SKILL.md
Curated for awesome-quant-skills
-->name: EdgarTools description: Query and analyze SEC filings using EdgarTools
EdgarTools
Analyze SEC filings and financial statements.
Skills
| Skill | Purpose |
| core (this directory) | Company lookup, filings, search |
| financials/ | Financial statements and metrics |
| reports/ | 10-K/10-Q/8-K section extraction |
| holdings/ | 13F institutional holdings |
| ownership/ | Form 3/4/5 insider transactions |
| xbrl/ | Low-level XBRL facts and concepts |
| forms.yaml | SEC form type mappings |
Each skill directory has skill.yaml (patterns and examples) and sharp-edges.yaml (common mistakes to avoid).
Quick Setup
from edgar import set_identity
set_identity("Your Name your@email.com") # RequiredAPI Discovery
Every object has .docs for API reference:
company.docs # Full API guide
company.docs.search("filings") # Search for specific topic
filing.docs.search("xbrl") # How to access XBRLCommon Entry Points
from edgar import Company, get_filings, find
company = Company("AAPL") # By ticker
filing = find("0000320193-25-000079") # By accession
filings = get_filings(form="10-K", year=2024) # DiscoveryDoes 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.

