CtrlK
BlogDocsLog inGet started
Tessl Logo

nordic-api-gateway

Nordic API Gateway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nordic API Gateway data.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/nordic-api-gateway/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with executable Membrane CLI commands and a strong state-driven connection workflow. The main gaps are minor redundancy, an unlabeled "Step 2" reference, and an intro paragraph that over-explains the platform.

Suggestions

Tighten or remove the opening platform-description paragraph and fix the duplicated "Payment Request" entry in the overview to reduce padding.

Label the post-connection steps explicitly (e.g. add a "### Step 2: Search for actions" header) so the "skip to Step 2" pointer resolves.

Add a brief validation note for `action run` on mutating/payment operations (verify output state before reporting success) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is dominated by lean, copy-pasteable commands and a flag table, but the opening "Nordic API Gateway is a platform that helps businesses..." intro and a duplicated "Payment Request" entry in the overview are minor padding that could be trimmed, fitting the efficient-with-minor-over-explanation 4 anchor.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for the common cases (connection ensure, login, polling, action list/run, request proxy) with concrete flags and a parameter table, matching the 5 anchor.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with an explicit state-feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but it references a "Step 2" that is never labeled, leaving a minor sequencing gap that fits the 4 anchor rather than the fully-checkpointed 5.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is inline; sections are well-organized with clear headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), which is good structure with minor gaps like inlined reference-style material, fitting the 4 anchor.

4 / 5

Total

17

/

20

Passed

Description

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

The description is well-structured with an explicit Use-when clause, third-person voice, and a distinctive product-name trigger. Its main weakness is generic action verbs ("manage data, records") that under-specify the skill's concrete financial-API capabilities.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Connect to banking and payment APIs, fetch account and transaction data, and initiate payments".

Broaden the when-clause with natural synonyms users actually say, such as "banking data", "account aggregation", or "payment initiation".

Mention the fintech/banking context to improve trigger-term coverage and distinguish it from generic data tools.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain plus a couple of actions, but the actions are generic ("manage data", "records") rather than concrete capabilities like payments or account aggregation, fitting the anchor that names 1-2 actions without comprehensive coverage.

3 / 5

Completeness

It answers both what ("Nordic API Gateway integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Nordic API Gateway data"), but the when-clause is somewhat circular and could be more specific, matching the 4 anchor.

4 / 5

Trigger Term Quality

"Nordic API Gateway" is exactly the natural phrase a user would say, and "interact with Nordic API Gateway data" gives good coverage, though synonyms like banking, payments, or fintech are missing, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The product name "Nordic API Gateway" anchors a clear niche with a distinct trigger, so it is unlikely to fire for an unrelated skill, matching the minimal-conflict 5 anchor.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-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.