Tessl • The management layer for AI agent skills

SkillPublic

blockstack

Blockstack integration. Manage data, records, and automate workflows. Use when the user wants to interact with Blockstack 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/blockstack/SKILL.md

Quality

Content

57%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 delivers genuinely actionable CLI guidance with a sensible connect-then-act flow and good state-handling checkpoints, but its organization undermines it: broken step cross-references, an empty 'Popular actions' section, duplicated commands, and filler content. It is a serviceable single-file skill that would score well with tightened structure and repaired internal references.

Suggestions

Fix the broken workflow numbering: define 'Step 1'/'Step 2' (or relabel '1b' and the 'skip to Step 2' references) so the connection-to-action sequence is coherent.

Either populate 'Popular actions' with actual common Gaia/Blockstack action examples or remove the section and keep the single discovery command in 'Searching for actions'.

Trim the filler 'Use action names and parameters as needed.' and the Blockstack definition paragraph, and remove the duplicated action-list command to tighten token usage.

Dimension	Reasoning	Score
Conciseness	The body is command-driven and mostly efficient, but includes unnecessary material: an overview tree ending in the filler 'Use action names and parameters as needed.', an intro explaining what Blockstack is, and a duplicated action-list command in 'Popular actions'. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened', not anchor 4 which requires only minor trimmable instances.	3 / 5
Actionability	Concrete copy-paste commands cover the common cases (install, login, connection ensure, action list/run, proxy with a flags table), matching 'Mostly executable guidance; concrete code or commands with minor gaps'. It falls short of anchor 5 because the 'Popular actions' heading promises example actions but delivers none, and placeholders like CONNECTION_ID and <actionId> are never instantiated.	4 / 5
Workflow Clarity	The connection flow has real checkpoints (poll with --wait, handle CLIENT_ACTION_REQUIRED, check the error field), but 'skip to Step 2' appears twice with no Step 2 in the document and '#### 1b.' exists with no '1a', leaving the sequence broken at those points. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than anchor 4's fully coherent sequence.	3 / 5
Progressive Disclosure	The ~140-line body inlines everything (full CLI guide plus a proxy flag table) with no external references, has clear section headers but dangling internal cross-references ('Step 2') and a misleading 'Popular actions' section. This matches 'Some structure but could be better organized' rather than anchor 4's well-placed content with clear navigation.	3 / 5
	Total	13 / 20 Passed

Description

57%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 an explicit and appropriate 'Use when...' trigger clause and a distinct niche (Blockstack), but the capability statement is generic — 'Manage data, records, and automate workflows' could describe almost any integration skill and names no concrete Blockstack operations (e.g., Gaia storage, files, shared links). Trigger coverage relies on a single term with no synonyms or ecosystem vocabulary.

Suggestions

Replace the generic action list with concrete Blockstack operations visible in the body, e.g., 'Manage files in Gaia storage buckets, create shared links, and query Blockstack records.'

Broaden trigger terms to include ecosystem vocabulary users might naturally say, such as 'Stacks', 'Gaia', 'decentralized apps', or 'Blockstack data storage', in the 'Use when...' clause.

Drop the buzzword-y 'automate workflows' phrasing in favor of one or two specific capabilities it actually covers.

Dimension	Reasoning	Score
Specificity	The domain is named ('Blockstack integration') but the stated actions are generic — 'Manage data, records, and automate workflows' names no concrete operation, matching the anchor 'Names the domain but actions are minimal or generic'. It falls below anchor 3 because no specific concrete action (comparable to 'extracts content') is listed.	2 / 5
Completeness	Both 'what' ('Blockstack integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Blockstack data') are present. It sits between anchors 3 and 4 because the 'when' clause is explicit but the 'what' is vaguer than anchor 4's example.	4 / 5
Trigger Term Quality	'Blockstack' and 'Blockstack data' are relevant natural keywords, but common variations and synonyms users might say (Stacks, Stacks blockchain, Gaia, decentralized apps) are absent, matching 'Some relevant keywords but missing common variations or synonyms'. It does not reach anchor 4 because there is effectively only one real trigger term.	3 / 5
Distinctiveness Conflict Risk	'Blockstack' is a clear niche term unlikely to trigger the wrong skill, matching 'Mostly distinct; minor overlap risk with closely related skills'. It falls short of anchor 5 because no distinct synonym triggers are given to fully delineate the niche.	4 / 5
	Total	13 / 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
Revision: f484c82

Reviewed: 16 days ago

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.

blockstack

Table of Contents

Is this your skill?