us-stock-analysis
Skill2 starsChanged 8 days agoMITView on GitHub
Build dated, source-backed analysis for U.S. public companies and U.S.-listed ETFs. Use when analyzing a U.S. ticker, comparing U.S. stocks, preparing a pre-earnings or post-earnings memo, assessing valuation, summarizing an investment thesis, reviewing catalysts and risks, or adding style-specific U.S. growth stock, U.S. value stock, ETF, peer valuation, or chart analysis using current filings, investor materials, and recent news.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- KCNyu/clawocktheir own version, first seen Aug 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- KCNyu/clawock★ 23same name
- IngAs8/ClaudeSkill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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-sec-analysisSkill
- us-strategy-backtestSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 15 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to produce equity research style analysis for U.S.
- Distinctive: line 12
Treat prices, market caps, financial statements, guidance, analyst estimates, ownership, regulations, and news as time-sensitive.
- Distinctive: line 13
Prefer primary sources first: SEC filings, investor relations pages, earnings releases, earnings decks, transcripts, exchange …
- Very specific: line 15
If the workspace is writable, treat the default deliverable as a markdown report file, not just a chat reply.
- Very specific: line 16
If exact SEC filing support matters, use us-sec-analysis first.
- Distinctive: line 25
Read current price context, recent SEC filings, the latest earnings package, and any recent company-specific news needed for the question.
- Distinctive: line 31
Check balance sheet strength, cash generation, dilution, cyclicality, customer concentration, regulatory risk, and plausible bear cases.
- Distinctive: line 33
Use simple, defensible valuation methods that fit the business.
- Distinctive: line 35
Create or update the report file first when the workspace is writable, then lead with the conclusion, evidence, valuation, catalysts, …
- Distinctive: line 37
Read references/workflow.md for the detailed checklist.
- Distinctive: line 38
Read references/us-style-checklists.md when analyzing U.S.
- Distinctive: line 39
Read references/output-format.md for answer templates.
- Distinctive: line 40
Read references/script-inputs.md when using the bundled scripts with structured JSON inputs.
- Very specific: line 44
Use scripts/peer-valuation.js when the user provides peer metrics and you need a consistent markdown comparison table.
- Very specific: line 45
Use scripts/etf-overlap.js when the user provides two ETF holdings files and you need weighted overlap, common names, and top overlaps.
- Very specific: line 46
Use scripts/chart-basics.js when the user provides OHLCV price history and you need a basic technical read on trend, momentum, and volume …
- Very specific: line 47
Run all bundled scripts with node.
- Distinctive: line 52
Use exact dates for earnings, filings, guidance, and news.
- Distinctive: line 54
Prefer ranges and scenarios over false precision.
- Distinctive: line 56
If the user asks for portfolio sizing, tax, or personal suitability, keep the response informational unless the user provides those …
- Distinctive: line 57
If you produced a full single-stock memo, keep the file deliverable synchronized with the final chat answer rather than letting the report …
- Very specific: line 58
Do not re-collect SEC filings blindly when a matching sec-reference.md or sec-cache.json already covers the accession numbers being used.
- Very specific: line 67
Use us-sec-analysis as the SEC filing-precision stage when exact filing evidence is more important than a broad investment memo.
≈ “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. Stock Analysis
Use this skill to produce equity research style analysis for U.S. stocks and U.S.-listed ETFs without relying on stale memory.
Quick Start
- Treat prices, market caps, financial statements, guidance, analyst estimates, ownership, regulations, and news as time-sensitive. Verify them with current sources before using them.
- Prefer primary sources first: SEC filings, investor relations pages, earnings releases, earnings decks, transcripts, exchange announcements, ETF fact sheets, and official macro data.
- Pin the scope before analyzing: ticker, exchange, analysis horizon, comparison set, and the desired output type.
- If the workspace is writable, treat the default deliverable as a markdown report file, not just a chat reply. For a U.S. stock or ETF, create or update
analysis-example/us/<company>/memo.md. - If exact SEC filing support matters, use
us-sec-analysisfirst. Read any existinganalysis-example/us/<company>/sec-analysis.md,sec-reference.md, orsec-cache.jsonbefore re-fetching filings. - Open every memo with a
한줄요약line directly under the title: one sentence of at most 50 characters that states the conclusion. Seereferences/output-format.md. - State an explicit "as of" date in the final answer.
Workflow
- Define the task. Capture the security, market, user goal, time horizon, and whether the user wants a quick view, a deep memo, a comparison, or an event-driven read.
- Gather verified facts.
Read current price context, recent SEC filings, the latest earnings package, and any recent company-specific news needed for the question.
2A. Add SEC precision when needed.
For filing-sensitive claims about reported results, MD&A, Risk Factors, liquidity, cash flow, segment disclosure, controls, or exact XBRL facts, route through
us-sec-analysisand ingest itssec-reference.md/sec-cache.jsonartifacts before drafting. - Build the thesis. Explain what drives the business, why the market may be underpricing or overpricing it, and which metrics matter most for this business model.
- Stress test the idea. Check balance sheet strength, cash generation, dilution, cyclicality, customer concentration, regulatory risk, and plausible bear cases.
- Value the security. Use simple, defensible valuation methods that fit the business. Do not force a DCF when the inputs are too weak.
- Write the answer. Create or update the report file first when the workspace is writable, then lead with the conclusion, evidence, valuation, catalysts, risks, and what would change the view.
Read references/workflow.md for the detailed checklist. Read references/us-style-checklists.md when analyzing U.S. growth stocks, U.S. value stocks, or ETFs. Read references/output-format.md for answer templates. Read references/script-inputs.md when using the bundled scripts with structured JSON inputs.
Bundled Scripts
- Use
scripts/peer-valuation.jswhen the user provides peer metrics and you need a consistent markdown comparison table. - Use
scripts/etf-overlap.jswhen the user provides two ETF holdings files and you need weighted overlap, common names, and top overlaps. - Use
scripts/chart-basics.jswhen the user provides OHLCV price history and you need a basic technical read on trend, momentum, and volume regime. - Run all bundled scripts with
node.
Operating Rules
- Cite where each important factual claim came from.
- Use exact dates for earnings, filings, guidance, and news.
- Separate verified facts from your inference.
- Prefer ranges and scenarios over false precision.
- Say when data is missing or uncertain.
- If the user asks for portfolio sizing, tax, or personal suitability, keep the response informational unless the user provides those constraints explicitly.
- If you produced a full single-stock memo, keep the file deliverable synchronized with the final chat answer rather than letting the report drift.
- Do not re-collect SEC filings blindly when a matching
sec-reference.mdorsec-cache.jsonalready covers the accession numbers being used.
Source Priority
- SEC filings and official investor relations materials
- Exchange notices and fund sponsor documents
- Official macro or industry data
- Reputable news and transcript providers for context
Use us-sec-analysis as the SEC filing-precision stage when exact filing evidence is more important than a broad investment memo.
Minimum Output Standard
- Summary judgment
- What the business does and what matters most
- Evidence from current results and balance sheet
- Valuation view with at least one comparable metric
- Catalysts
- Risks and disconfirming evidence
- Clear "what would change my mind" section
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.

