How do I install the Logseq Format skill?

Run npx skillmds add majiayu000/logseq-format in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Logseq Format safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Logseq Format?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Logseq Format free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Logseq Format?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Logseq Format by majiayu000 — Agent Skill

Name: Logseq Format
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

logseq Format

Format content for logseq, an outliner-based knowledge management tool.

Core Principles

Everything is a bullet: logseq is outliner-first. All content lives in bullet points.
Hierarchy matters: Use indentation (2 spaces or 1 tab per level) to create structure.
Top-level = main ideas: Start with high-level concepts as top-level bullets (no indentation).

Formatting Rules

Top-Level List Structure

- First main topic
  - Sub-point with details
  - Another sub-point
    - Deeper nesting for specifics
- Second main topic
  - Related details
- Third main topic

Markup Syntax

Bold: **text** or __text__
Italic: *text* or _text_
Highlight: ^^highlighted^^
Code inline: `code`
Code block: Triple backticks with language
Links to pages: [[Page Name]]
Tags: #tag or #[[multi word tag]]
Block references: ((block-id))
TODO markers: TODO, DOING, DONE, LATER, NOW

Properties (metadata)

- Main topic
  property-name:: value
  another-property:: another value
  - Content continues here

Example Output

- Project Planning #project
  status:: active
  priority:: high
  - Define **scope** and objectives
    - List all deliverables
    - Set clear timeline with [[Q1 Goals]]
  - Identify stakeholders
    - TODO Schedule kickoff meeting
    - Gather requirements from [[Product Team]]
  - Risk assessment
    - Document potential blockers
    - Create mitigation strategies

Best Practices

Start broad, go deep: Top-level bullets = chapters, nested bullets = details
One idea per bullet: Keep bullets focused and atomic
Use properties sparingly: Add metadata only when it adds value for queries
Link liberally: Connect related concepts with [[page links]]
Indent consistently: Use 2 spaces per indentation level
Frontload importance: Put most important info at the top of each branch

---name: logseq-formatdescription: Use ONLY when user mentions converting/using/writing in "logseq format" or similar (must mention "logseq")--- # logseq Format Format content for logseq, an outliner-based knowledge management tool. ## Core Principles - **Everything is a bullet**: logseq is outliner-first. All content lives in bullet points. - **Hierarchy matters**: Use indentation (2 spaces or 1 tab per level) to create structure. - **Top-level = main ideas**: Start with high-level concepts as top-level bullets (no indentation). ## Formatting Rules ### Top-Level List Structure ```markdown - First main topic - Sub-point with details - Another sub-point - Deeper nesting for specifics - Second main topic - Related details - Third main topic ``` ### Markup Syntax - **Bold**: `**text**` or `__text__` - **Italic**: `*text*` or `_text_` - **Highlight**: `^^highlighted^^` - **Code inline**: `` `code` `` - **Code block**: Triple backticks with language - **Links to pages**: `[[Page Name]]` - **Tags**: `#tag` or `#[[multi word tag]]` - **Block references**: `((block-id))` - **TODO markers**: `TODO`, `DOING`, `DONE`, `LATER`, `NOW` ### Properties (metadata) ```markdown - Main topic property-name:: value another-property:: another value - Content continues here ``` ### Example Output ```markdown - Project Planning #project status:: active priority:: high - Define **scope** and objectives - List all deliverables - Set clear timeline with [[Q1 Goals]] - Identify stakeholders - TODO Schedule kickoff meeting - Gather requirements from [[Product Team]] - Risk assessment - Document potential blockers - Create mitigation strategies ``` ## Best Practices 1. **Start broad, go deep**: Top-level bullets = chapters, nested bullets = details 2. **One idea per bullet**: Keep bullets focused and atomic 3. **Use properties sparingly**: Add metadata only when it adds value for queries 4. **Link liberally**: Connect related concepts with `[[page links]]` 5. **Indent consistently**: Use 2 spaces per indentation level 6. **Frontload importance**: Put most important info at the top of each branch

Frequently asked questions