Skip to main content
skill CX Codex

results-season — Claude Code skill for earnings reactions

The results-season Claude Code skill analyzes how NSE and BSE stocks move after quarterly results. It scores price gaps, trading volume, and follow-through.

MIT ★ 69 updated 2026-11-13

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Shubhamkumartrichy/claude-trading-skills-india
/plugin install india-trading-skills@india-trading-skills
Open on GitHub

What results-season does

The skill reads NSE and BSE price data around quarterly results. It selects the reaction session from the announcement time, then measures the gap, return, volume against the prior 50 sessions, and later price movement. Each event gets a weighted score from 0 to 100 and a letter grade.

Commands cover single-stock analysis, event scans, gap checks, and possible entries after a strong rise. The results.py script runs offline on CSV files. A 200-day average needs at least 220 daily bars; ambiguous numeric dates are rejected rather than interpreted.

What it helps with

  • score a stock’s reaction to quarterly results
  • rank reactions across a list of events
  • check whether a price gap has filled
  • find holdings with results during a holding window

Example prompts for the agent

  • Assess TCS’s reaction to results on 2026-10-09 using tcs.csv.
  • Scan the events in q2.csv and rank the stock reactions.
  • Check which of my holdings report between 2026-11-02 and 2026-11-13.

How to install results-season

1Plugin marketplace

/plugin marketplace add Shubhamkumartrichy/claude-trading-skills-india
/plugin install india-trading-skills@india-trading-skills

This installs the whole india-trading-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add Shubhamkumartrichy/claude-trading-skills-india --skill results-season -a claude-code

3Manually: put the files in place

~/.claude/skills/results-season/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/results-season/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about results-season

How do I install results-season in Claude Code?

Add the marketplace with /plugin marketplace add Shubhamkumartrichy/claude-trading-skills-india, then install the skill with /plugin install india-trading-skills@india-trading-skills.

What does results-season do?

It analyzes NSE and BSE stock moves around quarterly results, scores price and volume reaction, and tracks gaps and subsequent movement.

What does results-season need to run?

It needs Python 3 and stock data in CSV files. Calculating the 200-day average requires at least 220 daily bars.

Source text

SKILL.md · MIT
---
name: results-season
description: |
  Reads the price reaction to quarterly results on NSE/BSE stocks. Picks the right reaction session
  from the announcement time (same day for pre-market/market-hours, next NSE session for after-hours,
  weekend or holiday releases), measures gap, close, close location, volume vs 50-day, ATR-normalised
  move, 1-20 session follow-through and gap fill, grades it 0-100 (A-D) with visible weights, watches
  weekly bars for a post-results drift entry or a failed reaction, ranks many events, and lists
  positions whose results fall inside a holding window. results.py works offline from CSVs.

  Use when the user asks: "how did X react to results", "was that a good results reaction", "should
  I buy after the results gap", "post-earnings drift setup in X", "rank this quarter's results
  reactions", "did the gap fill", "which of my holdings report before I exit", "results calendar
  check", or plans a swing trade during results season.
---

# Results Season (NSE/BSE)

`fundamental-screening` reads the numbers. This skill reads the market's verdict on them. The
reaction (how far, on how much volume, where it closed, and whether it held) is more objective
than a headline beat or miss, especially in India, where consensus estimates are not freely available.

## Commands

```bash
# One stock: reaction metrics, then the score (adds factor table and a plain-English read)
python3 scripts/results.py reaction --csv tcs.csv --date 2026-10-09 --timing post-market
python3 scripts/results.py score --symbol HDFCBANK --date 18-Oct-2026 --timing 14:20
# Weekly drift watch after a strong gap-up: pullback that holds the gap-day low, then a breakout
python3 scripts/results.py drift --csv dixon.csv --date 2026-07-24 --timing post-market
# Many events: symbol,date,timing CSV (+ optional file column); CSVs named SYMBOL.csv
python3 scripts/results.py scan --events q2.csv --csv-dir data/ --top 10
# Positions with results inside a holding window (feeds trading-discipline's event check)
python3 scripts/results.py calendar-check --events q2.csv --from 2026-11-02 --to 2026-11-13 --symbols TCS,INFY
```
Inputs follow `technical-analysis` (`--csv`, `--candles`, `--symbol`). Dates are ISO (2026-10-31) or
NSE style (31-Oct-2026); a numeric date that could be DD/MM or MM/DD is refused, never guessed.
`--timing` is pre-market, market-hours, post-market, or the filing time (16:05, read as IST). Every
command takes `--json`. Bad input exits 2 with one `error:` line. Use 220+ daily bars for the 200-DMA.

