# Reduce RPC Provider Calls with Goldsky Boost

Historical blockchain reads can increase RPC provider costs. This skill guides Goldsky Boost setup and cache troubleshooting while keeping your existing upstream provider.

## Install

```bash
npx skillstore add goldsky-io/boost
```

## Metadata

- Status: approved
- Slug: goldsky-io-boost
- Skillstore revision: r1
- Version status: missing
- Tree hash: 8062b36c508fee08047a659c22017231bb80692a0f33c7e11be2dd242876614a
- Author: goldsky-io
- GitHub username: goldsky-io
- License: MIT
- Repository: https://github.com/goldsky-io/goldsky-agent/tree/e8e18c16233d9a7cee64dc548ba779c5fb99205a/skills/boost
- Ref: 8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/goldsky-io-boost
- Manifest: https://skillstore.pages.dev/api/skills/goldsky-io-boost/manifest

## Capabilities

- Guide Boost setup with a connected QuickNode or Alchemy account, or an existing HTTPS provider endpoint.
- Explain cache eligibility for block, transaction, receipt, and log reads.
- Diagnose authentication errors, cache misses, batch behavior, and unsupported chains.
- Interpret cache headers, request history, and metrics for upstream request reduction.
- Explain provider activation, organization verification, and authentication forwarding.
- Show how to update a viem client transport to use a Boost endpoint.

## Use Cases

- Reduce Historical Indexing Requests: Plan Boost adoption for Ethereum or Base backfills, using concrete block ranges while retaining an existing provider.
- Investigate Cache Misses: Review cache headers, request history, and batch sizes to explain forwarding and identify eligible historical reads.
- Connect an Application: Adapt a viem transport and understand authentication, verification, and HTTP subscription boundaries before deployment.

## Prompt Templates

### Understand Boost

```
Explain whether Goldsky Boost fits our historical Ethereum reads. We want to keep our current RPC provider. Describe prerequisites and limitations.
```

### Plan Provider Setup

```
Plan Boost setup with QuickNode on Ethereum and Base. Use interactive credential entry, check verification requirements, and request approval before account changes.
```

### Diagnose Forwarded Requests

```
Our eth_getLogs requests end at latest, and receipt batches contain 200 items. Explain the MISS responses and propose a read-only verification plan.
```

### Review a Production Change

```
Plan a Boost upstream credential rotation with validation, explicit activation, and rollback. Keep secrets out of chat and command arguments. Require approval before mutations.
```

## Limitations

- Provides instructions, not a bundled RPC service or CLI implementation; live operations require configured Goldsky access.
- Boost supports HTTP only and offers chains with genesis coverage; WebSocket subscriptions remain with the upstream provider.
- Block tags and unsupported methods forward upstream, and eligible historical reads are not guaranteed cache hits.
- Configuration changes require organization verification; provider failover is manual, and cost savings depend on workload and provider pricing.

## Best Practices

- Check current CLI help and supported chains before planning changes, and validate the selected upstream against the intended chain.
- Use concrete historical block heights, keep batches within 100 items, and interpret served-item counts alongside cache headers.
- Keep secrets out of chat, logs, and command arguments; use supported secure credential entry and confirm account changes before execution.

## Anti Patterns

- Expecting block tags, state calls, or batches over 100 items to receive CDN caching.
- Treating one MISS response or a mixed-batch MISS as proof that Boost cannot serve historical data.
- Pasting credentials into chat or treating provider removal and disconnection as harmless diagnostic steps.

## Security Audit

- Audited at: 2026-09-28T16:21:58.654\+00:00
- Summary: All 104 static findings are false positives involving Markdown formatting, intended service URLs, credential placeholders, or provider setup documentation. One semantic finding concerns authentication secrets supplied through CLI arguments, which can expose them locally. No evidence found of prompt injection, malicious execution, or unauthorized exfiltration in the reviewed files.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0