skills/kanchi-dividend-us-tax-accounting/SKILL.md
Provide US dividend tax and account-location workflow for Kanchi-style income portfolios. Use when users ask about qualified vs ordinary dividends, 1099-DIV interpretation, REIT/BDC distribution treatment, holding-period checks, or taxable-vs-IRA account placement decisions for dividend assets.
npx skillsauth add MileniumTick/skills kanchi-dividend-us-tax-accountingInstall 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.
Apply a practical US-tax workflow for dividend investors while keeping decisions auditable. Focus on account placement and classification, not legal/tax advice replacement.
Use this skill when the user needs:
Prepare holding-level inputs:
tickerinstrument_typeaccount_typehold_days_in_window (if available){
"holdings": [
{
"ticker": "JNJ",
"instrument_type": "stock",
"account_type": "taxable",
"security_type": "common",
"hold_days_in_window": 75
},
{
"ticker": "O",
"instrument_type": "reit",
"account_type": "ira",
"hold_days_in_window": 100
}
]
}
For deterministic output artifacts, provide JSON input and run:
python3 skills/kanchi-dividend-us-tax-accounting/scripts/build_tax_planning_sheet.py \
--input /path/to/tax_input.json \
--output-dir reports/
Always state this clearly: tax outcomes depend on individual facts and jurisdiction. Treat this skill as planning support, then escalate final filing decisions to a tax professional.
For each holding, classify expected cash flow into:
Use references/qualified-dividend-checklist.md
for holding-period and classification checks.
For potential qualified treatment:
If data is incomplete, mark status as ASSUMPTION-REQUIRED.
Map planning assumptions to expected tax-form buckets:
Use form terminology consistently so year-end reconciliation is straightforward.
Use references/account-location-matrix.md to place
assets by tax profile:
When constraints conflict (liquidity, strategy, concentration), explain the tradeoff explicitly.
Use references/annual-tax-memo-template.md and include:
Always output:
skills/kanchi-dividend-us-tax-accounting/scripts/build_tax_planning_sheet.py.Use this minimum rhythm:
kanchi-dividend-review-monitor.kanchi-dividend-sop.WARN/REVIEW) from kanchi-dividend-review-monitor.kanchi-dividend-sop before new entries.skills/kanchi-dividend-us-tax-accounting/scripts/build_tax_planning_sheet.py: tax planning sheet generator.skills/kanchi-dividend-us-tax-accounting/scripts/tests/test_build_tax_planning_sheet.py: tests for tax planning outputs.references/qualified-dividend-checklist.md: classification and holding-period checks.references/account-location-matrix.md: placement matrix by account type and instrument.references/annual-tax-memo-template.md: reusable memo structure.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.