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.
npx skills add https://github.com/BaggaT236/AI-Trading-Skills --skill kanchi-dividend-review-monitor
Detect abnormal dividend-risk signals and route them into a human review queue.
Treat automation as anomaly detection, not automated trade execution.
Use this skill when the user needs:
OK/WARN/REVIEW output before manual decision making.Provide normalized input JSON that follows:
references/input-schema.mdIf upstream data is unavailable, provide at least:
tickerinstrument_typedividend.latest_regulardividend.prior_regularNever auto-sell based only on machine triggers.
Always create WARN or REVIEW evidence for human confirmation first.
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.
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.
Collect per ticker fields in one JSON document:
Use references/input-schema.md for field definitions
and sample payload.
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).
If multiple triggers fire:
For each REVIEW ticker, include:
Use references/review-ticket-template.md output format.
When implementing live SEC fetchers:
User-Agent string (name + email).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.Always return:
REVIEW tickets.kanchi-dividend-sop.REVIEW results back to kanchi-dividend-sop for re-underwriting and position-size review.kanchi-dividend-us-tax-accounting when risk events imply account relocation decisions.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.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.
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.
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.
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.
> 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).
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.
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.
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.
Take baggat236/kanchi-dividend-review-monitor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.