## Which session is the reaction?

| Announced | Reaction session |
|---|---|
| Before 09:15 on a trading day | Same day: the open is the verdict |
| 09:15–15:30 | Same day. The open came before the news, so read the close, not the gap |
| 15:00–15:30 | Same day, flagged: NSE's close is the volume-weighted price of the last 30 minutes, so part of the move lands next session |
| After 15:30, or a weekend/holiday | Next NSE session (holiday list from `../fno-options-analysis/scripts/options.py`) |

Some companies hold results board meetings on Saturdays, and those react on Monday. Muhurat or
special sessions in the data are skipped and flagged. Use `--reaction-date` to override.

## Reading `reaction` and `score`

`reaction` reports gap %, reaction-day return, close location (0 = low, 1 = high), volume ÷ the
prior 50 sessions, ATR(14) as of the day before, follow-through at +1/3/5/10/20 sessions (vs the
reaction close and vs the pre-results close, and whether the reaction-day low held), and whether
the gap filled.

| Factor | Weight | Full marks | Why |
|---|---|---|---|
| Reaction size | 35 | close ≥ +3 ATR vs pre-results close | ATR scales the move to the stock's usual noise; the close is what the market kept |
| Volume expansion | 20 | 4× the 50-day average (1× = 0) | Funds re-rating a stock can't hide their size |
| Close strength | 15 | closed at the day's high | A faded gap means holders used the news to sell |
| Trend position | 20 | above 200-DMA (7), above 50-DMA (6), at the pre-results 52-week high (7, zero at −10%) | Gaps into new highs meet no trapped sellers |
| Fresh surprise | 10 | ≤ +10% in the 60 sessions before results (zero at +40%) | A big run-up often means the news was already priced in |

Volume, trend and fresh surprise are context, so they are multiplied by a **gate**: 0 for a flat or
negative close and 1 from +1 ATR up. A stock in a perfect uptrend that does nothing on results earns
little. Missing data (no volume, under 200 bars) drops that factor and rescales the total to 100.
Grades: **A ≥80, B ≥60, C ≥40, D below**. The score is long-biased. A strong negative reaction is a D
with a bearish read.

## Reading `drift`

Runs only after a strong gap-up: gap or close ≥ `--min-gap-pct` (4%) with a green close. Weeks
start after the reaction week.
- **Failed:** any daily close below the gap-day low. The reaction was rejected, so drop it.
- **Pullback-set:** the first red weekly candle whose low stays above the gap-day low. The trigger is
  that week's high, and the stop is its low minus `--stop-buffer-pct` (0.5%). Further red weeks
  extend the pullback and lower the trigger. A week that dips under the gap-day low intraday but
  closes above it is noted as a shakeout.
- **Triggered / stopped:** the later breakout above the trigger (a gap above it fills at the open),
  then the stop check. Reports R so far. **Expired:** no entry within `--max-weeks` (12).

Feed the trigger and stop to `../breakout-planner/scripts/breakout.py plan --pivot .. --stop ..` for
ticks, size and GTT orders.

## India context

- **Deadlines (SEBI LODR Reg 33(3)):** Q1–Q3 results within 45 days of quarter end (14 Aug, 14 Nov,
  14 Feb). Q4 comes with the audited annual results within 60 days of the FY end (30 May).
  `calendar-check` prints the season deadline and flags positions with no known date.
