Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Ctx Journal Normalize | Skills Pool

Skill File

Ctx Journal Normalize

Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.

ActiveMemory43 starsApr 14, 2026

Occupation
Categories: Debugging

Skill Content

Reconstruct journal entries as clean markdown from stripped plain text.

When to Use

After ctx journal site shows rendering issues
When journal entries have fence nesting problems
When metadata blocks render as raw **Key**: value
Before running ctx-journal-enrich (clean markdown improves extraction)

When NOT to Use

On entries already normalized (check .state.json)
When the site renders correctly
On non-journal markdown files

Output Rules

Fences: Always use backtick fences. Innermost code gets 3 backticks. Each nesting level adds 1.
Metadata: **Key**: value blocks become collapsed <details>.
Tool output: Collapse into <details> when > 10 lines.

Related Skills

Quick Install

Ctx Journal Normalize

npx skillvault add ActiveMemory/activememory-ctx-internal-assets-integrations-copilot-cli-skills-ctx-journal-normalize-skill-md

Download Skill Open repository

Author: ActiveMemory
stars: 43
Updated: Apr 14, 2026
Occupation

On this page

Lists: 2-space indent per level.

No invented content: Every word in output traces to input.

Process

Backup first: copy journal directory to .bak sibling
Identify files to normalize (skip already-normalized via .state.json)
Process files turn-by-turn (not whole file at once)
Write back the fixed files
Mark normalized: ctx system mark-journal <filename> normalized
Regenerate site: ctx journal site --build
Report what changed

Quality Checklist

Backup created before modifying
Already-normalized files skipped
No content was invented or lost
State file updated for processed entries

02

When NOT to Use

05Quality Checklist

Word Processors and Typists

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.

Word Processors and Typists