ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
Best use case
ctx-journal-normalize is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
Teams using ctx-journal-normalize should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-journal-normalize/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-journal-normalize Compares
| Feature / Agent | ctx-journal-normalize | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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 1. **Fences**: Always use backtick fences. Innermost code gets 3 backticks. Each nesting level adds 1. 2. **Metadata**: `**Key**: value` blocks become collapsed `<details>`. 3. **Tool output**: Collapse into `<details>` when > 10 lines. 4. **Lists**: 2-space indent per level. 5. **No invented content**: Every word in output traces to input. ## Process 1. **Backup first**: copy journal directory to `.bak` sibling 2. Identify files to normalize (skip already-normalized via `.state.json`) 3. Process files turn-by-turn (not whole file at once) 4. Write back the fixed files 5. Mark normalized: `ctx system mark-journal <filename> normalized` 6. Regenerate site: `ctx journal site --build` 7. 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
Related Skills
ctx-journal-enrich
Enrich journal entry with metadata. Use when journal entries lack frontmatter, tags, or summary for future reference.
ctx-journal-enrich-all
Full journal pipeline: import unimported sessions, then batch-enrich all unenriched entries. Use when the user says 'process the journal' or to catch up on the backlog.
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.