Skip to main content

verify-a-data-export-checksum

Verify a data export checksum with a named algorithm, exact byte scope, manifest, transfer context, and semantic reconciliation. Use when proving that exported files arrived unchanged.

소스 정보

저장소
protosphinx/sphinxstack
최근 소스 활동
2026년 7월 29일 13:55
감지된 SKILL.md 언어
영어
스타
3
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
verify-a-data-export-checksum
category
data
description
Verify a data export checksum with a named algorithm, exact byte scope, manifest, transfer context, and semantic reconciliation. Use when proving that exported files arrived unchanged.
# verify-a-data-export-checksum ## When to use - Use for files, parts, archives, manifests, or transferred snapshots. - A checksum proves byte identity, not completeness, authorization, or semantic correctness. ## Procedure 1. Record export identity, producer, time, scope, files, sizes, algorithm, and expected hashes. 2. Preserve the signed or independently authenticated manifest. 3. Hash exact bytes without newline, archive, or encoding transformation. 4. Compare every file, part, manifest entry, total size, and unexpected extra. 5. Verify decryption and decompression at the intended layer separately. 6. Reconcile record counts, schema, boundaries, and expected source state. ## Failure plan - Quarantine mismatched or unmanifested data and request a new controlled export. ## Worked example All part hashes match, but the authenticated manifest lacks the final partition, so completeness fails. ## Done - A checksum verification report records export, manifest, algorithm, files, sizes, hashes, extras, and semantic reconciliation - Manifest-authenticity, byte-scope, part, archive, encryption, count, schema, and source-boundary checks verify transfer
GitHub에서 보기