Skills suchen.../

Archive | Skills Pool

Skill-Datei

Archive

Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says "archive this". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.

ReScienceLab788 Sterne13.03.2026

Beruf
Kategorien: Debugging

Skill-Inhalt

Archive Skill

Capture, index, and reuse project knowledge across sessions.

When to Archive

After completing a significant task (deploy, migration, major feature)
After resolving a tricky debugging session
When the user says "archive this"
After any multi-step process with learnings worth preserving

When to Consult Archives

Before debugging infrastructure, deploy, or CI issues
Before repeating a process done in a past session
When encountering an error that may have been solved before

Search: grep -ri "keyword" .archive/ Index: .archive/MEMORY.md

Archive Workflow

Read .archive/MEMORY.md — check for related existing archives
Create directory if needed

Verwandte Skills

Schnellinstallation

Archive

npx skills add ReScienceLab/opc-skills

Skill herunterladen Repository öffnen

Autor: ReScienceLab
Sterne: 788
Aktualisiert: 13.03.2026
Beruf

Auf dieser Seite

01Archive Skill

.archive/YYYY-MM-DD/

Write markdown file with YAML frontmatter (see references/TEMPLATE.md)

Update .archive/MEMORY.md: add one-line entry under the right category

If related archives exist, add related field in frontmatter

Lookup Workflow

Read .archive/MEMORY.md to find relevant entries
Read the specific archive file for detailed context
Apply learnings to current task

Categories

infrastructure — AWS, ECS, IAM, networking, secrets, CloudWatch
release — TestFlight, versioning, Git Flow, CHANGELOG
debugging — Bug fixes, error resolution, gotchas
feature — Feature design, implementation notes
design — UI/UX, icons, visual design

Rules

.archive/ must be in .gitignore — local-only notes
Keep entries concise but reproducible
Focus on problems, fixes, and exact commands
Always update MEMORY.md after creating an archive
Use descriptive filenames (e.g., cloudwatch-logging.md not session.md)
Include YAML frontmatter with tags, category, and optional related

02

When to Archive

03When to Consult Archives

04Archive Workflow

05Lookup Workflow

Sekretäre und Verwaltungsassistenten, außer Recht, Medizin und Geschäftsführung

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Sekretäre und Verwaltungsassistenten, außer Recht, Medizin und Geschäftsführung