Name: overledger
Rating: 52.8 (1 reviews)
Author: membranedev

overledger

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

Quality

59%

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

Quality

Content

56%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 CLI usage guide is genuinely strong — executable commands, a well-sequenced connection workflow with state polling and error recovery, and useful best practices. The skill is dragged down by a massive, mostly-irrelevant bullet 'overview' that inflates token cost and belongs in a separate file or should be removed entirely.

Suggestions

Delete or externalize the 'Overledger Overview' bullet list: the vast majority of entries (Spiritual Growth, Venture Capital, Climate Change, etc.) are unrelated to Overledger and add no actionable value.

Fix the broken step references in the connection flow — label the 'Searching for actions' step as 'Step 2' and reconcile the stray '1b' heading so the sequence is unambiguous.

De-duplicate action discovery: the 'Searching for actions' and 'Popular actions' sections repeat the same `action list --intent` command; consolidate them and add a brief note on interpreting inputSchema/outputSchema.

Dimension	Reasoning	Score
Conciseness	The actionable sections are reasonably lean, but the ~290-line 'Overledger Overview' bullet list (e.g. 'Spiritual Growth', 'Venture Capital', 'Initial Public Offering', 'Climate Change') is heavy, largely irrelevant padding that does not earn its tokens, fitting the 'noticeably verbose; several padded sections' anchor and approaching the severely-padded level 1.	2 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure/get --wait, action list/run, request with a full flag table), covering the common cases copy-paste ready; minor gaps are unresolved placeholders (CONNECTION_ID, <actionId>) and a redundant 'Popular actions' section repeating the search command.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based validation checkpoints and a feedback loop (poll --wait, handle CLIENT_ACTION_REQUIRED, re-poll after user action, check CONFIGURATION_ERROR); it stays at 4 rather than 5 because 'Step 2' is referenced but unlabeled, the '1b' numbering is inconsistent, and action-run results lack a verify step.	4 / 5
Progressive Disclosure	The body has clear section headers, but with no bundle files and everything inlined, the ~290-line overview list is content that should live in a separate reference file or be deleted, matching the 'some structure but content that should be separate is inline' anchor; the under-50-line exception does not apply to this ~440-line skill.	3 / 5
	Total	13 / 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 a solid, third-person statement that covers both what and when with an explicit 'Use when' clause, anchored by a distinctive product name. Its weakness is generic action verbs and narrow trigger-term coverage rather than concrete capabilities and synonyms.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query transactions, read balances, submit payments, and manage wallet addresses across blockchains via Overledger.'

Add natural trigger synonyms and tokens users say, such as 'blockchain transactions', 'Overledger API', 'quant network', or '.quant' where applicable.

Tighten the 'when' clause to specific intents, e.g. 'Use when the user wants to read or write blockchain data, check transaction status, or automate cross-chain workflows through Overledger.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Overledger integration') and three actions ('Manage data, records, and automate workflows'), but the actions are generic verbs ('manage') rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor rather than the more concrete level 4.	3 / 5
Completeness	It explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Overledger data'); the 'when' is explicit but the 'what' is generic, so it sits at level 4 rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'Overledger' (repeated as 'Overledger data'), with no synonyms, related terms, or file extensions, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'Overledger' gives it a clear niche with minimal conflict risk, but the generic 'manage data, records, workflows' phrasing retains minor overlap risk with broad data-management skills, placing it just below the clearly-distinct level 5.	4 / 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/overledger/SKILL.md
Commit: f484c82

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