Syntic
← All skills
ScreeningFreeCommunityv1.0.0

stockbee-exhaustion-hammer-screener

Use when the user wants Stockbee/Pradeep-Bonde-style selling-exhaustion hammer setups: undercut/reclaim reversals, long-lower-wick candidates, or pullback entries in strong, liquid stocks.

About this skill

Use when the user wants Stockbee/Pradeep-Bonde-style selling-exhaustion hammer setups: undercut/reclaim reversals, long-lower-wick candidates, or pullback entries in strong, liquid stocks.

SKILL.md

stockbee-exhaustion-hammer-screener.SKILL.md

Place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.

SKILL.md
---
name: stockbee-exhaustion-hammer-screener
description: Use when the user wants Stockbee/Pradeep-Bonde-style selling-exhaustion hammer setups: undercut/reclaim reversals, long-lower-wick candidates, or pullback entries in strong, liquid stocks.
category: Screening
version: 1.0.0
tools: []
---

# Stockbee Exhaustion Hammer Screener

Screen US equities for Stockbee-style (Pradeep Bonde) selling-exhaustion hammer candidates. This is a candidate-generation and setup-quality workflow — it surfaces and scores candidates for human review, not a signal service or auto-execution system.

## When to Use
Use when the user asks for Stockbee or Pradeep Bonde style exhaustion setups, near-close hammer / long-lower-wick reversal candidates, a scan of strong liquid stocks that pulled back and may be showing selling exhaustion, undercut/reclaim candidates near or after the close, or supplies a symbol list / OHLCV data to screen. Run this only when the broader market-regime read allows taking on new swing risk; otherwise mark any output as manual-review-only rather than actionable.

## Setup Families Detected
- **Selling exhaustion hammer**: a long lower wick, small body, strong close-location (close near the high of the bar), and a clear recovery off the day's low.
- **Undercut/reclaim hammer**: the day's low undercuts the prior short-term low, and the near-close price reclaims back above that level.
- **Prior momentum pullback**: a recent high formed within a defined lookback window, followed by a controlled pullback rather than a sustained downtrend.
- **Quality/liquidity context**: price, volume, 20-day average dollar volume, market cap, and — when available — institutional/fund-holder metadata.

## Scoring
Score each candidate across: quality/liquidity, prior momentum, pullback and selling-exhaustion context, hammer candle geometry (lower wick, body, upper wick, close location, recovery off the low), risk distance to the day low plus a buffer, and alignment with the broader market gate (allowed/restricted for new risk).

## Presenting Results
For each candidate report: the trigger type and every matched tag; pullback depth from the recent high and days since that high; undercut/reclaim status and the short-term prior low; hammer geometry (lower wick, body, upper wick, close location, recovery from the low); volume ratios and average dollar volume; entry reference, stop reference, and risk percentage to the stop; the setup score, rating, state, and any reject reasons; and a suggested next action.

## Acting on Results
Use output conservatively, gated by grade: **A / A-** candidates — validate the chart manually and check earnings/news risk before treating as a real position candidate; **B** candidates — manual review, or wait for a next-day hammer-high confirmation; **watch** candidates — keep on a watchlist and wait for follow-through or tighter risk before acting; **rejected** candidates — keep for post-analysis only, not for action. For deeper chart validation or position sizing on survivors, @mention a teammate who covers technical analysis or risk sizing.

Install

Syntic App

  1. 1Create a dedicated folder for this skill in your local skills library.
  2. 2Place SKILL.md into that folder.
  3. 3Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

  1. 1Save SKILL.md in your local Syntic Code skills directory.
  2. 2Keep related files in the same skill folder.
  3. 3Run in a safe environment and validate outputs.