Name: decentro
Rating: 58.4 (1 reviews)
Author: membranedev

decentro

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

Quality

68%

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/decentro/SKILL.md

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.

The content is highly actionable with concrete, executable CLI commands and a well-structured connection workflow with validation checkpoints. Its main weaknesses are minor over-explanation in the prose and a broken step-numbering scheme that slightly muddies the workflow sequence.

Suggestions

Fix the step numbering: add an explicit 'Step 1'/'Step 2' framing and rename '1b' so the 'skip to Step 2' reference resolves, which would clarify the connection workflow.

Trim the introductory paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' to tighten conciseness.

Consider moving the proxy-requests flag table and the full clientAction state-machine detail into a reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but contains some over-explanation that could be trimmed, such as the intro paragraph explaining what Decentro is and 'so you can focus on the integration logic rather than auth plumbing', fitting the 'mostly efficient but includes some unnecessary explanation' anchor; it is not score 2 because the padding is limited rather than extensive.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run, proxy with a full flag table) covering the common cases, matching the 'fully executable; copy-paste ready code or commands' anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with validation checkpoints (poll until READY, a state machine handling READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the step numbering is broken ('skip to Step 2' with no Step 2 header, a '1b' with no '1a'), which is a minor gap preventing a score of 5; no destructive or batch operations apply the cap.	4 / 5
Progressive Disclosure	The ~150-line body is well-organized into clear sections (Overview, Working with Decentro, Best practices) with no bundle files present, matching 'good structure; most content appropriately placed'; it does not reach 5 because at over 50 lines the proxy flags table and detailed clientAction state machine could plausibly live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

61%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 has a clear, distinct trigger tied to the named Decentro platform and an explicit use-when clause, but it is let down by generic action language that under-describes what the skill actually does. Tightening the 'what' to list concrete Decentro operations would raise specificity and completeness.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Decentro actions such as beneficiary validation, remittance, UPI collect requests, and KYC verification to improve specificity.

Add natural trigger terms a user would actually say (e.g. 'Decentro API', 'UPI payments', 'banking verification', 'KYC') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Decentro domain but its actions ('Manage data, records, and automate workflows') are generic rather than the concrete Decentro operations (beneficiary validation, UPI collect, KYC verification) shown in the body, matching the 'names the domain but actions are minimal or generic' anchor rather than score 3 which requires concrete actions.	2 / 5
Completeness	It states both the 'what' ('Decentro integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Decentro data'), matching the anchor where both are present; it does not reach 5 because the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	'Decentro' is a specific natural product term, but the remaining keywords ('data', 'records', 'workflows') are generic and common user-said synonyms or variations are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Decentro platform with the trigger 'interact with Decentro data' creates a clear niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	14 / 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/decentro/SKILL.md
Commit: f484c82

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