us-sec-analysis
Skill2 starsChanged 8 days agoMITView on GitHub
Collect and summarize source-mapped SEC evidence for U.S. public companies. Use when the user needs filing-precision work before broader U.S. stock analysis: latest 10-K or 10-Q facts, MD&A, Risk Factors, balance sheet and cash-flow checks, latest 8-K metadata, SEC XBRL companyfacts metrics, filing text extraction, reusable sec-reference.md/sec-cache.json artifacts, or a Korean SEC evidence pack under analysis-example/us/<company>/sec-analysis.md. This is the SEC filing-precision stage before us-stock-analysis when exact filing support matters.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- kr-analyst-report-discoverSkill
- kr-analyst-report-fetchSkill
- kr-analyst-report-insightSkill
- kr-analyst-report-watchSkill
- kr-article-readabilitySkill
- kr-chatgpt-reviewSkill
- kr-daily-market-newsSkill
- kr-earnings-reviewSkill
- kr-finance-slide-claritySkill
- kr-foreign-analystSkill
- kr-market-leadersSkill
- kr-market-sentimentSkill
- kr-naver-bloggerSkill
- kr-naver-blog-publishSkill
- kr-naver-browseSkill
- kr-naver-insightSkill
- kr-order-backlog-analysisSkill
- kr-portfolio-guardSkill
- kr-portfolio-monitorSkill
- kr-research-siteSkill
- kr-sector-analysisSkill
- kr-sector-auditSkill
- kr-sector-compareSkill
- kr-sector-data-packSkill
- kr-sector-planSkill
- kr-sector-updateSkill
- kr-stock-analysisSkill
- kr-stock-chartSkill
- kr-stock-dart-analysisSkill
- kr-stock-data-packSkill
- kr-stock-planSkill
- kr-stock-updateSkill
- kr-strategy-backtestSkill
- kr-trade-flow-analysisSkill
- kr-web-browseSkill
- telegram-report-senderSkill
- us-daily-market-newsSkill
- us-earnings-reviewSkill
- us-stock-analysisSkill
- us-strategy-backtestSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. About 0 are common, 11 are distinctive, and 15 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to turn SEC EDGAR filings and XBRL facts into a reusable evidence pack before broader U.S.
- Distinctive: line 18
Default to Korean for user-facing output, headings, notes, and summaries unless the user explicitly asks for English.
- Distinctive: line 19
Keep official company names, ticker symbols, SEC form names, accounting labels, accession numbers, and quoted disclosure text exactly as …
- Very specific: line 24
Prefer the latest 10-K and 10-Q plus latest 8-K metadata for the default filing set.
- Very specific: line 25
Use SEC primary sources first: data.sec.gov submissions, SEC XBRL companyfacts, and the filing's primary document in /Archives/edgar/data/.
- Very specific: line 27
If the workspace is writable and the user wants a reusable artifact, write the result to analysis-example/us/<company>/sec-analysis.md.
- Very specific: line 29
If existing sec-analysis.md, sec-reference.md, or sec-cache.json files already exist for the company, read them before re-collecting and …
- Very specific: line 36
Run scripts/fetch-sec-edgar.js to resolve ticker-to-CIK, collect submissions, collect companyfacts, select latest forms, download primary …
- Very specific: line 38
Run scripts/extract-sec-sections.js on the relevant latest-10k.txt or latest-10q.txt when the user needs MD&A, Risk Factors, controls, …
- Very specific: line 40
Run scripts/build-sec-reference.js to generate sec-reference.md and sec-cache.json from filing export, sections, and facts.
- Very specific: line 42
Use the default SEC analysis shape from references/output-format.md, keep every material number source-mapped, and label gaps as not …
- Very specific: line 44
Use us-stock-analysis after this when the user wants thesis, valuation, catalysts, risks, and conclusion.
- Distinctive: line 46
Read references/workflow.md for the SEC collection and extraction checklist.
- Distinctive: line 47
Read references/output-format.md for the default Korean evidence-pack shape.
- Distinctive: line 48
Read references/script-inputs.md before running the bundled scripts.
- Very specific: line 55
Run all bundled scripts with node.
- Distinctive: line 59
Do not invent revenue mix, customer concentration, segment profitability, governance facts, or valuation metrics that are not in the …
- Distinctive: line 60
Do not derive standalone quarters from year-to-date XBRL facts unless the user explicitly asks and you have the matching prior cumulative …
- Distinctive: line 62
Treat SEC XBRL companyfacts as standardized fact evidence, not as a complete substitute for reading the filing text.
- Very specific: line 63
If a company uses only custom taxonomy for a memo-critical metric and companyfacts lacks the standard concept, mark it as not separately …
- Distinctive: line 64
Keep latest 8-K work metadata-first unless the user asks to parse 8-K items.
- Very specific: line 65
If a filing section parse is missing or needs_review, do not convert that into not separately disclosed.
- Very specific: line 66
Keep SEC fair access explicit: declared User-Agent, efficient downloads, cache reuse, and request cadence below 10 requests/second.
- Very specific: line 88
Use us-stock-analysis after this when the user wants a final investment memo, valuation, catalysts, risks, or comparison.
- Distinctive: line 89
If the user's question is mainly "what does the SEC filing actually say", keep the output in SEC analysis mode and stop short of a thesis.
- Very specific: line 90
If an existing sec-reference.md or sec-cache.json covers the same accession numbers, cite and update that artifact instead of …
≈ “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
U.S. SEC Analysis
Use this skill to turn SEC EDGAR filings and XBRL facts into a reusable evidence pack before broader U.S. stock interpretation.
<!-- US_SEC_FAIR_ACCESS_RULE --><!-- US_SEC_REFERENCE_DIGEST_RULE --><!-- US_SEC_SOURCE_MAP_RULE -->Language
- Default to Korean for user-facing output, headings, notes, and summaries unless the user explicitly asks for English.
- Keep official company names, ticker symbols, SEC form names, accounting labels, accession numbers, and quoted disclosure text exactly as disclosed when precision matters.
Quick Start
- Lock the exact company, ticker or CIK, target forms, and whether the user wants a filing-only pack or an input to a broader memo.
- Prefer the latest
10-Kand10-Qplus latest8-Kmetadata for the default filing set. - Use SEC primary sources first:
data.sec.govsubmissions, SEC XBRLcompanyfacts, and the filing's primary document in/Archives/edgar/data/. - Declare a real
User-Agentfor SEC requests. UseSEC_USER_AGENTor pass--user-agent; keep request cadence below SEC fair-access limits. - If the workspace is writable and the user wants a reusable artifact, write the result to
analysis-example/us/<company>/sec-analysis.md. - For long filings or memo-critical work, also create
analysis-example/us/<company>/sec-reference.mdandanalysis-example/us/<company>/sec-cache.jsonso downstream work can cite the digest/cache without re-fetching the entire filing. - If existing
sec-analysis.md,sec-reference.md, orsec-cache.jsonfiles already exist for the company, read them before re-collecting and only refresh when the requested filing/date scope requires it.
Workflow
- Lock scope. Confirm the ticker or CIK, target form set, latest versus specific period, and the key filing questions.
- Collect SEC data.
Run
scripts/fetch-sec-edgar.jsto resolve ticker-to-CIK, collect submissions, collect companyfacts, select latest forms, download primary filing HTML, and emit text plus JSON artifacts. - Parse filing sections.
Run
scripts/extract-sec-sections.json the relevantlatest-10k.txtorlatest-10q.txtwhen the user needs MD&A, Risk Factors, controls, legal proceedings, or financial-statement sections. - Build a reusable reference.
Run
scripts/build-sec-reference.jsto generatesec-reference.mdandsec-cache.jsonfrom filing export, sections, and facts. - Write the analysis.
Use the default SEC analysis shape from
references/output-format.md, keep every material number source-mapped, and label gaps asnot separately disclosedorneeds_review. - Hand off cleanly.
Use
us-stock-analysisafter this when the user wants thesis, valuation, catalysts, risks, and conclusion.
Read references/workflow.md for the SEC collection and extraction checklist. Read references/output-format.md for the default Korean evidence-pack shape. Read references/script-inputs.md before running the bundled scripts.
Bundled Scripts
scripts/fetch-sec-edgar.jsresolves ticker or CIK, fetches SEC submissions/companyfacts, downloads selected filing HTML, writes filing text files, and emitssec-filing-export.jsonplussec-companyfacts.json.scripts/extract-sec-sections.jsparses 10-K/10-Q Item headings and labels section coverage asparsed,partial,missing, orneeds_review.scripts/build-sec-reference.jsrenderssec-reference.mdandsec-cache.jsonfrom the fetch and section artifacts.- Run all bundled scripts with
node.
Operating Rules
- Do not invent revenue mix, customer concentration, segment profitability, governance facts, or valuation metrics that are not in the current SEC source set.
- Do not derive standalone quarters from year-to-date XBRL facts unless the user explicitly asks and you have the matching prior cumulative fact; v1 should preserve XBRL start/end period facts as disclosed.
- Preserve accession number, form, filed date, period start/end, unit, taxonomy, and source URL for each material XBRL fact.
- Treat SEC XBRL companyfacts as standardized fact evidence, not as a complete substitute for reading the filing text.
- If a company uses only custom taxonomy for a memo-critical metric and companyfacts lacks the standard concept, mark it as
not separately disclosed in standard SEC companyfactsand inspect the filing text. - Keep latest 8-K work metadata-first unless the user asks to parse 8-K items.
- If a filing section parse is
missingorneeds_review, do not convert that intonot separately disclosed. - Keep SEC fair access explicit: declared
User-Agent, efficient downloads, cache reuse, and request cadence below 10 requests/second.
Source Priority
- SEC filing primary document and inline XBRL filing text
- SEC
data.sec.gov/submissions/CIK##########.json - SEC
data.sec.gov/api/xbrl/companyfacts/CIK##########.json - Company IR earnings releases or decks for management commentary
- Reputable news/transcripts only for context, not as a substitute for filing facts
Minimum Output Standard
- Scope with ticker, CIK, company name, forms, accession numbers, filing dates, and period dates
- Latest 10-K and 10-Q filing links, plus latest 8-K metadata when available
- XBRL fact table for revenue, gross profit, operating income, net income, diluted EPS, cash, assets, liabilities, equity, operating cash flow, and capex when disclosed in standard concepts
- MD&A, Risk Factors, financial statements, controls, and other requested filing sections with coverage status
- Clear
not separately disclosedandneeds_reviewnotes - Source Map table another analyst can audit quickly
- Reusable
sec-reference.mdandsec-cache.jsonfor long or memo-critical filing work
Handoff Guidance
- Use
us-stock-analysisafter this when the user wants a final investment memo, valuation, catalysts, risks, or comparison. - If the user's question is mainly "what does the SEC filing actually say", keep the output in SEC analysis mode and stop short of a thesis.
- If an existing
sec-reference.mdorsec-cache.jsoncovers the same accession numbers, cite and update that artifact instead of re-downloading unchanged filings.
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.

