CtrlK
BlogDocsLog inGet started
Tessl Logo

openfinance-bank-adapter

Technical guide for adding a new Open Finance bank integration adapter (e.g., Itaú, Banco Inter, Mercado Pago) in FinanceHub (.NET 10), implementing IBankConnector, OAuth2/mTLS authentication, rate limiting, and publishing TransactionIngested events via MassTransit Outbox.

64

Quality

75%

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 ./.agents/skills/openfinance-bank-adapter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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-structured, actionable implementation guide with executable code and a clear step sequence, held back only by a couple of undefined helper methods and the absence of explicit feedback loops in verification.

Suggestions

Show the FetchTokenAsync implementation and the ToDomain()/response DTO mapping so the connector and auth handler are fully copy-paste ready.

Turn the verification checklist into an explicit feedback loop (e.g., 'If dotnet test fails, fix mapping/resilience issues and re-run until green').

Consider moving the full IBankConnector contract and DTO definitions into a references/ file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no basic-concept padding), but the opening line restates the description and a few transitional sentences could be trimmed.

4 / 5

Actionability

Provides concrete, mostly copy-paste C# with justified <BankName> placeholders, but FetchTokenAsync and the ToDomain() extension are referenced without being shown, leaving minor gaps.

4 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced and followed by a verification checklist (dotnet build/test), but there is no explicit fix→re-validate feedback loop for failed checks.

4 / 5

Progressive Disclosure

Content is well-sectioned (Overview, Interface, Directory, Steps, Verification) with no nested references, though at ~230 lines all material is inline with no external file split.

4 / 5

Total

16

/

20

Passed

Description

75%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 highly specific, well-scoped description that clearly conveys what the skill does and is distinct from other skills, but it lacks an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause such as 'Use when adding or onboarding a new Open Finance bank adapter in FinanceHub, or when the user mentions Itaú, Banco Inter, or Mercado Pago integration.'

Soften internal jargon (e.g., 'MassTransit Outbox') in favor of a natural phrasing like 'transactional outbox event publishing' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain plus multiple concrete actions — 'implementing IBankConnector, OAuth2/mTLS authentication, rate limiting, and publishing TransactionIngested events via MassTransit Outbox' — giving comprehensive coverage.

5 / 5

Completeness

The 'what' is detailed and clear, but there is no explicit 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Bank names (Itaú, Banco Inter, Mercado Pago) and 'Open Finance bank integration adapter' are natural terms a user would say, but they sit alongside heavier jargon (MassTransit Outbox, mTLS), leaving a few common phrasings uncovered.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Open Finance bank adapters in FinanceHub .NET 10) with distinct triggers (named banks, IBankConnector, MassTransit Outbox), giving minimal conflict risk with other skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JoseMD12/finance-hub
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.