uptrend-analyzer
Skill4 starsChanged 2 months agoMITView on GitHub
Use this skill to score how many stocks in a universe are in an established "stage 2" uptrend (price above the 50-day MA, 50-day MA above the 200-day MA) from a plain CSV, no market-data API required. Trigger on "uptrend participation", "stage 2 stocks", "how many stocks are in an uptrend", "50 MA above 200 MA screen". Pairs with [market-breadth-analyzer](../market-breadth-analyzer/SKILL.md) for a fuller market-regime read.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 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 repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/CLAUDE.mdCLAUDE.md
- deep-planningSkill
- deep-planningSkill
- deprecatedSkill
- architecture-reviewSkill
- code-reviewSkill
- diagnoseSkill
- tddSkill
- ui-design-engineeringSkill
- ux-ui-design-assessmentSkill
- in-progressSkill
- mcp-tool-managementSkill
- skill-managementSkill
- obsidian-canvasSkill
- obsidian-markdownSkill
- obsidian-notion-bridgeSkill
- obsidian-vault-workflowSkill
- boomz-preferencesSkill
- personal-agent-workflowSkill
- personalSkill
- automation-designSkill
- grill-with-docsSkill
- handoffSkill
- inbox-meeting-triageSkill
- markdown-reportSkill
- prompt-improvementSkill
- project-docs-prepSkill
- claim-citation-checkSkill
- daily-news-reportSkill
- github-skill-researchSkill
- project-discoverySkill
- repo-tourSkill
- research-methodologySkill
- seo-website-evaluatorSkill
- thaiSkill
- thai-addressSkill
- thai-customer-serviceSkill
- thai-date-formatSkill
- thai-festival-cardSkill
- thai-government-formSkill
- thai-id-validateSkill
- thai-invoiceSkill
- thai-pdpaSkill
- thai-resumeSkill
- thai-social-captionSkill
- thai-text-processingSkill
- thai-translateSkill
- backtest-expertSkill
- dividend-value-screenerSkill
- drawdown-circuit-breakerSkill
- exposure-coachSkill
- market-breadth-analyzerSkill
- portfolio-managerSkill
- position-sizerSkill
- tradingSkill
- trader-memory-coreSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 23
Only one moving average is available (no 50-day and 200-day both) — this test specifically needs both.
- Very specific: line 44
Run python3 uptrend.py for the self-test.
- Distinctive: line 49
Does not fetch data; accuracy depends entirely on the CSV the user supplies.
≈ “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
Uptrend Analyzer
Overview
market-breadth-analyzer asks "is price above one moving average?" This skill asks a stricter question: is the stock in an established uptrend structure — price above its 50-day MA, and the 50-day MA itself above the 200-day MA. That two-part test (a well-known heuristic associated with Stan Weinstein's stage analysis, also used in CANSLIM/Minervini-style trend approaches) filters out stocks that are merely bouncing from a downtrend but haven't structurally turned yet.
Not financial advice. This is a descriptive screen over data you supply, not a buy signal.
When to use
- คัดหุ้นที่อยู่ใน uptrend จริงๆ (ไม่ใช่แค่ราคาสูงกว่า MA เส้นเดียว)
- Scoring what fraction of a watchlist/index is in a "stage 2" structure
- Part of a market-regime or swing-candidate pre-screen (combine with a fundamental/technical screener like dividend-value-screener for the value side, or a breakout screener for the momentum side)
When NOT to use
- The user wants a short-term momentum/breakout signal — this skill measures structural trend state, not entry timing
- Only one moving average is available (no 50-day and 200-day both) — this test specifically needs both; use market-breadth-analyzer instead with whatever single MA is available
Core knowledge
Definition: price > 50-day MA AND 50-day MA > 200-day MA. Both legs matter — price above a declining or flat 50-day MA that hasn't yet crossed above the 200-day MA is typically still a base or early recovery, not an established uptrend by this definition.
This is one of several published trend-classification heuristics (Weinstein's four-stage model is the origin; CANSLIM and Minervini-style trend templates use variations with additional legs — e.g. price also above the 150-day MA, MAs in the correct order, price a meaningful distance above a 52-week low). This skill implements the simplified two-leg version; treat the result as a starting filter, not a complete trend-template screen.
Common mistakes
- Screening only on "price above 50-day MA" and calling it an uptrend — that alone doesn't distinguish an established uptrend from a stock still recovering inside a longer downtrend (missing the "50MA > 200MA" leg).
- Treating this as a complete trend-template screen — real trend-template methodologies (e.g. Minervini's 8-point template) add more conditions (distance from 52-week high/low, relative strength rank) that this simplified skill does not implement.
- Using the uptrend percentage as a timing signal for individual entries rather than a market-wide participation read.
Code
uptrend.py — no dependencies:
is_in_uptrend(price, ma50, ma200)→boolcompute_uptrend_participation(rows)→UptrendResult(total, in_uptrend, excluded, pct_uptrend)
Run python3 uptrend.py for the self-test.
Known limitations
- Implements the simplified two-leg heuristic only — not a full multi-criterion trend template.
- Does not fetch data; accuracy depends entirely on the CSV the user supplies.
- "Uptrend by this test" is a structural classification, not a prediction — a stock can satisfy the test and still decline from here.
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.

