Installation

Option 1: ClawhHub CLI (recommended)

Option 2: From GitHub

Archive Project Skill

Organize a completed project into a complete, long-term searchable archive.

Data Privacy: Archived data (session transcripts, project files) never leaves the internal workspace unless you explicitly approve a publish step. The sanitize script is applied automatically before any archival.

Trigger Conditions

Archive is triggered only when you say "archive this" or "can we archive this". This is the only trigger — you always decide when a project is done.

Trigger 2: Slash command

However, in these scenarios, I will prompt but not execute:

• - A delivery action just happened (email sent, demo link generated, all subagents done, code committed)
• You start a new project or say "next task" / "different topic"

I will NOT prompt when:

• - Project is still in active development
• Task is ongoing operations
• Waiting on external feedback (48h+ silence)

Archive Flow

Step 1: Create project archive directory

CODEBLOCK2

Step 2: Collect session transcripts

Subagent sessions (important — must collect):

CODEBLOCK3

Child subagent transcripts:

CODEBLOCK4

Step 3: Sanitize transcripts (CRITICAL — must do before archiving)

Before archiving, remove:

• - API keys, tokens, and authentication credentials
• Personal contact information (emails, phone numbers)
• Internal infrastructure details (hostnames, IPs)
• Any sensitive environment variables

Use the sanitization script:

CODEBLOCK5

The script redacts:

• - API keys (GitHub tokens, OpenAI keys, AWS credentials, etc.)
• Email addresses
• Phone numbers
• IP addresses (IPv4 and IPv6)
• Internal hostnames and AWS EC2 DNS names
• Generic secrets and high-entropy tokens

Verify before proceeding:
CODEBLOCK6

After verification, replace the original with the sanitized version:
CODEBLOCK7

Step 4: Write ARCHIVE.md

Use the template below. Fill in decision rationale — this is the most valuable part for future retrospectives.

Step 5: Update MEMORY.md

Add a one-line summary to MEMORY.md: project name + status + link.

Step 6: Delete EFS session files (requires approval)

Before deleting any session files from EFS, ask the user:

"Can I delete the EFS session files for this project? They are already backed up in the archive."

Only proceed if the user explicitly approves. Never auto-delete without asking.

If approved:
CODEBLOCK8

If not approved, leave the EFS session files as-is.

Step 7: Git commit (internal workspace only)

CODEBLOCK9

Keep project data private. Archive data is for internal reference only.

ARCHIVE.md Template

CODEBLOCK10bash

decisions.md Template

CODEBLOCK12

Sanitization Script Reference

The scripts/sanitize_transcript.py script provides deterministic, audited redaction of sensitive data from session transcripts.

What it redacts

Usage

CODEBLOCK13

Properties

• - Deterministic: Same input always produces identical output
• Non-destructive: Original file is never modified
• Structure-preserving: JSON/JSONL structure is maintained; only string values are redacted
• Testable: Built-in test mode verifies redaction patterns