domain-fintech

Use when building fintech apps. Keywords: fintech, trading, decimal, currency, financial, money, transaction, ledger, payment, exchange rate, precision, rounding, accounting, 金融, 交易系统, 货币, 支付

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/domain-fintech/SKILL.md

Quality

Discovery

37%

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

This description relies heavily on keyword stuffing rather than explaining what the skill actually does. While the trigger terms are comprehensive and well-chosen, the complete absence of concrete capabilities (what actions does this skill enable?) makes it nearly useless for Claude to understand when to apply it versus other coding-related skills.

Suggestions

Add specific concrete actions the skill enables, e.g., 'Handles decimal precision for currency calculations, implements transaction ledgers, manages exchange rate conversions, ensures proper rounding for financial operations.'

Expand the 'Use when' clause beyond just 'building fintech apps' to include specific scenarios like 'Use when implementing payment processing, currency arithmetic, or financial calculations requiring precision.'

Remove redundant keywords and integrate the most important ones naturally into capability descriptions rather than listing them separately.

Dimension	Reasoning	Score
Specificity	The description only says 'building fintech apps' without listing any concrete actions. It lacks specific capabilities like 'handle decimal precision', 'process transactions', or 'calculate exchange rates'.	1 / 3
Completeness	The 'what' is extremely weak (just 'building fintech apps') and while 'Use when' is present, it doesn't explain what the skill actually does. The keywords list doesn't substitute for describing capabilities.	1 / 3
Trigger Term Quality	Excellent coverage of natural keywords including 'fintech', 'trading', 'currency', 'money', 'payment', 'transaction', 'ledger', plus Chinese equivalents. These are terms users would naturally use when working in this domain.	3 / 3
Distinctiveness Conflict Risk	The fintech/financial domain is somewhat specific, and the keyword list helps narrow scope, but 'building fintech apps' is broad enough to potentially conflict with database, API, or general coding skills.	2 / 3
	Total	7 / 12 Passed

Implementation

72%

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

This is a well-structured domain constraints document that efficiently communicates fintech-specific rules and their Rust implications. Its strength lies in concise tabular presentation and clear cross-references to related skills. However, it would benefit from more executable code examples for patterns beyond the basic Currency type, and explicit validation workflows for financial transactions.

Suggestions

Add executable code examples for event sourcing pattern and audit logging, not just the Currency newtype

Include a validation workflow showing how to verify transaction integrity (e.g., double-entry balance checks) with explicit checkpoints

Add a concrete example of checked arithmetic usage to match the 'Silent overflow' fix mentioned in Common Mistakes

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables and code blocks to convey information densely. No unnecessary explanations of concepts Claude would already know; every section adds domain-specific value.	3 / 3
Actionability	Provides one concrete, executable code example for the Currency type, but other patterns (event sourcing, audit logging, ledger) are described abstractly without implementation examples. The 'Trace Down' section uses pseudocode-like notation rather than executable guidance.	2 / 3
Workflow Clarity	The skill presents constraints and patterns clearly but lacks explicit multi-step workflows with validation checkpoints. For financial operations involving transactions and ledgers, there are no feedback loops or verification steps shown.	2 / 3
Progressive Disclosure	Well-organized with clear sections, tables for quick reference, and explicit 'Related Skills' section pointing to other resources. The 'Trace Down' and 'Trace to Layer 1' sections provide clear navigation to related patterns without deep nesting.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: actionbook/rust-skills
Commit: 1f4becd

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.