---
name: ask-the-desks-view
description: Get RingMaster's own view of one ticker: its side, bullish, bearish or neutral, over the near time frames and the long ones. It also gives the two levels the desk watches. Use when the user asks which way a name is headed, or whether it is bullish or bearish. Also for a buy or sell read on a named security.
---

# Ask the desk's view

Trigger on: a ticker plus a question about direction.

- "Is X bullish or bearish". "Where is X headed".
- "Short term and long term on X". "What is your view on X".
- "Is X a buy or a sell". "What do you make of X".

This is the question the desk exists to answer, and it answers it. Do not
reach for `get_name_card` and assemble a view of your own out of the ranks.
The desk publishes one, the same one for every reader, and repeating it is
the job.

1. Call `get_desk_view` with the ticker. One call answers the whole question.
2. Open with the `statement` field, in the desk's own words. It carries the
   side, bullish, bearish or neutral, from the side the desk measured,
   and how the name ranks at 10, 20 and 45 trading days. Name the state by
   its `stateLabel`, such as Bearish, low confidence, Low RV or Not ranked. Never
   print a `signalState` id.
3. If `horizonsSplit` is true, give BOTH halves. The near ranks and the long
   ranks disagree, and the desk publishes both. Flattening them into one word
   is the one thing that answer must not become.
4. Give the trade when one is priced. `lines` carries Trade, Risk, Exit and
   Earnings right under the Signal line: the legs and the limit, the paper max
   loss and max gain, the one stop with its time stop, and the report date.
   Quote them as written. A Trade line that says no option trade says why.
5. Give the `levels` block, keyed `below` and `above`, one either side of the
   last close. Each is a price the name already turned at, with its date.
   When a trade is priced, its Exit line holds the one stop and the two
   levels are chart context. With no trade, lead with the level whose
   `invalidatesTheLean` is true: a close through it would put the price
   action against the desk's view. Never say a price will reach one.
6. Asked for a price target or the chance of a move, say the desk has no price
   model and no probability model. A win rate for a rank says
   nothing about where one stock will go. Then give the rank and the levels
   it does publish.
7. Close with the `label` field, word for word. Every answer that carries a
   view ends with it.

What this skill will not do: answer about the reader's own holdings, their
plan, their money or what they personally should do. The desk writes one view
about a security and hands the same one to everybody. Asked about a position
somebody holds, give the view of the name and say that is what the desk
publishes.

Going deeper on the same name, after the view:

- `get_price_history` for the bars the view was computed from.
- `get_name_card` for the ranks, the volatility outlook and the option chain.
- `get_analyst_note` for the desk's evening column.
- `get_headlines` with scope name for that ticker's own recent headlines,
  each carrying a one line take drawn from the same figures as the view.