mcpbeat Sign in

Kanchi Dividend Review Monitor Agent Skill

Monitor dividend portfolios with Kanchi-style forced-review triggers (T1-T5) and convert anomalies into OK/WARN/REVIEW states without auto-selling. Use when users ask for 減配検知, 8-Kガバナンス監視, 配当安全性モニタリング, REVIEWキュー自動化, or periodic dividend risk checks.

9k tokens
context cost
the whole folder, loaded on every use
8
files
ships runnable scripts
1
copies elsewhere
how many repositories repackaged it
118
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/BaggaT236/AI-Trading-Skills --skill kanchi-dividend-review-monitor

What comes with it

30 867 bytes besides the instruction
agents/openai.yaml
references/input-schema.md
references/review-ticket-template.md
references/trigger-matrix.md
scripts/build_review_queue.py
scripts/tests/conftest.py
scripts/tests/test_build_review_queue.py

The instruction itself

17 sections, as written by the author

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.
  • In scheduled portfolio reviews where upstream filing snippets are empty, use SEC company_tickers.json plus https://data.sec.gov/submissions/CIK##########.json to enumerate recent 8-K / 8-K/A filings for each holding, then scan primary filing documents for the T4 keyword family (Item 4.02, non-reliance, restatement, material weakness, SEC investigation, subpoena, going concern, auditor resignation, internal control). Record the scan window, recent 8-K count, and whether hits were found. Treat "no keyword hits" as a narrow T4 scan result, not a full governance clearance.

Output Contract

Always return:

  • Queue JSON with summary counts and ticker-level findings.
  • Markdown dashboard for quick triage.
  • 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.

Other skills for the same job

different authors, same section of the catalogue
Solidity Security
by ComeOnOliver
×2

Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.

6k tokens
Solidity Security
by ComeOnOliver
×2

Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.

8k tokens
Cross Border Ecommerce
by nexscope-ai
×1

Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.

9k tokens
Cosmos Vulnerability Scanner
by trailofbits

Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

39k tokens
Configure Auth
by dotnet

> Add authentication and authorization to a Blazor Web App, accounting for the app's render mode. USE WHEN the user needs [Authorize] on pages, AuthorizeView, role or policy-based access, login/logout Identity pages, or AuthenticationStateProvider. Also USE WHEN auth state is null after WebAssembly loads, SignInManager throws in an interactive component, <NotAuthorized> content never renders in static SSR, or HttpContext.User is null in an interactive component. DO NOT USE for general component authoring (see author-component), for prerendering concerns unrelated to auth (see support-prerendering), or for managing non-auth cascading state (see coordinate-components).

2k tokens
Hunt Websocket
by elementalsouls

Hunt WebSocket vulnerabilities — Cross-Site WebSocket Hijacking (CSWSH), missing/weak Origin validation on the WS handshake, no per-message authentication, message tampering, socket.io namespace/room authorization bypass, and handshake-layer Upgrade smuggling. Use when target has WebSocket endpoints (ws:// or wss://), socket.io / SignalR / Phoenix Channels, real-time features, chat, live dashboards, notifications, or trading platforms.

4k tokens
Web3 Audit
by elementalsouls

Smart contract security audit — 10 DeFi bug classes (accounting desync, access control, incomplete path, off-by-one, oracle, ERC4626, reentrancy, flash loan, signature replay, proxy), pre-dive kill signals (TVL < $500K etc), Foundry PoC template, grep patterns for each class, and real Immunefi paid examples. Use for any Solidity/Rust contract audit or when deciding whether a DeFi target is worth hunting.

6k tokens
Ctf Pwn
by ljagiello

Provides binary exploitation techniques for CTF challenges. Use when you already have a vulnerable native target or service and need to turn memory corruption or low-level primitives into code execution or privilege escalation, such as buffer overflows, format strings, heap bugs, ROP, ret2libc, shellcode, kernel exploitation, seccomp bypass, sandbox escape, or Windows/Linux exploit chains. Do not use it when the main blocker is understanding what the binary does; use reverse engineering first. Do not use it for pure web bugs, disk or packet forensics, or standalone crypto/math challenges.

114k tokens

How to use it

Copy the folder

Take baggat236/kanchi-dividend-review-monitor 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.