Name: centrifuge
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

centrifuge

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

66%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 a well-structured, mostly executable integration guide with a clear connection workflow and explicit state handling. It is held back from higher scores by minor padding in the overview and slightly generic best-practice framing.

Suggestions

Trim the introductory 'Centrifuge is a platform for on-chain asset financing...' blurb and the bare overview bullet list, which Claude can infer or discover via action search.

Add a concrete example showing how to obtain CONNECTION_ID and actionId end-to-end (connection ensure output -> action list -> action run).

Add a brief verification step after proxy requests (e.g. checking the response status/shape) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and minimal concept over-explanation, but sections like the 'Pool/Pool State/Transaction/Invoice' overview list and the introductory platform blurb add padding that could be tightened.	3 / 5
Actionability	Provides concrete, copy-pasteable commands for install, login, connection ensure/get, action list/run, and proxy requests with flag tables; minor gaps around how to derive actionId and CONNECTION_ID values in practice.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checks (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling guidance; the destructive/batch cap is not triggered, though proxy/request examples lack a verify step.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Install, Auth, Connecting, Searching, Popular actions, Best practices) with no bundle files to reference; the inlined action/state reference is brief enough to stay inline.	4 / 5
	Total	15 / 20 Passed

Description

62%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 clear, third-person, and includes an explicit 'Use when' trigger, satisfying the core completeness bar. It would benefit from more concrete capability verbs and Centrifuge-specific trigger terms (pools, tokens, financing) to lift specificity and trigger-term quality.

Suggestions

Enumerate concrete Centrifuge actions (e.g. 'query pools, manage transactions, fetch invoices') instead of the generic 'Manage data, records, and automate workflows'.

Add natural trigger terms a user would say, such as 'on-chain financing', 'tokenize assets', 'DeFi pools', or 'real-world assets'.

Tighten the 'Use when' clause to reference Centrifuge-specific scenarios rather than only 'interact with Centrifuge data'.

Dimension	Reasoning	Score
Specificity	Names the domain (Centrifuge integration) and several concrete actions ('Manage data, records, and automate workflows'), but the actions are moderately generic with minor gaps in coverage rather than a comprehensive enumerated list.	4 / 5
Completeness	It states what the skill does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Centrifuge data'), with the 'when' explicit but somewhat generic.	4 / 5
Trigger Term Quality	It surfaces 'Centrifuge' and 'data, records, and automate workflows' plus a 'Use when' clause, but it omits common natural synonyms or variations a user might actually say (e.g. 'on-chain financing', 'tokenize assets', 'pools', 'DeFi').	3 / 5
Distinctiveness Conflict Risk	The Centrifuge-specific name and trigger make it mostly distinct with only minor overlap risk against other integration skills.	4 / 5
	Total	15 / 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/centrifuge/SKILL.md
Commit: f484c82

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