bkn-archive

Name: bkn-archive
Availability: InStock
Author: kweaver

Generate ARCHIVE_ID and TIMESTAMP for OpenClaw session archival workflows.

Updated Aug 23, 2026

Search Tags:#archive #timestamp #data-governance #openclaw #archive-id #document-archival

Ready to run

npx skills add https://github.com/kweaver-ai/kweaver-dip --skill bkn-archive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bkn-archive
Source: https://github.com/kweaver-ai/kweaver-dip/tree/main/skills/bkn-creator/internal/bkn-archive
Command: npx skills add https://github.com/kweaver-ai/kweaver-dip --skill bkn-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a centralized archival protocol that automates ARCHIVE_ID and TIMESTAMP generation, enforces deterministic archive paths, and validates read-backs after writing artifacts.

Core Features & Use Cases

Governance of archives: generate ARCHIVE_ID from session_status (or fallback) and enforce paths like archives/{ARCHIVE_ID}/{TIMESTAMP}/{ORIGIN_NAME} to ensure traceability.
Lifecycle coverage: archive common outputs such as PLAN.md, report.md, summary.md, result.json, and notes.md, enabling consistent recovery and audits.
Real-world scenarios: ensures archiving before task completion in OpenClaw-enabled workflows, with post-write verification.

Quick Start

Execute the archive protocol before any file write to ensure all artifacts are archived predictably.

Frequently Asked Questions about bkn-archive

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

FAQPage Schema

How do I automate document archival for OpenClaw session artifacts?▼

You can automate document archival by generating an ARCHIVE_ID and TIMESTAMP, then enforcing a deterministic archive path like archives/{ARCHIVE_ID}/{TIMESTAMP}/{ORIGIN_NAME} for session artifacts such as report.md and result.json.

What is the archive path scheme for storing OpenClaw outputs?▼

The archive path scheme is archives/{ARCHIVE_ID}/{TIMESTAMP}/{ORIGIN_NAME}, which ensures traceability and recoverability for artifacts like PLAN.md, summary.md, and notes.md generated during OpenClaw sessions.

How does post-write verification work for archived artifacts?▼

Post-write verification validates read-backs after writing artifacts to the enforced archive paths, ensuring that files like PLAN.md and result.json are successfully stored and recoverable within the OpenClaw archival workflow.

Can I use session_status to generate ARCHIVE_ID for data governance?▼

Yes, the archival protocol extracts ARCHIVE_ID directly from session_status when available, applying a fallback mechanism if absent, to maintain consistent data governance and traceability across OpenClaw workflows.

What file types are covered by the OpenClaw archival workflow?▼

The archival workflow covers common session outputs including PLAN.md, report.md, summary.md, result.json, and notes.md, ensuring these artifacts are consistently archived before task completion for audits and recovery.

When do I need to run the archival protocol in an OpenClaw workflow?▼

You need to run the archival protocol before any file write operation to ensure all OpenClaw session artifacts are predictably archived, enabling consistent recovery, traceability, and data governance prior to task completion.