Stock Monitor

Use when building a manual stock watchlist, defining alert thresholds, or documenting a repeatable monitoring routine with public market data.

Security Scan

The skill is an instruction-only guide for building a manual stock watchlist and contains no installs, credentials, or commands that exceed its stated purpose.

Purpose & Capability

The name and description match the requirements and content: it's a manual monitoring/workflow guide for public market data and does not request unrelated resources or capabilities.

Instruction Scope

SKILL.md contains only procedural guidance (how to build a watchlist, define thresholds, cadence, and notes). It does not instruct the agent to read local files, access credentials, run shell commands, or transmit data to external endpoints.

Install Mechanism

No install spec or code files are present. Being instruction-only means nothing is written to disk or downloaded during install.

Credentials

The skill requests no environment variables, credentials, or config paths — proportional to an instruction-only monitoring workflow.

Persistence & Privilege

always is false and there is no request to persist configuration or modify other skills. Autonomous invocation is allowed by default on the platform but this skill's instructions do not escalate privileges or demand persistent presence.

Assessment

This is a low-risk, instruction-only skill useful as a template for manual monitoring. Before installing, be aware: the skill itself does not fetch live data or send alerts — if you later add integrations (APIs, bots, or automation) those will require credentials and raise additional risks. Do not provide any API keys or trading credentials to the skill unless you trust implemented code; review any future code or install specs for network calls, downloads, or credential usage. If you want automated alerts, plan to supply only the minimal, purpose-specific credentials to a vetted integration rather than to this skill as-is.

This skill helps design a repeatable monitoring workflow. It does not ship a background daemon, alert bot, or proprietary market-data service.

When to use

• You want a watchlist for holdings or names you are considering.
• You need threshold rules for price moves, volume spikes, or gap opens.
• You want a simple routine for checking public market data and recording follow-up actions.

Suggested workflow

1. Build a watchlist. Record ticker, market, thesis, baseline price, and the event you care about.
2. Define alert thresholds. Examples: percentage move, break above resistance, break below support, or unusual volume.
3. Decide the review cadence. Intraday, daily close, weekly review, or earnings-only monitoring.
4. Record observations. Note what changed, whether the thesis still holds, and what action should happen next.

Example watchlist template

{
  "watchlist": [
    {
      "ticker": "AAPL",
      "market": "NASDAQ",
      "baseline_price": 190.0,
      "alert_rules": [
        "price moves more than 5% from baseline",
        "close breaks above previous 20-day high"
      ],
      "review_notes": "Watch the next earnings call and hardware guidance."
    }
  ]
}

Good outputs

• A clean watchlist
• Explicit threshold rules
• Review cadence
• Notes for what to do when a rule triggers

Guardrails

• Treat all public quotes as delayed or vendor-dependent unless verified.
• Do not claim that automatic alerts were sent unless an actual notification system exists.
• Keep records of thresholds and rationale so later reviews are comparable.
• This skill is for monitoring and planning, not for trade execution.