Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Process Journal Zettels

ASecurity

Takes a journal entry, analyzes linked pages, and generates any missing or empty zettels using synthesize_knowledge process

8 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgodatabaseperformancedocumentation

Works with

mcp

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add tstapler/dotfiles --skill process_journal_zettels --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Process Journal Zettels?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Process Journal Zettels
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-process-journal-zettels-dotfiles/badge)](https://www.skillsdirectory.com/skills/tstapler-process-journal-zettels-dotfiles)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
description: Takes a journal entry, analyzes linked pages, and generates any missing or empty zettels using synthesize_knowledge process
---

# Journal Entry Zettel Processing

I'll analyze a journal entry, check all linked pages, and generate comprehensive zettels for any missing or empty pages using the same systematic approach as the synthesize_knowledge command.

## Process Overview

### Phase 1: Journal Entry Analysis
I'll examine the specified journal entry to:
- **Process [[Needs Processing]] tags**: Specifically look for this tag and recursively process all child bullet points and nested content to ensure full context is captured for synthesis.
- Extract all page links `[[Page Name]]` and references
- **Identify implicit topics and concepts** mentioned in the text that could benefit from dedicated zettels
- **Analyze key terms, technical concepts, and domain-specific terminology** that appear significant
- **Detect emerging themes, patterns, or repeated concepts** across the journal entry
- **Identify proper nouns, methodologies, frameworks, or tools** mentioned that warrant documentation
- **Spot decision points, insights, or conclusions** that could become standalone knowledge pages
- Note any incomplete thoughts or areas needing expansion
- Understand the context and connections being made
- Focus particularly on: ${2:-[any specified focus topic]}

### Phase 2: Comprehensive Topic Assessment
For both explicit links and identified implicit topics, I'll:
- **Explicit Links**: Check if pages exist in `~/Documents/personal-wiki/logseq/pages/`
- **Implicit Topics**: Determine which concepts warrant dedicated zettel pages
- **Content Evaluation**: Assess existing pages for completeness (empty, minimal, or incomplete)
- **Priority Assessment**: Rank topics by importance, frequency of mention, and knowledge value
- **Gap Analysis**: Identify missing connections and knowledge gaps
- **Conceptual Mapping**: Map relationships between all identified concepts (explicit and implicit)
- **Zettel Candidacy**: Evaluate which implicit topics would add most value as standalone pages

### Phase 3: Content Generation Strategy
Using the synthesize_knowledge approach, I'll:
- **mcp__brave-search__brave_web_search**: Research each missing/incomplete topic for authoritative sources
- **mcp__stapler-mcp__read_website**: Extract detailed information from relevant sources
- **WebFetch**: Gather additional context and perspectives
- Plan comprehensive zettel structure for each missing page
- Design linking strategy that connects to existing knowledge

### Phase 4: Zettel Creation
For each missing, incomplete, or newly identified topic, I'll:
- **Create comprehensive Zettelkasten-formatted content** for both explicit links and implicit topics
- **Follow your CLAUDE.md guidelines and conventions** for all generated content
- **Include proper cross-references and bidirectional links** connecting new pages to existing knowledge
- **Add semantic tags for discoverability** (#concepts, #tools, #methodologies, etc.)
- **Create concept hierarchies** where implicit topics relate to broader themes
- **Establish connection pathways** between journal insights and broader knowledge domains
- **Ensure content integrates with existing knowledge base** and enhances the overall network
- **Save directly to `~/Documents/personal-wiki/logseq/pages/` when possible**

### Phase 5: Integration and Linking
Finally, I'll:
- Update the original journal entry with enhanced links if needed
- Create supporting concept pages where beneficial
- Establish meaningful connections between new and existing content
- Ensure all references are properly formatted and functional
- Verify the knowledge network adds value

## Usage Examples

**Basic usage:**
`/process_journal_zettels 2025_09_08`

**With focus topic:**
`/process_journal_zettels 2025_09_08 "database performance"`

**Specific date format:**
`/process_journal_zettels "Sep 8th, 2025" "system architecture"`

## Implementation Process

### Step 1: Journal Entry Location
I'll look for the journal entry in:
- `~/Documents/personal-wiki/logseq/journals/${1:-[journal_date]}.md`
- Common date formats: `YYYY_MM_DD.md`, `YYYY-MM-DD.md`
- If not found, I'll search the journals directory for matching dates

### Step 2: Comprehensive Content Analysis
For the journal entry `${1:-[journal_date]}`, I'll:
- **Parse all `[[Page Name]]` references** (explicit links)
- **Recursively process [[Needs Processing]] tags**: For any block tagged with `[[Needs Processing]]`, recursively extract and analyze all child bullet points and nested content to maintain full context.
- **Extract any `#tags` that might need pages**
- **Perform semantic analysis** to identify implicit topics:
  - Technical terms and jargon that appear significant
  - Proper nouns (tools, frameworks, methodologies, people, companies)
  - Decision frameworks or mental models mentioned
  - Insights, conclusions, or "aha moments" worth preserving
  - Recurring themes or concepts that span multiple entries
  - Problem-solution pairs that could become case studies
  - Questions or hypotheses that warrant investigation
- **Note any `TODO` items or incomplete thoughts**
- **Analyze writing patterns** to detect concepts the author finds important
- **Identify cross-cutting concerns** that appear across different contexts

### Step 3: Research and Content Generation
For each missing/incomplete page AND newly identified implicit topics, I'll apply the full synthesize_knowledge process:
- **Research topics comprehensively** using available MCP tools (including all content recursively extracted from `[[Needs Processing]]` blocks)
- **Analyze multiple authoritative sources** to build robust understanding
- **Synthesize information into coherent, valuable content** that serves long-term knowledge goals
- **Structure content for maximum knowledge network value** with proper interconnections
- **Prioritize high-value implicit topics** that frequently appear or connect to multiple domains
- **Create foundational pages** for concepts that enable understanding of other topics

### Step 4: File Creation and Integration
- **Primary**: Save directly to `~/Documents/personal-wiki/logseq/pages/[Page Name].md`
- **Fallback**: Provide markdown content in code blocks with intended file paths
- Ensure all content follows Logseq/Zettelkasten best practices
- Create meaningful connections to existing knowledge

## Expected Outcomes

This command will:
- **Transform incomplete journal references into comprehensive knowledge pages**
- **Surface and formalize implicit knowledge** from journal writing into structured zettels
- **Create a robust network of interconnected concepts** linking explicit and implicit topics
- **Fill knowledge gaps identified in your journaling** through both obvious and subtle patterns
- **Enhance the value of your personal knowledge system** by capturing tacit insights
- **Provide research-backed content for topics you're exploring** including concepts you mention but haven't formally documented
- **Build conceptual bridges** between disparate ideas mentioned in journal entries
- **Preserve intellectual breadcrumbs** that might otherwise be lost in stream-of-consciousness writing

## Quality Standards

All generated zettels will:
- Include authoritative source information and references
- Follow proper Zettelkasten linking conventions
- Integrate seamlessly with existing knowledge base
- Provide actionable insights and clear explanations
- Include appropriate tags and cross-references
- Be structured for long-term knowledge value

The goal is to transform your journal entries from simple notes into comprehensive knowledge resources that become more valuable over time through their connections and research-backed content.

Usage: `/process_journal_zettels [journal_date] [optional_focus_topic]`

Attribution

tstaplertstapler
View sourceMore from tstapler →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →