CtrlK
BlogDocsLog inGet started
Tessl Logo

bitquery

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

56

Quality

64%

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/bitquery/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, largely executable guide to driving Bitquery via the Membrane CLI, with strong connection-state validation and feedback loops. It is held back by duplicated commands, empty placeholder bullets, slightly inconsistent step numbering, and a generic product blurb at the top.

Suggestions

Remove the duplicated action-list command and the empty 'GraphQL Query'/'Response' overview bullets, or fill them with a concrete example query and response shape.

Fix the step numbering so 'Step 2' is an explicit labeled header and '1b' has a matching '1a', giving the connect→wait→search→run flow a coherent ordered sequence.

Add at least one end-to-end example showing a real GraphQL query run through `membrane action run` with an actual `--input` payload and the expected `output` field.

DimensionReasoningScore

Conciseness

Mostly lean with executable commands, but the action-list command is duplicated across sections, the overview bullets ('GraphQL Query' / 'Response') are empty placeholders, and the opening product blurb explains something Claude largely knows.

3 / 5

Actionability

Concrete executable commands throughout (install, login, connection ensure, action run, request with a flags table), with only minor gaps such as no example action invocation using real parameters or a sample GraphQL query.

4 / 5

Workflow Clarity

A clear install→authenticate→connect→poll→run sequence with explicit state-validation checkpoints and feedback loops (poll again after a client action); step numbering is slightly inconsistent (references an unlabeled 'Step 2' and a '1b' with no 1a), preventing a top score.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested/deep references and content appropriately placed inline for a CLI usage skill; falls short of 5 only because nothing is split into referenced files and there is no navigation to deeper material.

4 / 5

Total

15

/

20

Passed

Description

61%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 correctly pairs a what-clause with an explicit use-when trigger and is anchored to a distinct named product. Its main weakness is generic action language ('Manage data, records, and automate workflows') and missing natural synonyms like 'blockchain' or 'GraphQL'.

Suggestions

Replace generic verbs with concrete Bitquery actions, e.g. 'Run GraphQL queries against blockchain data, retrieve token transfers, and stream real-time DEX trades.'

Add natural trigger terms users would say — 'blockchain data', 'GraphQL', 'on-chain analytics', 'DEX trades' — to the Use when clause.

Tighten the Use when clause to specific intents, e.g. 'Use when the user wants to query on-chain data, analyze blockchain activity, or run GraphQL queries against Bitquery.'

DimensionReasoningScore

Specificity

Names the Bitquery domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete, matching the anchor for minimal/generic actions.

2 / 5

Completeness

Both a 'what' and an explicit 'Use when the user wants to interact with Bitquery data' trigger are present; the trigger could be more specific, fitting the anchor for both-with-room-to-improve.

4 / 5

Trigger Term Quality

'Bitquery' and 'data' are relevant keywords but it omits natural synonyms users would say such as 'blockchain', 'GraphQL', or 'crypto', so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

'Bitquery' is a named product producing a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

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.