- **Notice (Reg 29):** the board meeting to approve results must be intimated at least 2 working
  days ahead, excluding the intimation and meeting days. This has applied since the 17-May-2024
  amendment; it was 5 days before that. Exchange board-meeting lists therefore cover only the next
  few days. Re-check them during long holds.
- **Timing (Sch III Part A):** the outcome must be filed within 30 minutes of the meeting ending, so
  results can land mid-session as well as after 15:30. Use the filing timestamp.
- **F&O stocks:** implied volatility builds into results and collapses after (IV crush). Option
  buyers can be right on direction and still lose. Compare the IV-implied move from
  `fno-options-analysis` with the realised ATR move here.
- **Non-F&O stocks** have 5/10/20% price bands. A results-day upper circuit means buyers may not have
  been filled. A lower circuit traps holders, and stops do not fill. The script flags closes pinned
  at a band.
- **No free consensus.** Judge the numbers by YoY growth first (seasonality), then QoQ, plus margins
  and management commentary (`fundamental-screening`). The reaction shows how they compared with
  what the market expected.

## How it connects

- `india-market-analyst`: avoid fresh swing entries just before results. Run `calendar-check` before
  any multi-day plan.
- `trading-discipline`: an INSIDE row from `calendar-check` means the gate gets `--event yes`.
- `momentum-scanner`: a grade-A gap out of a quiet base is an episodic pivot candidate.
- `breakout-planner`: a pivot within ~5 sessions of results is a coin toss. After the event, the
  drift trigger is a cleaner pivot.
- `trailing-stops`: manage a triggered drift trade (breakeven at 1R).

## Limits

These are daily bars only: no intraday order of events, no delivery %, no option IV. Reactions to
other news on the same day (block deals, index inclusion, market-wide gaps) look like results
reactions, so check the NIFTY move that day. Thresholds are conventions, not fitted parameters.

_Educational analysis, not investment advice._

© Shubham Kumar · MIT · Shubhamkumartrichy/claude-trading-skills-india

Similar skills

All skills for Finance and business →

From the same set36

The whole set →
indian-tax-for-traders The indian-tax-for-traders Claude Code skill explains Indian tax treatment of stock-market income for resident individuals. It helps classify trades, estimate tax, and choose an ITR form. CX Codex +1 ★ 69repo stars fno-options-analysis The fno-options-analysis Claude Code skill analyses Indian futures and options, including option chains, volatility, Greeks and expiries. It activates for questions about NIFTY, PCR, India VIX, margins or expiry rules. CX Codex +1 ★ 69repo stars breakout-planner breakout-planner — a Claude Code skill that evaluates breakout setups for NSE/BSE stocks and works out a trade plan. It responds to requests about Stage 2 trends, bases, entry points, or scanning a stock list. CX Codex +1 ★ 69repo stars stock-screener The stock-screener Claude Code skill filters and ranks Indian stocks using fundamentals from a CSV. It runs on requests to screen a company list, find stocks by financial criteria, or explain a failed rule. CX Codex +1 ★ 69repo stars portfolio-review The portfolio-review Claude Code skill reviews Indian stock portfolios for concentration, risk and rebalancing options. It runs on requests to assess a portfolio or after a broker holdings file is uploaded. CX Codex +1 ★ 69repo stars market-regime The market-regime Claude Code skill classifies market conditions from index or ETF data. It runs on questions about NIFTY’s trend and exposure before new trades. CX Codex +1 ★ 69repo stars momentum-scanner The momentum-scanner Claude Code skill scans NSE/BSE stocks for short-term momentum. It responds to requests about breakouts, news gaps and relative-strength rankings. CX Codex +1 ★ 69repo stars trading-discipline The trading-discipline Claude Code skill checks trade plans before an order and calculates allowed risk from a journal. It responds to questions about taking a trade, loss limits, or a losing streak. CX Codex +1 ★ 69repo stars

Project sponsors

Companies that keep this analytics open