Name: algorand
Rating: 56.8 (1 reviews)
Author: membranedev

algorand

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

Quality

65%

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

Quality

Content

67%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 concrete CLI commands and a well-sequenced connection workflow including state-driven checkpoints. Its main weakness is a boilerplate intro paragraph explaining concepts Claude already knows.

Suggestions

Remove or drastically shorten the introductory paragraph explaining what Algorand is; Claude already knows this and it consumes context for no gain.

Explicitly label 'Step 2' (the action/proxy workflow) so the cross-reference from the connection section resolves clearly.

Add a brief validation/verification note for proxy requests (e.g. checking HTTP status and error fields) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ('Algorand is a blockchain platform and cryptocurrency designed for speed and security...') explains concepts Claude already knows, which the rubric penalizes; the rest is mostly efficient, matching the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action run, request) plus a proxy flag table, matching the score-4 anchor of mostly executable guidance with minor gaps such as generic <actionId>/CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connection setup is well sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, matching the score-4 anchor; not a 5 because 'Step 2' is referenced but never explicitly labeled, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	A single-file skill with no bundle files, organized into clear headed sections (install, auth, connecting, actions, proxy, best practices); good structure with minor organization gaps rather than the lean overview-plus-references pattern of a 5.	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 clearly names the Algorand niche and provides an explicit 'Use when' trigger, but its action verbs are generic and it lacks keyword variations. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Algorand-specific actions such as querying accounts, assets, transactions, and blocks.

Expand trigger terms to include natural phrasings users might say, e.g. 'Algorand accounts, assets, transactions, blocks, or on-chain data'.

Tighten the 'Use when' clause to reference specific Algorand objects so the trigger is more distinctive.

Dimension	Reasoning	Score
Specificity	Names the domain (Algorand) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the score-3 anchor of domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	States both the 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Algorand data'), matching the score-4 anchor where both are present but 'when' could be more specific; not a 5 because the trigger phrases are thin.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Algorand' and 'Algorand data' but offers no synonyms or variations a user might say, fitting the score-3 anchor of relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	'Algorand' is a clear, niche trigger with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with other integration skills, matching the score-4 anchor.	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/algorand/SKILL.md
Commit: f484c82

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