# Logseq File Graph Knowledge

> Canonical guidance for Logseq file graphs (Markdown). Use this skill to avoid DB-graph assumptions. Covers tasks (markers), properties (key:: value), and query syntax ({{query ...}} and advanced queries).

- **Type:** Skill
- **Install:** `agentstack add skill-weilong-qin-logseq-skills-logseq-file-graph-knowledge`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Weilong-Qin](https://agentstack.voostack.com/s/weilong-qin)
- **Installs:** 0
- **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Weilong-Qin](https://github.com/Weilong-Qin)
- **Source:** https://github.com/Weilong-Qin/logseq-skills/tree/main/logseq-file-graph-knowledge

## Install

```sh
agentstack add skill-weilong-qin-logseq-skills-logseq-file-graph-knowledge
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Logseq File Graph Knowledge

This skill is the “ground truth” for working with **Logseq file graphs** (the classic graph type backed by Markdown files).

Many assistants confuse Logseq DB graphs with file graphs. When the user is in a **file graph**, use these rules.

## Scope

- Graph type: file-based (Markdown files)
- Primary use case: everyday note-taking, tasks, GTD, dashboards

## Tasks (File Graph)

### Task markers

In file graphs, tasks are ordinary blocks prefixed with a marker keyword.

Common marker sequences:

- `LATER` → `NOW` → `DONE`
- `TODO` → `DOING` → `DONE`

Additional markers that may appear:

- `WAIT` / `WAITING`
- `IN-PROGRESS`
- `CANCELED` / `CANCELLED`

### Creating and cycling markers

- Users can type the marker at the start of the block (e.g., `TODO call Alice`).
- Users can also use the editor command (e.g., `/TODO`).
- Users can cycle markers with `Ctrl/Cmd+Enter`.

### Priority

File graph tasks support priorities:

- `[#A]` (highest), `[#B]`, `[#C]` (lowest)

Example:

```text
- TODO [#A] Finish weekly review
```

### Scheduling and deadlines

In file graphs, scheduling is typically expressed via Logseq’s built-in `SCHEDULED:` and `DEADLINE:` syntax (inserted via `/Scheduled` and `/Deadline`).

Example:

```text
- TODO Submit form
  DEADLINE: 
```

## Properties (File Graph)

### Block properties

Block properties are written as:

```text
key:: value
```

Properties can appear:

- in the same block (inline), or
- in a child block (common for metadata)

### Property naming rules (important)

- Property names are **case-insensitive** and normalized to lowercase.
- Property names with `_` are normalized to `-` (e.g., `done_at` becomes `done-at`).
- Property values cannot contain newlines.

### Values

Property values can include:

- plain text
- page references like `[[Project X]]`
- tags like `#inbox`
- links

To force a value to be treated as plain text (no page refs), wrap it in quotes:

```text
source:: "[[Not a page]]"
```

## Queries (File Graph)

Logseq supports two common query styles.

### Simple query blocks

Use:

```text
{{query ...}}
```

Examples:

```text
{{query (task todo)}}
{{query (and (task todo doing) [[Project X]])}}
{{query (and (task todo) (priority a))}}
{{query (and [[inbox]] (task todo doing))}}
{{query (and (task todo) (not [[inbox]]))}}
```

### Advanced queries

Use an advanced query block when simple query filters are not enough.

General shape:

```text
#+BEGIN_QUERY
{:title "My query"
 :query [:find (pull ?b [*])
        :where
        ...]}
#+END_QUERY
```

## Safe defaults for user-facing workflows

When you are building workflows for file graphs:

- Use markers (`TODO`/`DOING`/`DONE`) for tasks.
- Use child blocks with `key:: value` for metadata.
- Prefer simple `{{query ...}}` blocks for dashboards.
- Do not use DB-graph-only concepts like `#Task` classes, `Status` property tasks, or `{:query ...}`-only conventions.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Weilong-Qin](https://github.com/Weilong-Qin)
- **Source:** [Weilong-Qin/logseq-skills](https://github.com/Weilong-Qin/logseq-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-weilong-qin-logseq-skills-logseq-file-graph-knowledge
- Seller: https://agentstack.voostack.com/s/weilong-qin
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.