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.
Diesen Skill nicht automatisch installieren.
Die maßgebliche Richtlinie verlangt vor jeder Installationsaktion eine Prüfung durch einen Bediener.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„subgraph-migrate“ wird verwendet. I have the old public GraphQL endpoint but no IPFS hash.
Erwartetes Ergebnis:
Use the public endpoint migration path. Confirm the endpoint first, deploy the subgraph, and verify indexing before changing the application.
„subgraph-migrate“ wird verwendet. The deployment is stuck at a low synchronization percentage.
Erwartetes Ergebnis:
- 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“ wird verwendet. The migration is synced and I need a stable production endpoint.
Erwartetes Ergebnis:
Create a production tag for the verified version, test its endpoint, then update the application to use the tagged URL.
Sicherheitsaudit
KritischThe 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.
Bestätigte Sicherheitsbedenken (1)
Elemente der Fähigkeitsprüfung (1)
Dies sind echte lokale Fähigkeiten, die für diese Fähigkeit erwartet werden können; daher müssen sie überprüft werden, werden jedoch nicht als bestätigtes bösartiges Verhalten gezählt.
Risikofaktoren
⚙️ Externe Befehle (38)
🌐 Netzwerkzugriff (3)
Erkannte Muster
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/goldsky-io-subgraph-migrate/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/goldsky-io-subgraph-migrate?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
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-Zitat
@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-Score
Warum dieser Score Evidenzvertrauen: NiedrigWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
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?
Entwicklerdetails
Autor
goldsky-ioLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1
Aktualität der Wartung
30.9.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur