AF blockpi-blockchain-rpc
Multi-protocol BlockPI access skill for discovering documented methods, routing requests by protocol, mapping RU pricing, and calling BlockPI endpoints across JSON-RPC, HTTP, gRPC, and GraphQL where the official docs support them. Use when you need to validate whether a BlockPI method exists, estimate RU cost, pick the right protocol for a chain such as Sui or Solana, persist per-chain endpoints for jsonrpc/grpc/graphql, execute a live BlockPI call against a user-provided endpoint or token, or prepare protocol-aware designs like Sui gRPC and Solana Yellowstone gRPC.
As a process F 35/100 · Will not run — References files that are not bundled: references/rpc_catalog.json, scripts/build_blockpi_catalog.py
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/rpc_catalog.json - warning
missing-refreference to a missing file: scripts/build_blockpi_catalog.py
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: references/rpc_catalog.json, scripts/build_blockpi_catalog.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (blockpi-blockchain-rpc) differs from the folder (blockpi-rpc-skill)
- 70Failures and branches. 4 branches
- 85Steps. 42 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1853 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 572: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.