📦

boost

Name: boost
Author: goldsky-io

コンテンツリビジョン r1 中リスク ⚙️ 外部コマンド🌐 ネットワークアクセス🔑 環境変数

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.

対応: Claude Codex Code(CC)

📊 70 十分

Maintain this Skill? Claim it 📊 70 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "boost" from https://skillstore.io/skills/goldsky-io-boost.md and its manifest at https://skillstore.io/api/skills/goldsky-io-boost/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/goldsky-io-boost.md 署名済み manifest GET /api/skills/goldsky-io-boost/manifest 署名済み lockfile GET /api/skills/goldsky-io-boost/lockfile

テストする

「boost」を使用しています。 Why do log queries ending at latest always miss the cache?

期待される結果:

Block tags always forward to your upstream provider.
For a fixed historical range, use concrete hexadecimal block heights for both bounds.
Repeat the request and inspect cache headers; eligible data can still forward when unavailable.

「boost」を使用しています。 My receipt batch has 200 items and reports MISS. Is caching broken?

期待される結果:

Batches over 100 items forward without CDN lookups.
Split requests into batches of at most 100 items and assign unique request identifiers.
A mixed batch reports MISS even when some items are served; inspect x-edge-billable for the served-item count.

「boost」を使用しています。 Does an organization verification error stop our existing Boost traffic?

期待される結果:

The documented verification gate applies to configuration changes, not existing request serving.
Check organization eligibility or contact Goldsky support with your team identifier.
Do not share API keys or provider credentials in chat.

セキュリティ監査

中リスク

v1 • 2026/9/28 バージョン別レポートを開く

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.

スキャンされたファイル

323

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (1)

中

SKILL.md:157 SKILL.md:167-168 SKILL.md:220

Provider Credentials Exposed Through CLI Arguments

The guide recommends 'provider add --header k:v' for a persistent provider credential. Substituting secrets into command arguments can expose them through shell history and process listings.

Line 220 explicitly recommends CLI header arguments for credentials, while the interactive-input safeguard on line 174 covers only provider connect. Actual exposure depends on execution and host controls.

リスク要因

⚙️ 外部コマンド (50)

🌐 ネットワークアクセス (7)

SKILL.md:23 SKILL.md:51 SKILL.md:60 SKILL.md:196 SKILL.md:222 SKILL.md:271 SKILL.md:272

🔑 環境変数 (1)

SKILL.md:23

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/goldsky-io-boost/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/goldsky-io-boost/security.svg)](https://skillstore.io/skills/goldsky-io-boost?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/goldsky-io-boost?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/goldsky-io-boost/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/goldsky-io-boost.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

goldsky-io. (2026). boost security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/goldsky-io-boost/audits/1

BibTeX形式の引用

@techreport{goldsky-io-goldsky-io-boost-2026,
  author = {goldsky-io},
  title = {boost security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/goldsky-io-boost/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "boost security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "goldsky-io"
date-released: "2026-09-28"
url: "https://skillstore.io/skills/goldsky-io-boost/audits/1"
identifiers:
  - type: other
    value: "skillstore:goldsky-io-boost:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

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.

これらのプロンプトを試す

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.

ベストプラクティス

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.

回避

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.

よくある質問

Does Boost replace my existing RPC provider?

No. Boost serves eligible reads and forwards other requests to your configured provider. Goldsky Edge is the separate managed RPC product.

Does Boost guarantee lower bills?

No. The guide describes Boost as free, but savings depend on served requests, provider pricing, and workload eligibility.

Why does eth_getLogs still forward?

Block-tag bounds always forward. Concrete bounds or a block hash enable eligibility, but unavailable data still forwards.

Can I use WebSocket subscriptions?

No. Boost is HTTP-only. Keep WebSocket subscriptions connected directly to your provider.

Do I need a verified organization?

The guide requires verification for enabling Boost and most configuration changes. Reading configuration and serving existing traffic do not require verification.

How should I provide credentials?

Never paste credentials into chat. Use the interactive prompt for provider connect and a supported secure input method for other secrets.