agentsclimarketplace

Technical analysis

Skill blaze10011/market-flow-desk/.claude/skills/technical-analysis

Full technical report card + volatility-sized trade plan for a single stock (the "#6 Citadel" skill). Use when the user asks "should I buy/sell <ticker>", "what's the setup on <ticker>", "give me entry/stop/target for <ticker>", "is <ticker> a buy here", "technical read on <ticker>", or wants a trade plan with position size for a specific name before acting.From its SKILL.md

Install
npx -y skills add blaze10011/market-flow-desk --skill technical-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 603 tokens by cl100k_base, as published. Nobody here has run it

Technical Analysis (#6 — Citadel)

Give the user a clear technical report card AND a disciplined trade plan that fixes their #1 weakness: cutting winners early / letting losers run. Every plan must have a stop, a target at ≥2:1, and a volatility-based size.

Steps

  1. Run the engine from the project root (pass the user's account size and risk % if they gave them; defaults are $20,000 and 1%): python3 scripts/technical.py <TICKER> [--account 20000] [--risk 1] It prints: trend vs 50/100/200-DMA, RSI, MACD, Bollinger, ATR, volume, support/resistance, 52-week range, and a TRADE PLAN (beta to SMH, entry, ATR-based stop, 2:1 target, share count, $ at risk, sector-equivalent exposure).

  2. Interpret only what the script printed (never invent prices, levels, or beta). Translate each line into plain English:

    • Trend + MA stack = the direction and whether price is leading or lagging.
    • RSI >70 overbought / <30 oversold / else neutral; MACD bull/bear = momentum; Bollinger %band = stretched vs mid.
    • Volume: heavy on the move = conviction; light = weak/profit-taking.
    • ATR% = how much it swings daily (sets stop width). Beta = how hard it moves vs the chip sector.
  3. Deliver a report card with a clear verdict, in this shape:

    • Setup: one-line read (e.g. "uptrend, but extended and momentum cooling").
    • Key levels: support / resistance / 50-DMA from the data.
    • Trade plan: entry, stop, target, R:R, share size + $ at risk (straight from the script).
    • Confidence: strong buy / buy / neutral / sell / strong sell — with one-line reasoning.
  4. Always close with the discipline rules (this is the point of the skill):

    • Honor the stop — it's set at 1.5× ATR so normal noise won't hit it; if it does, the thesis is wrong, exit.
    • Hold to the target — don't book a tiny gain; the 2:1 target is what fixes the payoff-ratio leak.
    • The size already accounts for volatility (high-ATR/high-beta names get fewer shares). Don't oversize past it.

Horizons: short-term = 1–3 days, long-term = 14–20 days — give a lean for each when relevant. Decision support, NOT a buy/sell signal. Data ~15-min delayed. Always pair a lean with a level and what invalidates it.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,645. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.