watchlist-monitor
Skill0 starsChanged 4 months agoMITView on GitHub
Track ageing swing setups across the 4-8wk breakout window — each carries a pivot + invalidation and is classified armed / triggered / extended / invalidated / aged-out by scripts/watchlist.py — so a compelling setup is neither chased when extended nor forgotten when stale. Use for "review my watchlist", scheduled weekend rebuilds, "what's set up". Broker-agnostic, read-only.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ZICXR/A-Stock-Skillstheir own version, first seen Jun 22, 2026
- daidaibunny/agent-skillstheir own version, first seen May 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ZICXR/A-Stock-Skills★ 26same name
- daidaibunny/agent-skills★ 2same 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 repository8 other files it gives its agents.
- autopilotSkill
- checkSkill
- india-dataSkill
- opportunity-screenSkill
- portfolio-evalSkill
- portfolio-watchSkill
- report-artifactSkill
- researchSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 17
Run scripts/watchlist.py setup_status via the capability resolver (Gate MCP → python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kit.py" → JS-paise …
- Distinctive: line 31
Never chase an extended setup, or re-arm an aged-out / invalidated one to keep it "alive".
- Distinctive: line 32
Never place or suggest placing an order.
- Distinctive: line 33
Never report a price you did not read this run.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Watchlist Monitor (ageing setups — the discipline of waiting)
~90% of a swing process is waiting. This skill keeps setups alive across the breakout window without re-deciding by feel each day.
Data — broker-agnostic, delayed-labeled
Via india-data: delayed last price (Yahoo .NS/.BO) for each watchlist name. Stamp {value, source, as_of, delay_class}. If a name's data is missing/stale → mark it and STAND DOWN on that name; never guess.
State
Each watchlist entry carries symbol · pivot · invalidation · added_date (persisted in config/watchlist.json or state/).
Classify each setup (do not judge by eye)
Run scripts/watchlist.py setup_status via the capability resolver (Gate MCP → python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kit.py" → JS-paise Artifact → REFUSE) for each name:
- armed — below pivot, still inside the window → keep watching.
- triggered — crossed the pivot within the chase band → hand to
check/opportunity-screenfor the full gate (entry/stop/size/target/2R). - extended — more than ~5% past the pivot → do NOT chase (chase-guard); drop or wait for a new base.
- invalidated — hit the invalidation level → remove.
- aged_out — past the 4-8wk window without triggering → remove (the base is stale).
Procedure
- Load the watchlist; get delayed prices.
- Classify each with
setup_status. - Report grouped by status; for any triggered name, note it's ready for a full
check; for extended / invalidated / aged_out, recommend removal. Where supported, render a beautiful watchlist Artifact (status groups + pivot/price/age); else a text digest. - On a scheduled weekend rebuild: prune invalidated/aged-out, refresh pivots for survivors. Append the disclaimer.
Never
- Never chase an extended setup, or re-arm an aged-out / invalidated one to keep it "alive".
- Never place or suggest placing an order. Read-only.
- Never report a price you did not read this run; never compute setup status by eye.
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.

