subgraph-migrate
Migrate a Subgraph to Goldsky
Moving from The Graph can require a reliable source identifier, deployment path, and endpoint transition. This skill guides the migration and verifies sync before application cutover.
請勿自動安裝此 Skill。
權威政策要求在執行任何安裝操作前由操作人員審查。
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "subgraph-migrate" from https://skillstore.io/skills/goldsky-io-subgraph-migrate.md and its manifest at https://skillstore.io/api/skills/goldsky-io-subgraph-migrate/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「subgraph-migrate」。 I have the old public GraphQL endpoint but no IPFS hash.
預期結果:
Use the public endpoint migration path. Confirm the endpoint first, deploy the subgraph, and verify indexing before changing the application.
正在使用「subgraph-migrate」。 The deployment is stuck at a low synchronization percentage.
預期結果:
- Check the reported network and deployment status.
- Treat a low percentage as a possible mapping or handler error.
- Send the exact error to the subgraph troubleshooting workflow.
正在使用「subgraph-migrate」。 The migration is synced and I need a stable production endpoint.
預期結果:
Create a production tag for the verified version, test its endpoint, then update the application to use the tagged URL.
安全審計
嚴重The 38 external-command findings are false positives caused by Markdown backticks, code fences, and inline command examples in SKILL.md. The installer command at SKILL.md:55 pipes a remote script into a shell and is a confirmed critical supply-chain risk; the three hardcoded URLs are expected service or documentation endpoints, with the installer URL retaining a low network risk.
已確認的安全問題 (1)
能力複核項目 (1)
這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。
風險因素
⚙️ 外部命令 (38)
🌐 網路存取 (3)
偵測到的模式
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/goldsky-io-subgraph-migrate/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/goldsky-io-subgraph-migrate?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/goldsky-io-subgraph-migrate?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/goldsky-io-subgraph-migrate/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/goldsky-io-subgraph-migrate.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). subgraph-migrate security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/goldsky-io-subgraph-migrate/audits/1BibTeX 引用
@techreport{goldsky-io-goldsky-io-subgraph-migrate-2026,
author = {goldsky-io},
title = {subgraph-migrate security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/goldsky-io-subgraph-migrate/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: "subgraph-migrate 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-subgraph-migrate/audits/1"
identifiers:
- type: other
value: "skillstore:goldsky-io-subgraph-migrate:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 低你可以打造什麼
Replace a The Graph endpoint
Move a production subgraph to Goldsky while preserving the existing application query model.
Recover a sunset deployment
Use an existing endpoint or IPFS deployment hash when a former hosted subgraph endpoint is unavailable.
Validate a migration rollout
Deploy, monitor indexing, create a stable tag, and prepare the new endpoint for an application cutover.
試試這些提示
Help me migrate my subgraph from The Graph to Goldsky. Ask for the current endpoint or IPFS deployment hash before choosing a path.
I have a public GraphQL endpoint, an IPFS deployment hash, and local source. Compare the migration paths and recommend the safest option.
Guide me through deploying this subgraph to Goldsky, checking indexing progress, and identifying whether any error requires troubleshooting.
Create a production cutover checklist for my Goldsky subgraph, including a stable tag, endpoint validation, rollback considerations, and sync verification.
最佳實務
- Require the user to provide and verify the source endpoint or IPFS hash.
- Confirm indexing progress before changing the application endpoint.
- Use a stable tag so future deployments do not require frontend URL changes.
避免
- Do not guess a The Graph endpoint, IPFS hash, network, or deployment name.
- Do not declare success before the Goldsky index advances and the endpoint responds.
- Do not use this workflow to diagnose complex mapping or synchronization errors.
常見問題
What source information is required?
Does migration require subgraph code changes?
Which migration path should I use?
How do I know the migration is working?
How should I avoid changing my frontend later?
What if deployment or sync fails?
開發者詳細資訊
作者
goldsky-io授權
MIT
Skillstore 修訂
r1
版本提示
作者未聲明版本。
引用
8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1
維護新鮮度
2026/9/30
使用量
0 次下載 · 0 次瀏覽
檔案結構