From 67f2ba6c9ee22ba74e2ff703742e82355780f4ef Mon Sep 17 00:00:00 2001 From: rcmerci Date: Fri, 1 May 2026 20:59:39 +0800 Subject: [PATCH] enhance(skill): update logseq-cli --- .agents/skills/logseq-cli/SKILL.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.agents/skills/logseq-cli/SKILL.md b/.agents/skills/logseq-cli/SKILL.md index 74dfa4d215..4a3de7e334 100644 --- a/.agents/skills/logseq-cli/SKILL.md +++ b/.agents/skills/logseq-cli/SKILL.md @@ -68,6 +68,12 @@ Use `logseq` to inspect and edit graph entities, run Datascript queries, and con - Use `logseq list ...`, `logseq show ...`, or `logseq query ...` first to discover valid ids/uuids. - For graph transfer flows, keep `graph export --file` and `graph import --input` paths consistent. +## Structured block writes + +- When writing multi-item or hierarchical content, prefer a block tree instead of packing everything into one block. +- Preserve the source structure as sibling and child blocks. Each logical bullet, row, or subsection should usually become its own block. +- Reserve `--content` for true single-block writes or targeted updates to one existing block. +- If the user asks to write notes, lists, outlines, imported data, or any content that already has structure, do not flatten it into one long `--content` string. ## Tag association semantics