logseq

name	logseq
description	Integrate with Logseq PKM - read/write journals, pages, blocks
version	1.0.0
author	Logseq Hermes Integration
license	MIT
platforms	["macos","linux"]
metadata	{"hermes":{"tags":["knowledge-management","productivity","logseq"],"config":[{"key":"logseq.graph_path","description":"Path to your Logseq graph folder","prompt":"Enter the path to your Logseq graph:","default":"~/Documents/logseq","required":true}]}}

Logseq Integration

A Hermes skill for reading from and writing to Logseq personal knowledge management (PKM) graphs. Enables Hermes to expand on notes captured in Logseq — on demand or via scheduled cron jobs.

What This Skill Does

Hermes can interact with your Logseq graph in two ways:

1. Read — Pull information from Logseq files for context
2. Write — Append new content to journals and pages

Use Cases

• Note expansion: Ask Hermes to expand on notes you've already captured in Logseq
• Daily review: Have Hermes read your journal and add insights or tasks
• Knowledge synthesis: Pull content from multiple pages and create summaries
• Scheduled automation: Set up cron jobs to automatically process your Logseq data

Installation

Prerequisites

• Hermes Agent installed
• Logseq graph folder (local directory)

Setup Steps

1. Install the skill:

   skills install logseq
   

2. Configure your graph path when prompted:

   Enter the path to your Logseq graph: ~/Documents/logseq
   

3. Verify installation:

   skills list
   

Directory Structure

Your Logseq graph should contain:

logseq-graph/
├── journals/          # Daily journal files (YYYYMMDD.md)
├── pages/            # Named pages (*.md)

Configuration

Required Config

Key	Description	Default
logseq.graph_path	Path to your Logseq graph	~/Documents/logseq

Optional Cron Config

Key	Description	Example
cron.schedule	Cron expression	0 9 * * *
cron.operation	Operation to run	append_journal
cron.output_destination	Where to write	journal
cron.content	Content template	{{insights}}

Usage

Reading Operations

Read Today's Journal

Read today's journal

Returns: Full content of today's journal file with frontmatter properties and body text.

Read Specific Date

Read journal for 2025-04-24

Date format: YYYY-MM-DD

Read a Page

Read page "Project Notes"

List All Pages

List all pages

Returns: Array of page names in your graph.

Search Pages

Search for "API"

Returns: Matching pages with content snippets showing context.

---

Writing Operations

Append to Today's Journal

Append to journal: Remember to follow up on the API integration

The content is appended as an indented block under the last entry.

Create a New Page

Create page "Meeting Notes"

Creates pages/meeting_notes.md with title:: Meeting Notes frontmatter.

Append to Existing Page

Append to page "Project Notes": Next steps are to test the integration

---

Automation (Cron)

Configuration

Add to config.yaml:

cron:
  schedule: "0 9 * * *"
  operation: append_journal
  output_destination: journal
  content: "Daily insight: {{summary}}"

Cron Expression Format

┌───────────── minute (0-59)
│ ┌─────────── hour (0-23)
│ │ ┌───────── day of month (1-31)
│ │ │ ┌─────── month (1-12)
│ │ │ │ ┌───── day of week (0-6)
* * * * *

Examples:

• 0 9 * * * — Daily at 9:00 AM
• 0 8 * * 1-5 — Weekdays at 8:00 AM
• 0 */2 * * * — Every 2 hours

---

Error Handling

Common Errors

Error	Cause	Solution
Graph path not found	Invalid path	Verify logseq.graph_path points to valid directory
Journal not found	Date doesn't exist	Try a different date or create first
Page not found	Page doesn't exist	Create the page first or check spelling
Permission denied	Can't write to directory	Check file permissions

Failure Modes

• File not found: Returns error with suggestion
• Invalid path: Validation error with correction hint
• Disk full: Error logged, run skipped
• Logseq unavailable: Error logged, cron run skipped

---

File Format Reference

Journal Files

Location: journals/YYYYMMDD.md

Format:

title:: Daily Note
date:: 2026-04-24
public:: false
tags:: [[journal]]

- 9:00 AM :: [[Morning routine]]
  - [ ] Task 1
  - [x] Task 2

Page Files

Location: pages/{slug}.md

Format:

title:: Page Name
tags:: [[tag1]], [[tag2]]
alias:: Alias

 Content starts here...

- First block
  - Nested block

Properties

Logseq uses key:: value format (not YAML frontmatter):

• title:: — Page title
• date:: — Journal date
• tags:: — Tag list
• alias:: — Page aliases

Links

• Page links: [[Page Name]]
• Tags: [[#tag]] or #tag
• Block refs: ((block-uuid))

---

Examples

Example 1: Morning Journal Expansion

User asks: "What's in my journal from this week?"

Hermes:

1. Reads journal files for the past 7 days
2. Extracts key points and tasks
3. Returns synthesized summary

Example 2: Create Note from Conversation

User asks: "Create a note about our API discussion"

Hermes:

1. Creates pages/api_discussion.md
2. Adds frontmatter with title
3. Adds user's content as initial block

Example 3: Daily Scheduled Insights

Cron runs daily at 9am:

1. Reads yesterday's journal
2. Generates insight summary
3. Appends to today's journal

---

Version History

• 1.0.0 — Initial release with read/write/journal/cron support

---

Getting Help

• skills list — Check installed skills
• skills info logseq — View skill details
• Check .planning/ROADMAP.md for feature roadmap