enclave-attestation

Name: enclave-attestation
Availability: InStock
Author: Latch

Audit Latch Enclave sessions and generate tamper-evident logs and receipts.

2|Updated Feb 26, 2026

Search Tags:#compliance #audit logging #Merkle tree #session attestation #GitHub PR annotation

Ready to run

npx skills add https://github.com/latchagent/latch-core --skill enclave-attestation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enclave-attestation
Source: https://github.com/latchagent/latch-core/tree/main/.agents/skills/enclave-attestation
Command: npx skills add https://github.com/latchagent/latch-core --skill enclave-attestation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides secure audit logging and session attestation for the Latch Enclave, ensuring tamper-evident logging and session receipt verification for compliance and security needs.

Core Features & Use Cases

Audit Logging: Captures hash-chained proxy audit events and Merkle tree proofs.
Session Attestation: Generates and verifies session receipts for compliance proofs and inclusion proofs.
PR Annotation: Posts attestation receipts as GitHub PR comments for traceability.
Use Case: For organizations needing to demonstrate compliance with security policies and maintain audit trails for code reviews and collaboration.

Quick Start

Generate and annotate a GitHub PR with session attestation data using the enclave-attestation skill.

Frequently Asked Questions about enclave-attestation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create tamper-evident audit logs for secure enclave sessions?▼

Tamper-evident audit logs for secure enclave sessions are created by capturing hash-chained proxy events and generating Merkle tree proofs. This Skill automates that logging process and provides session receipts for compliance verification.

Can I post session attestation receipts as comments on GitHub pull requests?▼

Yes, session attestation receipts can be posted as GitHub PR comments. This Skill integrates with the GitHub API to annotate pull requests directly, ensuring traceability and compliance proofs are visible during code reviews.

What is a Merkle tree inclusion proof and when do I need it for compliance?▼

A Merkle tree inclusion proof is a cryptographic verification that a specific session event exists within the audit log. You need it for compliance to mathematically prove session data has not been altered.

Do I need Ed25519 signing keys to generate session attestation receipts?▼

Yes, Ed25519 signing is required to generate and verify session attestation receipts. This cryptographic signing ensures the authenticity and integrity of the compliance proofs and audit trail data.

What is the best way to verify session receipts for security compliance audits?▼

The best way to verify session receipts for compliance audits is using Merkle tree inclusion proofs and Ed25519 signature validation. This Skill handles that verification process to prove session data integrity.

Are there limitations to using hash-chained proxy audit logging for enterprise compliance?▼

Hash-chained proxy audit logging requires continuous Ed25519 key management and GitHub API access to function properly. If the signing keys are compromised or API access is lost, attestation verification will fail.