Name: blockstack
Rating: 61.6 (1 reviews)
Author: membranedev

blockstack

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

Quality

72%

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

Quality

Content

82%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 copy-paste commands and a well-sequenced connection workflow including state-aware checkpoints. It is efficient and well-structured, with only minor redundancy and no explicit post-action validation loop.

Suggestions

Remove the duplicated `membrane action list` command between "Searching for actions" and "Popular actions" to tighten conciseness.

Add an explicit verify step after `membrane action run` (e.g. check the `output`/`error` fields and retry on failure) to close the workflow validation gap.

Consider splitting the proxy flags table and best practices into a separate reference file to improve progressive disclosure for this 140-line skill.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands with only minor padding (the opening Blockstack definition and a repeated `membrane action list` command across two sections), fitting the efficient anchor with minor trim opportunities.	4 / 5
Actionability	It provides copy-paste ready bash commands throughout with concrete flags, a full proxy-options table, and JSON-output guidance, matching the fully executable anchor that covers common cases.	5 / 5
Workflow Clarity	A clear sequence runs install → authenticate → connect → poll for READY → search → run, with explicit state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) as checkpoints, but it lacks an explicit verify/retry loop after running actions, fitting the clear-sequence anchor with minor validation gaps.	4 / 5
Progressive Disclosure	The single-file body is well-organized into clearly labeled sections with no nested references, but all content is inlined (no bundle files exist) and a few blocks like the proxy flags table could live separately, fitting the good-structure anchor with minor organization gaps.	4 / 5
	Total	17 / 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 cleanly states both capability and trigger with a distinctive domain name, but the listed actions are generic and the trigger terms lack synonyms or variations. It is solid but not comprehensive.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Blockstack-specific actions such as read/write Gaia storage files or list shared links.

Expand the trigger clause with natural variations, e.g. "Use when the user wants to interact with Blockstack data, Gaia storage, or shared links."

Add file/extension or resource cues (e.g. Gaia buckets) to strengthen distinctiveness against general data skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Blockstack domain plus a couple of actions, but the actions are generic rather than concrete (no specific verbs like extract, create, or query), matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Blockstack data"), with an explicit trigger clause; the 'when' is present and clear but could be more specific, matching the anchor for both present with room for sharper triggers.	4 / 5
Trigger Term Quality	"Blockstack data" supplies the core natural keyword, but the description lacks synonyms or common variations a user might say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Blockstack integration" carves a clear niche with a distinct trigger unlikely to fire for unrelated skills, though the generic action verbs leave minor overlap risk with other data-management skills, fitting the mostly-distinct 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/blockstack/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.