skills/kanchi-dividend-sop/SKILL.md
Convert Kanchi-style dividend investing into a repeatable US-stock operating procedure. Use when users ask for かんち式配当投資, dividend screening, dividend growth quality checks, PERxPBR adaptation for US sectors, pullback limit-order planning, or one-page stock memo creation. Covers screening, deep dive, entry planning, and post-purchase monitoring cadence.
npx skillsauth add MileniumTick/skills kanchi-dividend-sopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement Kanchi's 5-step method as a deterministic workflow for US dividend investing. Prioritize safety and repeatability over aggressive yield chasing.
Use this skill when the user needs:
The entry signal script requires FMP API access:
export FMP_API_KEY=your_api_key_here
Prepare one of the following inputs before running the workflow:
skills/value-dividend-screener/scripts/screen_dividend_stocks.py.skills/dividend-growth-pullback-screener/scripts/screen_dividend_growth.py.When using --input, provide JSON in one of these formats:
{
"profile": "balanced",
"candidates": [
{"ticker": "JNJ", "bucket": "core"},
{"ticker": "O", "bucket": "satellite"}
]
}
Or simplified:
{
"tickers": ["JNJ", "PG", "KO"]
}
For deterministic artifact generation, provide tickers to:
python3 skills/kanchi-dividend-sop/scripts/build_sop_plan.py \
--tickers "JNJ,PG,KO" \
--output-dir reports/
For Step 5 entry timing artifacts:
python3 skills/kanchi-dividend-sop/scripts/build_entry_signals.py \
--tickers "JNJ,PG,KO" \
--alpha-pp 0.5 \
--output-dir reports/
Collect and lock the parameters first:
Load references/default-thresholds.md and apply baseline
settings unless the user overrides.
Start with a quality-biased universe:
Use explicit source priority for ticker collection:
skills/value-dividend-screener/scripts/screen_dividend_stocks.py output (FMP/FINVIZ).skills/dividend-growth-pullback-screener/scripts/screen_dividend_growth_rsi.py output.Return a ticker list grouped by bucket before moving forward.
Primary rule:
forward_dividend_yield >= 3.5%Trap controls:
>= 8%) as deep-dive-required.Output:
PASS or FAIL per ticker.deep-dive-required flag for potential yield traps.Require:
Add safety checks:
When trend is mixed but not broken, classify as HOLD-FOR-REVIEW instead of hard reject.
Use references/valuation-and-one-off-checks.md and apply
sector-specific valuation logic:
PER x PBR can remain primary.P/FFO or P/AFFO instead of plain P/E.P/E, P/FCF, and historical range.Always report which valuation method was used for each ticker.
Reject or downgrade names where recent profits rely on one-time effects:
Record one-line evidence for each FAIL to keep auditability.
Set entry triggers mechanically:
+0.5pp).P/E, P/FFO, or P/FCF).Execution pattern:
40% -> 30% -> 30%.Always produce three artifacts:
PASS, HOLD-FOR-REVIEW, FAIL with evidence).references/stock-note-template.md).Return and/or generate:
references/stock-note-template.md.skills/kanchi-dividend-sop/scripts/build_sop_plan.py in reports/.skills/kanchi-dividend-sop/scripts/build_entry_signals.py in reports/.Use this minimum rhythm:
Run this skill first, then hand off outputs:
kanchi-dividend-review-monitor for daily/weekly/quarterly anomaly detection.kanchi-dividend-us-tax-accounting for account-location and tax classification planning.skills/kanchi-dividend-sop/scripts/build_sop_plan.py: deterministic SOP plan generator.skills/kanchi-dividend-sop/scripts/tests/test_build_sop_plan.py: tests for plan generation.skills/kanchi-dividend-sop/scripts/build_entry_signals.py: Step 5 target-buy calculator (5y avg yield + alpha).skills/kanchi-dividend-sop/scripts/tests/test_build_entry_signals.py: tests for signal calculations.references/default-thresholds.md: baseline thresholds and profile tuning.references/valuation-and-one-off-checks.md: sector valuation map and one-off checklist.references/stock-note-template.md: one-page memo template for each candidate.development
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
development
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
development
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
tools
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.