CtrlK
BlogDocsLog inGet started
Tessl Logo

domain-fintech

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

58

Quality

73%

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/domain-fintech/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-structured, token-efficient domain-constraints reference with concrete Rust guidance and a complete code pattern. Its main weakness is that it is reference material without a procedural workflow, so workflow clarity is only adequate rather than strong.

Suggestions

De-duplicate the 'Critical Constraints' RULE/WHY/RUST blocks against the top 'Domain Constraints' table to tighten conciseness further.

Define the Currency and CurrencyMismatch types referenced in the Amount code pattern so the example is fully copy-paste executable.

If the skill is meant to guide implementation, add an ordered apply-pattern sequence (choose crate → model value objects → enforce immutability) with a validation/compile-check checkpoint to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is table-driven and terse (RULE/WHY/RUST blocks, compact crate and pattern tables) and assumes Claude's competence without explaining what decimals or Arc are, though the 'Critical Constraints' rules duplicate information already in the top 'Domain Constraints' table.

4 / 5

Actionability

Concrete, mostly-executable Rust guidance is given — 'Use rust_decimal::Decimal', 'Arc<T> for sharing', a full Amount code pattern, and a named-crate table — with minor gaps such as the undefined Currency and CurrencyMismatch types in the example.

4 / 5

Workflow Clarity

A conceptual sequence exists ('Trace Down ↓' from constraints to design patterns to implementation), but this is a reference document, not a procedural workflow, so there are no explicit checkpoints or validation steps; no destructive/batch cap applies since none are involved.

3 / 5

Progressive Disclosure

Content is well-organized into clear headed sections with no bundle files present, so it is appropriately self-contained; the 'Related Skills' table points one level out to sibling skills rather than to nested bundle references.

4 / 5

Total

15

/

20

Passed

Description

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

Strong, comprehensive trigger-term coverage makes this description highly discoverable, but it lacks a clear statement of what the skill actually does — it says when to use it but not what capabilities it provides. The domain niche is well-targeted with low conflict risk.

Suggestions

Add a concrete capability clause before the trigger, e.g. 'Provides financial-precision, audit, and consistency constraints with Rust design patterns (rust_decimal, Arc<T>, event sourcing).'

State the what explicitly so the description answers both 'what does this do' and 'when to use it', pushing completeness above 3.

Mention Rust/Decimal specifically in the description since the entire skill body is Rust-oriented — currently the language is invisible to a triggering user.

DimensionReasoningScore

Specificity

The description names the domain ('building fintech apps') but the only action is the generic verb 'building' — no concrete capabilities are listed, unlike the rubric's score-2 example 'Processes PDF files'.

2 / 5

Completeness

The 'when' is explicit ('Use when building fintech apps' plus keyword triggers), but the 'what' is weak — it never states that the skill supplies domain constraints and Rust design patterns, so it does not clearly answer both what and when.

3 / 5

Trigger Term Quality

Comprehensive keyword coverage including natural terms and synonyms ('fintech, trading, decimal, currency, financial, money, transaction, ledger, payment, exchange rate, precision, rounding, accounting') plus multilingual equivalents (金融, 交易系统, 货币, 支付).

5 / 5

Distinctiveness Conflict Risk

The fintech/financial niche with ledger, transaction, and accounting triggers is mostly distinct from generic skills, with only minor overlap risk against a hypothetical generic 'currency' or 'payment' skill.

4 / 5

Total

14

/

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
actionbook/rust-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.