sector-price-driver-patterns
Skill9 starsChanged 41 days agoNo licenceView on GitHub
Explain what drove stock prices across a sector, theme, or value chain over a past period and find the tested pattern separating winners from losers: which layers led or lagged, how much of the move was macro versus company-specific, synchronized sell-offs and their triggers, beats that were sold, and where fundamentals and price diverged. Historical analysis only: no trade ideas, setups or long/short calls. Distilla MCP first; web search only for macro triggers. Use whenever the user asks why a group of stocks moved, what drove a sector or theme, "why did the [theme] value chain move over the last N months", whether there is a pattern across a value chain, or which layer/sub-industry led or lagged (e.g. AI infrastructure, GLP-1, defense, uranium, EV supply chain, China internet), even without the words "value chain". Do NOT use when the user asks for today''s setup, trade ideas or positioning (use sector-price-driver-review), for a single-stock question, or for general market commentary with no sector focus.
In this repository36 other files it gives its agents.
- bull-signal-screenSkill
- capacity-utilizationSkill
- capex-cycleSkill
- company-briefSkill
- competitive-positionSkill
- consumer-brand-equitySkill
- cycle-positioningSkill
- daily-briefSkill
- dcf-modelingSkill
- distribution-channelsSkill
- earnings-digestSkill
- earnings-previewSkill
- earnings-revisionsSkill
- financial-statement-reviewSkill
- fundamental-guruSkill
- growth-profileSkill
- industry-analysisSkill
- initial-screenSkill
- long-short-ideasSkill
- management-governanceSkill
- manufacturing-cost-structureSkill
- peer-benchmarkingSkill
- profit-pool-analysisSkill
- roe-decompositionSkill
- sector-price-driver-reviewSkill
- sell-side-briefSkill
- sell-side-viewSkill
- sentiment-readSkill
- special-situations-screenSkill
- stock-screenerSkill
- supply-chain-resilienceSkill
- technical-analysisSkill
- technology-positionSkill
- thematic-winnersSkill
- valuation-compression-recoverySkill
- x-discourseSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 18 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.