CtrlK
BlogDocsLog inGet started
Tessl Logo

getblock

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/getblock/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is highly actionable with concrete Membrane CLI commands and a clear connect-then-query workflow including state-polling feedback loops, with only minor conciseness and labeling gaps.

DimensionReasoningScore

Conciseness

Largely efficient and command-driven with only minor marketing prose (e.g. "so you can focus on the integration logic rather than auth plumbing") that could be trimmed.

4 / 5

Actionability

Provides concrete, copy-paste-ready commands for the full workflow (install, login, connection ensure, poll, action list/run, proxy request) covering the common cases.

5 / 5

Workflow Clarity

Clear sequence with an explicit state-polling checkpoint and a re-poll feedback loop for CLIENT_ACTION_REQUIRED; minor gaps in step labeling (a referenced "Step 2" is not explicitly numbered).

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no external references needed; slightly over the simple-skill threshold and the thin "GetBlock Overview" list is a minor organization gap.

4 / 5

Total

17

/

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 answers both what and when with an explicit trigger, but its capability phrasing is generic and it lacks blockchain-synonym trigger terms that users would naturally say.

Suggestions

Replace generic verbs with concrete GetBlock-specific capabilities, e.g. "Query blockchain node data, send transactions, and read blocks/wallets via GetBlock RPC."

Add natural trigger terms and synonyms users actually say, such as "blockchain data," "blockchain nodes," "RPC," or "Web3."

Tighten the "what" so it reflects GetBlock's actual offering (node API access) rather than abstract "manage data, records, automate workflows."

DimensionReasoningScore

Specificity

Names the domain ("GetBlock integration") but the listed actions are generic and buzzwordy ("Manage data, records, and automate workflows") rather than concrete capabilities.

2 / 5

Completeness

Provides both a "what" and an explicit "Use when the user wants to interact with GetBlock data" trigger clause; the "what" is present but could be more specific.

4 / 5

Trigger Term Quality

Includes the relevant keyword "GetBlock" / "GetBlock data" but misses common synonyms a user might say such as blockchain, nodes, RPC, or Web3.

3 / 5

Distinctiveness Conflict Risk

The named GetBlock product gives a clear niche with minimal conflict risk, though the generic "manage data, records" phrasing creates minor overlap with other data skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.