Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
tradermonty avatar

Kanchi Dividend Review Monitor

  • 723 installs
  • 2.6k repo stars
  • Updated August 4, 2026
  • tradermonty/claude-trading-skills

kanchi-dividend-review-monitor is an agent skill that scans dividend portfolios for Kanchi-style T1-T5 risk triggers and routes anomalies into OK, WARN, or REVIEW states without auto-selling for developers monitoring div

About

kanchi-dividend-review-monitor is a claude-trading-skills module for dividend holdings surveillance using Kanchi-style forced-review triggers labeled T1 through T5. It treats automation as anomaly detection only—flagging dividend cuts, governance signals, and 8-K keyword hits—then classifies positions into OK, WARN, or REVIEW without executing sells. The skill supports daily, weekly, or quarterly cadences and responds to Japanese and English prompts around 減配検知, 8-K governance monitoring, and REVIEW queue automation. Developers reach for it when maintaining dividend income portfolios that need systematic escalation to human review rather than blind algo trading. It outputs structured review queues, not brokerage orders.

  • Implements Kanchi-style T1-T5 forced-review triggers
  • Converts anomalies into deterministic OK/WARN/REVIEW states
  • Performs 8-K/governance keyword scans tied to portfolio tickers
  • Never auto-sells; always produces evidence for human confirmation
  • Supports daily, weekly, and quarterly anomaly detection runs

Kanchi Dividend Review Monitor by the numbers

  • 723 all-time installs (skills.sh)
  • +33 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #187 of 1,106 Finance & Trading skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tradermonty/claude-trading-skills --skill kanchi-dividend-review-monitor

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs723
repo stars2.6k
Last updatedAugust 4, 2026
Repositorytradermonty/claude-trading-skills

How do you monitor dividend cut risk signals?

Automatically scan dividend portfolios for risk signals and route anomalies into a forced human review queue.

Who is it for?

Developers or quants operating dividend income portfolios who need scheduled anomaly detection with mandatory human review gates.

Skip if: Traders seeking automated sell execution, intraday scalping signals, or non-dividend equity strategies.

When should I use this skill?

User asks for dividend risk monitoring, T1-T5 review triggers, 減配検知, 8-K governance scans, or REVIEW queue automation.

What you get

Portfolio positions classified as OK, WARN, or REVIEW with T1-T5 trigger annotations and a forced human review queue.

  • OK/WARN/REVIEW classification report
  • Forced human REVIEW queue entries

By the numbers

  • Uses 5 Kanchi-style forced-review risk triggers labeled T1 through T5
  • Classifies portfolio state into 3 outcomes: OK, WARN, and REVIEW

Files

SKILL.mdMarkdownGitHub ↗

Kanchi Dividend Review Monitor

Overview

Detect abnormal dividend-risk signals and route them into a human review queue. Treat automation as anomaly detection, not automated trade execution.

When to Use

Use this skill when the user needs:

  • Daily/weekly/quarterly anomaly detection for dividend holdings.
  • Forced review queueing for T1-T5 risk triggers.
  • 8-K/governance keyword scans tied to portfolio tickers.
  • Deterministic OK/WARN/REVIEW output before manual decision making.

Prerequisites

Provide normalized input JSON that follows:

  • references/input-schema.md

If upstream data is unavailable, provide at least:

  • ticker
  • instrument_type
  • dividend.latest_regular
  • dividend.prior_regular

Non-Negotiable Rule

Never auto-sell based only on machine triggers. Always create WARN or REVIEW evidence for human confirmation first.

State Machine

  • OK: no action.
  • WARN: add to next check cycle and pause optional adds.
  • REVIEW: immediate human review ticket + pause adds.

Use references/trigger-matrix.md for trigger thresholds and actions.

Flat-dividend cadence caveat

When T6 is driven only by freeze_flag / latest regular dividend equal to prior regular dividend, treat it as a WARN for cadence confirmation, not as proof of dividend deterioration. Many quarterly dividend payers repeat the same dividend for several quarters between annual raise cycles. In reports, phrase this as “confirm next dividend-growth cadence / pause optional adds until checked” and avoid implying a cut or broken thesis unless T1/T2/T3/T4/T5 evidence also supports escalation.

Monitoring Cadence

  • Daily:
  • T1 dividend cut/suspension.
  • T4 SEC filing keyword scan (8-K oriented).
  • Weekly:
  • T3 proxy credit stress checks.
  • Quarterly:
  • T2 coverage deterioration and T5 structural decline scoring.

Workflow

1) Normalize input dataset

Collect per ticker fields in one JSON document:

  • Dividend points (latest regular, prior regular, missing/zero flag).
  • Coverage fields (FCF or FFO or NII, dividends paid, ratio history).
  • Balance-sheet trend fields (net debt, interest coverage, buybacks/dividends).
  • Filing text snippets (especially recent 8-K or equivalent alert text).
  • Operations trend fields (revenue CAGR, margin trend, guidance trend).

Use references/input-schema.md for field definitions and sample payload.

2) Run the rule engine

Run:

python3 skills/kanchi-dividend-review-monitor/scripts/build_review_queue.py \
  --input /path/to/monitor_input.json \
  --output-dir reports/

The script maps each ticker to OK/WARN/REVIEW based on T1-T5. Output files are saved to the specified directory with dated filenames (e.g., review_queue_20260227.json and .md).

3) Prioritize and deduplicate

If multiple triggers fire:

  • Keep all findings for audit trail.
  • Escalate final state to highest severity only.
  • Store trigger reasons as single-line evidence.

4) Generate human review tickets

For each REVIEW ticker, include:

  • Trigger IDs and evidence.
  • Suspected failure mode.
  • Required manual checks for next decision.

Use references/review-ticket-template.md output format.

SEC Filing Guardrail

When implementing live SEC fetchers:

  • Include a compliant User-Agent string (name + email).
  • Use caching and throttling.
  • Respect SEC fair-access guidance.

Output Contract

Always return: 1. Queue JSON with summary counts and ticker-level findings. 2. Markdown dashboard for quick triage. 3. List of immediate REVIEW tickets.

Multi-Skill Handoff

  • Consume ticker universe and baseline assumptions from kanchi-dividend-sop.
  • Feed REVIEW results back to kanchi-dividend-sop for re-underwriting and position-size review.
  • Share account-type context with kanchi-dividend-us-tax-accounting when risk events imply account relocation decisions.

Resources

  • scripts/build_review_queue.py: local rule engine for T1-T5.
  • scripts/tests/test_build_review_queue.py: unit tests for T1-T5 and report rendering.
  • references/trigger-matrix.md: trigger definitions, cadence, and actions.
  • references/input-schema.md: normalized input schema and sample JSON.
  • references/review-ticket-template.md: standardized manual-review ticket layout.

Related skills

FAQ

Does kanchi-dividend-review-monitor execute trades automatically?

kanchi-dividend-review-monitor performs anomaly detection only. It assigns OK, WARN, or REVIEW states and enqueues human review—it does not auto-sell positions when dividend risk triggers fire.

What are T1-T5 triggers in kanchi-dividend-review-monitor?

kanchi-dividend-review-monitor uses five Kanchi-style forced-review triggers (T1-T5) to flag dividend cuts, governance issues, and related anomalies that require escalation beyond a simple OK status.

Finance & Tradingfinancepayments

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.