archive-protocol

Name: archive-protocol
Availability: InStock
Author: kweaver

Archive task outputs to the archives directory with validation and session tracking.

Updated Aug 23, 2026

Search Tags:#archives #compliance #protocol #archive #archiving #task-outputs

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive-protocol
Source: https://github.com/kweaver-ai/kweaver-dip/tree/main/deploy/openclaw-extensions/dip/skills/archive-protocol
Command: npx skills add https://github.com/kweaver-ai/kweaver-dip --skill archive-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol ensures that all artifacts generated during a task are archived to a centralized archives area, enforcing traceability and compliance.

Core Features & Use Cases

End-to-end archiving: Automatically moves PLAN.md, reports, JSON, and other artifacts to archives/ with proper ARCHIVE_ID and TIMESTAMP.
Audit-ready workflow: Validates that no artifacts remain in the working area after archiving and supports WebUI archive grids.
Use Case: When a project finishes, all outputs are relocated to archives/ and a verification log is generated.

Quick Start

Apply the archive protocol to ensure all outputs move to archives after task completion.

Frequently Asked Questions about archive-protocol

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

FAQPage Schema

How do I automatically move task outputs like reports and JSON files to an archives directory?▼

To automatically move task outputs to an archives directory, apply an end-to-end archiving protocol that relocates plans, reports, and JSON artifacts with proper ARCHIVE_ID and TIMESTAMP. This ensures traceability and compliance for completed workflows.

What is post-archive validation for workflow compliance?▼

Post-archive validation for workflow compliance is a verification mechanism that checks no artifacts remain in the working area after archiving. It generates a verification log to prove all outputs moved successfully to the archives directory.

Does the archiving protocol support session tracking for audit-ready workflows?▼

Yes, the archiving protocol supports session tracking for audit-ready workflows. It enforces session tracking alongside post-archive validation to ensure complete traceability of all relocated task artifacts.

How do I ensure traceability for generated plans, summaries, and JSON artifacts?▼

To ensure traceability for generated plans, summaries, and JSON artifacts, use an automated archiving protocol that moves outputs to a centralized archives area. This enforces traceability by assigning ARCHIVE_ID and TIMESTAMP records to all relocated files.

What is the best way to archive task outputs end-to-end for compliance?▼

The best way to archive task outputs end-to-end for compliance is using a protocol that automatically moves all artifacts via an archive tool to a centralized area. It enforces post-archive validation to confirm no files remain in the working directory.

When do I need to archive task outputs to a centralized area?▼

You need to archive task outputs to a centralized area when a project finishes and you must enforce compliance. This relocation step moves all plans, reports, and JSON artifacts out of the working area to generate a verification log.