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
aeondave/verification-before-completionInformes y cumplimiento

verification-before-completion

⁨Check evidence before reporting work complete, fixed, passing, or ready. Use at a completion boundary or when later changes may have invalidated an earlier result.⁩

v2026.11.13-21cd5683 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 10 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/verification-before-completion

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

FirmaFirmado, ed25519
Mb91943Npb…lU5v3TBA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete47e74fe7…9b1851aa
47e74fe7810d…39ce9b1851aa2 archivos · ⁦2.5 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/behaviours/verification-before-completion@21cd568

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

Match each completion claim to evidence for the state being delivered. evidence-before-claims owns general evidence quality and uncertainty; this skill checks freshness and coverage.

Completion gate

  1. Name the outcome being claimed and the check that can detect its failure.
  2. Run the relevant check after the last change that could affect its result. Preserve required repository gates.
  3. Inspect exit status, substantive output, skipped cases, and the artifact or state actually checked.
  4. Map the evidence to acceptance criteria. Report uncovered requirements and unavailable checks explicitly.
  5. Investigate failures, correct in-scope causes, and rerun affected checks. Report unresolved failures and uncertain attribution. Once checks pass, repeat or broaden them only for a new change, failure, or unresolved concern.

A recorded result may be reused when its command, relevant inputs and checked state, environment, and coverage still apply. Compare changes since that result: a new turn, reader, commit, or unrelated edit does not alone invalidate it. Rerun affected checks when relevant inputs change; reverify when provenance or applicability cannot be established.

Select the check

Claim Useful evidence Limit
Tests pass Relevant suite on the delivered code Passing tests do not establish untested requirements.
Build succeeds Successful build for the intended target Lint alone does not establish a build.
Bug fixed Original failure reproduced and then resolved A nearby edit is not proof; disclose unavailable baseline reproduction.
Skill structure valid Frontmatter validation and resource sweep Structural checks do not prove behavior or token savings.
Delegated work complete Inspect diff/artifacts and corresponding check output Rerun when state, coverage, or provenance is insufficient; a summary alone is not evidence.
Remediation complete Relevant post-action state A successful command may not establish the intended effect.

Use diff inspection and required structural checks for low-impact editorial work; do not invent runtime tests that merely mirror text. Distinguish checks not run from checks that failed.

Load references/completion-evidence.md when choosing regression evidence, comparing implementation with an agreed design, or diagnosing an overstated completion claim.

Archivos de esta versión

Permisos

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

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

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

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd56847e74fe7Firmada–

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