Name: fidel
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fidel

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fidel/SKILL.md

Quality

Content

76%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 copy-paste CLI commands and a strong connection workflow, but it lacks validation checkpoints for destructive operations and keeps all reference-grade detail inline. Adding verification steps and splitting reference material would raise the weakest dimensions.

Suggestions

Add an explicit validation/verification step before destructive action runs or proxy POST/PUT/DELETE calls (e.g. inspect --json output, confirm idempotency, or dry-run where supported).

Move the proxy flag table and clientAction state reference into a separate reference file linked from the body to improve progressive disclosure.

Trim motivational prose like 'so you can focus on the integration logic rather than auth plumbing' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and a tight flag table, but includes minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing', fitting 'efficient; minor instances of over-explanation that could be trimmed' below the lean 5 anchor.	4 / 5
Actionability	It provides copy-paste ready commands for install, login, connection ensure, action list/run, and proxy requests plus a thorough options table, fully matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	The connection flow has explicit state checkpoints and polling, but the skill enables destructive operations (proxy DELETE, action runs on records) with no validation/verification step, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Content is well organized into clear sections with no nested references, but everything (~140 lines including the proxy flag table and clientAction state detail) is inlined in a single file with no bundle split, fitting 'good structure; minor organization gaps' below the 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

48%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 correctly targets a distinct named niche and includes an explicit use-when trigger, but its capability statement is generic and lacks concrete Fidel-specific actions. Tightening the 'what' with specific operations would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Fidel-specific actions, e.g. 'Connect credit/debit cards, list transactions, manage programs and authorizations'.

Expand the trigger clause with natural user phrases like 'card transactions, transaction data, or Fidel API'.

Avoid the abstract 'automate workflows' phrasing in favor of what the integration actually does.

Dimension	Reasoning	Score
Specificity	The description names the Fidel domain but its actions ('Manage data, records, and automate workflows') are generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor and falling below the 3 anchor which requires specific actions.	2 / 5
Completeness	An explicit 'Use when the user wants to interact with Fidel data' clause is present, but the 'what' ('Manage data, records, and automate workflows') is too generic to count as a clear what, so it does not rise to the 4 anchor requiring both a clear what and when.	3 / 5
Trigger Term Quality	'Fidel' and 'interact with Fidel data' provide some relevant natural keywords, but common variations or synonyms beyond the brand name are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than 4.	3 / 5
Distinctiveness Conflict Risk	Fidel is a specific named financial API niche with a distinct trigger, giving low conflict risk, but the generic 'manage data, records, workflows' phrasing keeps minor overlap risk, fitting 'mostly distinct; minor overlap risk' below the 5 anchor.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/fidel/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.