CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kanchi-dividend-us-tax-accounting

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured content with strong progressive disclosure — an overview body that defers detail to real, clearly signaled one-level-deep reference files — and a clearly sequenced workflow with an executable script. Weakest areas are mild redundancy, non-skill-relative script paths, and the absence of an output-verification step.

Suggestions

Consolidate duplicated material: the script path appears in both Prerequisites and Output, and the Resources section restates the reference files already cited inline in the workflow steps — a single Resources section (or inline citations only) would trim tokens.

Use skill-relative script paths (scripts/build_tax_planning_sheet.py) instead of repo-root paths (skills/kanchi-dividend-us-tax-accounting/scripts/...) so the bash command is copy-paste runnable from the skill directory.

Add an explicit verification step after running the script (e.g. confirm the generated sheet's row count matches the holdings input and that no rows carry ASSUMPTION-REQUIRED without an open-risk entry) to create a validation feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what dividends, REITs, or tax forms are. Minor trims are possible: the "When to Use" section repeats the frontmatter description, the script path appears in both Prerequisites and Output, and the Resources section restates references already cited inline in the workflow.

4 / 5

Actionability

Concrete, executable guidance is present: a complete bash invocation with --input/--output-dir arguments and a JSON input contract in references/input-schema.md. It is not a 5 because the command uses repo-root paths ("skills/kanchi-dividend-us-tax-accounting/scripts/...") rather than skill-relative paths, and steps 3 and 5 delegate detail to templates without inline examples of the common case.

4 / 5

Workflow Clarity

A clearly sequenced 5-step workflow (classify, validate holding periods, map to reporting, account location, memo) with one explicit checkpoint ("If data is incomplete, mark status as `ASSUMPTION-REQUIRED`") and a defined output checklist. It falls short of 5 because there is no verification step for the generated planning sheet and no error-recovery loop around the script run.

4 / 5

Progressive Disclosure

The body is a concise overview that points to one-level-deep, well-signaled references at the exact point of use ("Use references/qualified-dividend-checklist.md for holding-period and classification checks", "Use references/account-location-matrix.md", "Use references/annual-tax-memo-template.md"), all of which exist as real files, plus a Resources index. Content is appropriately split with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' clause, concrete domain-specific trigger terms, and a clear niche. The main improvement opportunity is adding natural conversational variants and synonyms to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "1099-DIV interpretation", "holding-period checks", "REIT/BDC distribution treatment", "taxable-vs-IRA account placement decisions" — grounded in a specific domain ("US dividend tax and account-location workflow"). It falls short of a 5 because the lead action "Provide ... workflow" is umbrella phrasing and the items read more as topic coverage than fully concrete actions.

4 / 5

Completeness

It explicitly answers both questions: what ("Provide US dividend tax and account-location workflow for Kanchi-style income portfolios") and when ("Use when users ask about qualified vs ordinary dividends, 1099-DIV interpretation, ..."), with concrete trigger phrases. This matches the anchor 5 pattern of the good overall examples, including an explicit 'Use when' clause.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are present: "qualified vs ordinary dividends", "1099-DIV", "REIT/BDC distribution treatment", "holding-period checks", "taxable-vs-IRA account placement". It is not a 5 because common variations are missing, e.g. "dividend tax planning", "Form 1099-DIV", or conversational forms like "should I hold this REIT in my IRA".

4 / 5

Distinctiveness Conflict Risk

The "Kanchi-style income portfolios" niche and form/instrument-specific triggers (1099-DIV, REIT/BDC, holding-period) make it mostly distinct with minimal conflict against generic skills. It is not a 5 because sibling skills in the same family (e.g. kanchi-dividend-sop, kanchi-dividend-review-monitor) could overlap for general REIT/dividend-review questions, and the description does not carve out boundaries from them.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/kanchi-dividend-us-tax-accounting/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.