CtrlK
BlogDocsLog inGet started
Tessl Logo

kanchi-dividend-review-monitor

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.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/kanchi-dividend-review-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A well-organized, actionable skill body that defers detail to real reference files and avoids re-explaining known concepts. The main gap is the absence of an explicit output-validation feedback loop in a batch workflow, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint after step 2, e.g. 'Verify review_queue_*.json parses and contains all input tickers; if any are missing, re-run with --strict before generating tickets.'

Include a short copy-paste example of the review-ticket output format inline so Claude can generate tickets without opening the template file.

Tighten the SEC Filing Guardrail paragraph by moving the long enumeration of T4 keywords and URL paths into references/trigger-matrix.md or a dedicated SEC-fetching reference.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no preamble explaining dividends, 8-K filings, or basic concepts); the SEC-fetcher paragraph and flat-dividend caveat are non-obvious domain specifics that earn their tokens, with only minor padding that could be trimmed.

4 / 5

Actionability

Provides an executable bash command with concrete arguments pointing to a real script, plus specific per-ticker field lists and real reference files; not a 5 because ticket generation relies on a template file rather than an inline copy-paste example.

4 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced, but this is a batch operation (per-ticker queueing) and lacks an explicit validate/verify-then-retry feedback loop for the generated queue; per the batch-operations cap, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Clear overview with one-level-deep, well-signaled references (input-schema.md, trigger-matrix.md, review-ticket-template.md, build_review_queue.py, tests) — all of which are real bundle files — and content is appropriately split for easy navigation.

5 / 5

Total

16

/

20

Passed

Description

87%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, third-person description that concretely states capabilities and provides explicit multilingual trigger guidance. Minor room to expand trigger-term synonyms and surface T1-T5 scope within the description itself.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions ('Monitor dividend portfolios', 'forced-review triggers (T1-T5)', 'convert anomalies into OK/WARN/REVIEW states', 'without auto-selling'); not a 5 because the T1-T5 detail is deferred to the body rather than enumerated in the description.

4 / 5

Completeness

Explicitly answers both 'what' (monitor portfolios, convert anomalies to OK/WARN/REVIEW states) and 'when' via a concrete 'Use when users ask for ...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage across languages ('減配検知', '8-Kガバナンス監視', '配当安全性モニタリング', 'REVIEWキュー自動化', 'periodic dividend risk checks') with natural phrases users would say; not a 5 because a few common synonyms (e.g., 'dividend cut', ' payout cut') are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche ('Kanchi-style forced-review triggers', 'T1-T5', 'OK/WARN/REVIEW') with distinct, specialized triggers and minimal overlap risk with generic finance skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
tradermonty/claude-trading-skills
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.