← ClaudeAtlas

topxai-equity-researchlisted

Institutional-grade equity, industry and macro research workflow for AI agents. Use it whenever the user wants a stock deep dive, an industry or value-chain report, a macro / strategy note, an earnings-season update of an existing report, a valuation with scenarios and a settleable rating, a bull/bear debate on a company, an adversarial audit of a research draft, SEC EDGAR / XBRL financial pulls, or to register, track and settle research calls (coverage watch, call ledger, track record). Also use it for Chinese requests such as 写研报, 个股深度, 产业链报告, 更新研报, 结算台账, 跑值守, even when the user does not say "research report". Every number must trace to a primary source with an evidence grade; every conclusion must be falsifiable; ratings are research judgments, never personalised investment advice.
UnbelievableT/topxai-equity-research · ★ 0 · AI & Automation · score 78
Install: claude install-skill UnbelievableT/topxai-equity-research
# TopxAI Equity Research A research desk in a skill: it takes a company, a value chain or a macro question from kickoff to a published report, then keeps watching the calls the report made and settles each one when it comes due. The method is built for reports that a professional reader would pay for, so it is strict about evidence and about saying how you could be wrong. **The whole system in one sentence.** Markets, earnings and news are *outcomes*. A report earns its keep by explaining the *process* (how the mechanism works) and the *next step* (what follows from it), plus the *observation points* (how you will know you were wrong). A well-written summary of outcomes is a news digest, worth nothing. Answer in the user's language. The method files are in English; the report can be written in any language, and multi-language editions must match number for number (see `references/pipeline/05-publish.md`). ## How to use this skill 1. Find the step you are on in the **pipeline map** below. A new report starts at step 1; settling calls, the coverage watch and updates have their own entry points. 2. Read only that step's file and the method files the map names for it. Do not load everything at once. 3. Every step writes files under `research/<report-id>/` in the user's project and has an exit gate. Move on only when the gate passes. 4. You are the **editor**: you run the desk and do the deterministic work yourself (assembling, running scripts, registering calls). Re