Habilidades subgraph-migrate

📦

subgraph-migrate

Name: subgraph-migrate
Author: goldsky-io

Revisión del contenido r1 Crítico ⚙️ Comandos externos🌐 Acceso a red

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.

Compatible con: Claude Codex Code(CC)

⚠️ 38 Deficiente

Maintain this Skill? Claim it ⚠️ 38 Deficiente

No instales este Skill automáticamente.

La política canónica exige la revisión de un operador antes de cualquier acción de instalación.

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente

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.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/goldsky-io-subgraph-migrate.md Manifest firmado GET /api/skills/goldsky-io-subgraph-migrate/manifest Lockfile firmado GET /api/skills/goldsky-io-subgraph-migrate/lockfile

Pruébalo

Usando "subgraph-migrate". I have the old public GraphQL endpoint but no IPFS hash.

Resultado esperado:

Use the public endpoint migration path. Confirm the endpoint first, deploy the subgraph, and verify indexing before changing the application.

Usando "subgraph-migrate". The deployment is stuck at a low synchronization percentage.

Resultado esperado:

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.

Usando "subgraph-migrate". The migration is synced and I need a stable production endpoint.

Resultado esperado:

Create a production tag for the verified version, test its endpoint, then update the application to use the tagged URL.

Auditoría de seguridad

Crítico

v1 • 28/9/2026 Abrir el informe versionado

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.

Archivos escaneados

143

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (1)

Crítico

SKILL.md:55

Pipe to shell pattern

curl https://goldsky.com | sh

curl https://goldsky.com | sh executes content fetched from a remote server without local inspection, signature verification, or version pinning. A compromised server or transit path could execute arbitrary commands with the user's shell privileges.

Elementos de revisión de capacidades (1)

Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.

Bajo

SKILL.md:55

Hardcoded URL

curl https://goldsky.com | sh

The line uses a fixed external URL to download the CLI installer, creating a real network and supply-chain dependency. The critical risk comes from piping that response into a shell, while this verdict records the separate network exposure.

Patrones detectados

Pipe to shell pattern

Auditado por: codex

Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado

Copiar enlace del informe

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

Insignia Markdown

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

Insignia 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>

Tarjeta para insertar

<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>

Citas académicas (APA · BibTeX · CFF)

Cita 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/1

Cita BibTeX

@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"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Bajo

Arquitectura

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

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.

Prueba estos prompts

Start a migration

Help me migrate my subgraph from The Graph to Goldsky. Ask for the current endpoint or IPFS deployment hash before choosing a path.

Choose the source

I have a public GraphQL endpoint, an IPFS deployment hash, and local source. Compare the migration paths and recommend the safest option.

Deploy and verify

Guide me through deploying this subgraph to Goldsky, checking indexing progress, and identifying whether any error requires troubleshooting.

Plan production cutover

Create a production cutover checklist for my Goldsky subgraph, including a stable tag, endpoint validation, rollback considerations, and sync verification.

Mejores prácticas

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.

Evitar

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.

Preguntas frecuentes

What source information is required?

Provide the current GraphQL endpoint, the IPFS deployment hash, or local source when the published deployment is unavailable.

Does migration require subgraph code changes?

The standard migration is a drop-in replacement, but Goldsky validation can expose specification issues that require changes.

Which migration path should I use?

Use the public endpoint when available. Use the IPFS hash when you have the deployment identifier but no queryable endpoint.

How do I know the migration is working?

Check the deployment status and query metadata to confirm that the indexed block advances without indexing errors.

How should I avoid changing my frontend later?

Create a stable Goldsky tag and configure the application to use the tagged endpoint.

What if deployment or sync fails?

Capture the exact error and route it to the subgraph troubleshooting workflow. Do not guess at network or schema changes.

Detalles del desarrollador

Autor

goldsky-io

Licencia

MIT

Revisión de Skillstore

Aviso de versión

El autor no declaró una versión.

Repositorio

https://github.com/goldsky-io/goldsky-agent/tree/e8e18c16233d9a7cee64dc548ba779c5fb99205a/skills/subgraph-migrate

Ref.

8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1

Actualidad del mantenimiento

30/9/2026

Uso

0 descargas · 0 vistas

Estructura de archivos

📁 evals/

📄 trigger-eval.json

📄 SKILL.md

subgraph-migrate

Instalar con mi Agente

Recursos legibles por agentes

Pruébalo

Auditoría de seguridad

Preocupaciones de seguridad confirmadas (1)

Factores de riesgo

Patrones detectados

Copiar enlace del informe

Insignia Markdown

Insignia HTML

Tarjeta para insertar

Cita APA

Cita BibTeX

CITATION.cff

Puntuación de Skillstore

Lo que puedes crear

Replace a The Graph endpoint

Recover a sunset deployment

Validate a migration rollout

Prueba estos prompts

Mejores prácticas

Evitar

Preguntas frecuentes

Detalles del desarrollador