mcpbeat

Insider Trading

staskh/insider-trading

Get insider trading activity (SEC Form 4 filings) for one or more stocks. Use when user asks about insider buying/selling, executive transactions, insider sentiment, or Form 4 activity.

643 tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
308
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/staskh/trading_skills --skill insider-trading

The instruction itself

7 sections, as written by the author

Insider Trading

Fetch recent insider transactions from Yahoo Finance (SEC Form 4 data).

Instructions

> Note: If uv is not installed or pyproject.toml is not found, replace uv run python with python in all commands below.

uv run python scripts/insider_trading.py SYMBOLS [--days DAYS]

Arguments

  • SYMBOLS - Single ticker or comma-separated list (e.g., NVDA or NVDA,PLTR,GOOG)
  • --days - Trailing days to look back (default: 90)

Output

Returns JSON with:

  • transactions - List of insider trades with insider name, role, transaction type, shares, price, value, date, ownership type
  • summary - Net sentiment (net_buying, net_selling, neutral), buy/sell counts and values

For multiple symbols, results are ranked by net buying value (most buying first).

Use Cases

  • *"Show me insider buys for NVDA in the last 90 days"*
  • *"Compare insider activity across NVDA, PLTR, GOOG"*
  • *"Which of these stocks has the most insider selling recently?"*

Dependencies

  • yfinance

Timezone

All timestamps and time-based calculations must use the America/New_York timezone. All JSON output must include generated_at (NY time string) and data_delay fields.

How to use it

Copy the folder

Take staskh/insider-trading from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.