domain-fintech

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

Quality

46%

Does it follow best practices?

Impact

—

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

54%

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

The description is essentially a keyword dump with no explanation of what the skill actually does. While the trigger terms are comprehensive and well-chosen, the complete absence of concrete capabilities makes it impossible for Claude to understand what this skill provides versus other finance-related skills. The description needs to articulate specific actions and outputs.

Suggestions

Add concrete capability descriptions such as 'Provides patterns for decimal precision handling, currency conversion, ledger design, and transaction processing in financial applications'.

Differentiate from other potential finance-related skills by specifying the unique value, e.g., 'Guides implementation of financial-grade arithmetic, rounding rules, and double-entry bookkeeping patterns'.

Restructure to lead with 'what it does' before the 'when to use' clause, e.g., 'Implements financial-grade decimal handling, currency operations, and ledger patterns for fintech applications. Use when building fintech apps or when the user mentions...'

Dimension	Reasoning	Score
Specificity	The description says 'Use when building fintech apps' but does not describe any concrete actions or capabilities. There are no specific actions like 'handles decimal precision', 'converts currencies', or 'manages ledger entries' — just a domain label and a keyword list.	1 / 3
Completeness	It has a 'when' clause ('Use when building fintech apps') but the 'what' is essentially absent — there is no description of what the skill actually does or what capabilities it provides. The rubric caps completeness at 2 when trigger guidance is present but the other half is weak.	2 / 3
Trigger Term Quality	The description includes a comprehensive list of natural keywords users would say: 'fintech', 'trading', 'decimal', 'currency', 'financial', 'money', 'transaction', 'ledger', 'payment', 'exchange rate', 'precision', 'rounding', 'accounting', plus Chinese equivalents. These cover many natural variations.	3 / 3
Distinctiveness Conflict Risk	The fintech domain is somewhat specific, and the keyword list narrows the scope, but without concrete actions described, it could overlap with any finance-related skill (e.g., a currency converter skill, an accounting skill, a payment processing skill). The broad scope of 'fintech apps' creates moderate conflict risk.	2 / 3
	Total	8 / 12 Passed

Implementation

37%

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

The skill provides a reasonable reference card for fintech domain constraints in Rust, with good use of tables for quick scanning and one concrete code example. However, it reads more like a conceptual overview than an actionable skill—most patterns are named but not demonstrated, and there is no workflow guidance for actually building fintech components. The content would benefit significantly from additional executable examples and a clear step-by-step process.

Suggestions

Add executable code examples for the key patterns beyond just Currency type—especially transaction handling with event sourcing, double-entry ledger validation, and audit logging with tracing

Include a workflow section with sequenced steps for implementing a financial transaction, including validation checkpoints (e.g., verify debit/credit balance, validate currency consistency)

Remove redundant 'Trace Down' and 'Trace to Layer 1' sections or consolidate them into a single cross-reference table to improve conciseness

Add a concrete example showing checked arithmetic for Amount operations to demonstrate the 'silent overflow' fix mentioned in Common Mistakes

Dimension	Reasoning	Score
Conciseness	The content is reasonably structured with tables for quick scanning, but includes some redundancy—the 'Trace Down' and 'Trace to Layer 1' sections repeat information already conveyed in the constraints table and common mistakes table. The RULE/WHY/RUST blocks are somewhat verbose for what could be single-line entries.	2 / 3
Actionability	The Currency type code example is concrete and executable, which is good. However, much of the skill is descriptive tables and abstract pattern references (e.g., 'Event sourcing', 'RAII for transaction scope') without executable implementations. Key patterns like transaction handling, audit logging, and double-entry ledger are mentioned but not demonstrated with code.	2 / 3
Workflow Clarity	There is no clear workflow or sequenced process for building a fintech application. The content is organized as reference tables and constraints but lacks any step-by-step guidance, validation checkpoints, or feedback loops for operations like implementing transactions or ensuring double-entry balance correctness.	1 / 3
Progressive Disclosure	The 'Related Skills' table provides clear references to other skills (m09-domain, m01-ownership, etc.), which is good navigation. However, with no bundle files provided, these references are unverifiable. The content itself is somewhat monolithic with multiple tables that could benefit from being split into focused sub-documents for patterns like event sourcing or ledger implementation.	2 / 3
	Total	7 / 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: fa60f79

Reviewed: 6 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.