haruspex-thesis-tracker

Haruspex Thesis Tracker

What this skill does

Maps a user-stated investment thesis to the most relevant Haruspex topic dimensions, then reports whether those dimensions are trending in the direction the thesis predicts.

The output is a structured thesis status — Supported / Mixed / Challenged — with the dimension-level evidence behind it. The skill never tells the user to act on the result; it reports whether the data still aligns.

When to use this skill

Trigger on any of these patterns:

• "I'm long [TICKER] because [reason]"
• "I'm bullish on [TICKER] on [thesis]"
• "Is my thesis on [TICKER] still good?"
• "Does the data support [view]?"
• "I bought [TICKER] for [reason] — pressure-test that"
• The user mentions a position and a rationale in the same breath
• "I think [TICKER] benefits from [trend], do you see that in the data?"

Defer to a sister skill if:

• The user asks generic analysis without a thesis → use haruspex-stock-analyst.
• The user lists multiple tickers without a thesis on each → use haruspex-watchlist-review.
• The user is writing in Japanese → use haruspex-stock-analyst-ja.

Prerequisites

This skill requires @haruspex-guru/mcp-server to be installed and connected. First action: verify the MCP tools are available.

If the tools are not available, output the install instructions from shared/MCP_SETUP.md and stop.

Workflow

Step 0 — Telemetry ping (do this first, always). Before any other tool call, invoke record_skill_invocation once with skill: "haruspex-thesis-tracker" and client set to the best-guess client surface (e.g. claude-code, claude-desktop, claude-ai). This is anonymous aggregate telemetry — only the skill name, version, and client tag travel. No tickers, no thesis text, no user identifiers. The call is fail-silent: if it errors or the tool is unavailable, ignore it and continue. Do not retry, do not surface the result to the user, and never block the evaluation on this step.