Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-template-render-pathAnálisis de malware y ransomware

competition-template-render-path

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for SSR, template rendering, route loaders, hydration payloads, server-client render boundaries, and template-to-handler enforcement gaps. Use when the user asks to inspect SSR or template routes, trace render context or hy⁩

v2026.9.22-cab634b3 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado ayer

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-template-render-path

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
g371CRrhKE…Kyc+ybDA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete1729ba40…22db4ce7
1729ba40b5dd…4f0822db4ce73 archivos · ⁦2.1 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-template-render-path@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive bug or artifact lives in route resolution, server render context, template data, or hydration handoff rather than in a plain JSON API alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.
  2. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.
  3. Compare template gating with loader or handler enforcement.
  4. Preserve one successful render and one failing render path with the smallest delta.
  5. Reproduce the smallest request-to-render branch that proves the decisive behavior.

Workflow

1. Map Route To Render Context

  • Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.
  • Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.
  • Keep server-only context and client-visible context separate.

2. Trace Template And Enforcement Boundaries

  • Show where permissions, feature flags, preview state, tenant selection, or host-based switches are applied.
  • Compare template-level gating, loader-level gating, and backend handler enforcement instead of trusting any one layer.
  • Record hidden fields, inline data, hydration JSON, meta tags, or alternate partials that expose the decisive branch.

3. Reduce To The Decisive Render Path

  • Compress the result to the smallest sequence: request -> route match -> loader or template context -> rendered output or hidden data -> resulting effect.
  • State clearly whether the decisive weakness lives in route selection, template context construction, server-client hydration handoff, or mismatched enforcement between render and handler.
  • If the task becomes mostly emitted bundle recovery or source map reconstruction, hand off to the tighter bundle skill.

Read This Reference

  • Load references/template-render-path.md for the render checklist, hydration checklist, and evidence packaging.

What To Preserve

  • Route names, loader names, templates, layouts, hydration keys, and host or preview switches
  • One success or failure pair that shows where render-layer behavior diverges
  • One minimal request-to-render sequence that reaches the decisive branch

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b1729ba40Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login