New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Logseq Debug Workflow

by logseq in logseq/logseq

Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps.

AGPL-3.0Auto-check passedKnowledge Management

Install Logseq Debug Workflow

skills CLI
$ npx skills add logseq/logseq --skill logseq-debug-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install logseq/logseq logseq-debug-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/logseq/logseq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/logseq-debug-workflow .claude/skills/logseq-debug-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
logseq-debug-workflow
GitHub stars
45k
Token cost
~1k tokens
SKILL.md length
551 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps.

  • Works in 7 steps: Choose the correct runtime repl and say… → Reproduce the bug in runtime REPL before… → Capture concrete evidence from that… → …
  • Tasks that involve Debugging
  • SKILL.md covers Core rule, Do not conclude early, Debugging tools and Required final output, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Logseq Debug Workflow is an agent skill from logseq/logseq. Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Debugging. The repository describes itself as: A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: https://logseq.io/p/NX4mcggEV. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Debugging

Example prompts

  • “/logseq-debug-workflow”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Choose the correct runtime repl and say why
  2. Reproduce the bug in runtime REPL before editing code.
  3. Capture concrete evidence from that runtime: REPL output, CLI output, logs, or a failing test that matches the real runtime path.
  4. Check relevant logs early.
  5. Apply the smallest justified fix.
  6. Re-run the same reproduction flow after the fix and capture evidence again.
  7. Include restart/reload/reopen verification when the bug involves settings, startup, persistence, window creation, or cross-process behavior.

What it can do on your machine

Read from SKILL.md and the folder at commit 22a29b3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Logseq Debug Workflow loads about 1k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 551 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from logseq/logseq at commit 22a29b3, republished under its AGPL-3.0 licence (© logseq). 551 words, ~1,046 tokens.

Download SKILL.mdSave it as .claude/skills/logseq-debug-workflow/SKILL.md (or your agent's skills folder).
name
logseq-debug-workflow
description
Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps.

Logseq Debug Workflow

Use for any Logseq bug investigation.

Core rule

Treat this as a debugging workflow, not a code-only change.

Before claiming a fix, you must:

  1. Choose the correct runtime repl and say why:
    • :app for renderer, DOM, UI, frontend state
    • :electron for main-process, BrowserWindow, IPC, app config
    • :db-worker-node for worker DB behavior, worker IPC, queries, transactions
    • CLI for logseq command behavior
  2. Reproduce the bug in runtime REPL before editing code.
  3. Capture concrete evidence from that runtime: REPL output, CLI output, logs, or a failing test that matches the real runtime path.
  4. Check relevant logs early.
  5. Apply the smallest justified fix.
  6. Re-run the same reproduction flow after the fix and capture evidence again.
  7. Include restart/reload/reopen verification when the bug involves settings, startup, persistence, window creation, or cross-process behavior.

Do not conclude early

Do not say the bug is fixed if any of these is missing:

  • pre-fix reproduction evidence
  • relevant log evidence, or an explicit statement that checked logs had nothing useful
  • post-fix evidence from the same runtime/path
  • required end-to-end lifecycle verification

Unit tests alone are not enough when this skill applies, unless the bug is truly unit-level and you explicitly justify that.

If the environment blocks full verification, report:

  • the blocker
  • what you tried
  • which evidence is still missing
  • the strongest partial evidence you have

Debugging tools

General
  • Add labeled prn checkpoints when helpful.
  • Use small REPL/eval checks.
  • Use targeted tests to confirm behavior.
  • Inspect only relevant inputs, branches, transformed values, outputs, and errors.
  • For async flows, inspect both sides of the async boundary.
Logseq REPL

check logseq-repl skill.

When running under Codex, using the REPL is not enough for :app verification. Also use the chrome skill, open the :app target in the browser, and verify the behavior there.

Logs

Logs are evidence. Check them early for Electron, CLI, worker, IPC, async, or persistence issues.

Common locations:

  • tmp/desktop-app-repl/desktop-electron.log (logseq-repl skill)
  • tmp/logseq-repl/shared-shadow-watch.log (logseq-repl skill)
  • ~/Library/Logs/Logseq/main.log
  • ~/Library/Logs/Logseq/main.old.log
  • ~/Library/Application Support/Logseq/configs.edn
  • graph-local db-worker-node-<timestamp>.log
Show full SKILL.md (224 more words)Show less
Logseq CLI

Before using logseq, load logseq-cli skill.

Required final output

The final response must include these sections or an equivalent structure:

  1. Runtime chosen — which runtime REPL you used and why
  2. Pre-fix reproduction — reproduce bug in runtime REPL, exact steps and evidence
  3. Root cause — concrete cause and relevant files/flow
  4. Fix applied — short description of the change
  5. Post-fix verification — same steps again with new evidence
  6. Additional verification — tests/checks run, and what was not verified
  7. Gaps or blockers — any missing evidence and why

Quick checklist

Before ending, make sure the answer is yes to all:

  • Did I reproduce the bug before fixing it?
  • Did I show evidence, not just claim reproduction?
  • Did I inspect relevant logs?
  • Did I verify in the correct runtime?
  • Did I rerun the same scenario after the fix?
  • Did I include both before and after evidence in the final output?
  • Did I avoid claiming completion if required evidence is missing?

Verification reminders

  • Never run tests, lint, build, or E2E verification in the background.
  • Check logs before trusting REPL/CLI output alone.
  • For performance bugs, compare --profile before/after on the same graph and command.
  • For CLI bugs, reuse the same --graph, --data-dir, and output mode.
  • For REPL debugging, verify against the intended runtime, not a stale one.

Common checks: bb dev:test -v <namespace/testcase-name>, bb dev:lint-and-test, bb dev:cli-e2e.

© logseq, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/logseq-debug-workflow of logseq/logseq.

Open the folder on GitHubat commit 22a29b3

Compare with similar skills

Logseq Debug Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Logseq Debug Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logseq Debug Workflow this skilllogseq/logseq45k—~1kAutomated safety check: PassAGPL-3.0
Self LearnPratiyush/llm-wiki395—~1.6kAutomated safety check: PassMIT
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone
Obsidian CLIAtmosphere/atmosphere3.8k13 repos~795Automated safety check: PassApache-2.0
Karpathy LLM WikiAstro-Han/karpathy-llm-wiki2.4k—~3.6kAutomated safety check: PassMIT
Zlibrary To Notebooklmzstmfhy/zlibrary-to-notebooklm1.7k1 repos~968Automated safety check: PassMIT

Similar skills

  • Self Learn

    Pratiyush/llm-wiki

    Extract reusable patterns from recent sessions, propose framework improvements, and (with approval) update the framework docs.

    395 GitHub stars~1.6k tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed

  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed

  • Obsidian CLI

    Atmosphere/atmosphere

    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.

    3.8k GitHub starsUsed in 13 repos~795 tokens
    Knowledge ManagementAuto-check passed

  • Karpathy LLM Wiki

    Astro-Han/karpathy-llm-wiki

    A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.

    2.4k GitHub stars~3.6k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed

  • Zlibrary To Notebooklm

    zstmfhy/zlibrary-to-notebooklm

    自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式，自动转换，一键创建知识库。

    1.7k GitHub starsUsed in 1 repo~968 tokens
    Knowledge ManagementAuto-check passed

  • Multi-Source to NotebookLM Processor

    joeseesun/qiaomu-anything-to-notebooklm

    Collects content from WeChat articles, web pages, YouTube, podcasts, documents and more, uploads it to NotebookLM and generates podcasts, slides or mind maps.

    6.2k GitHub stars~3.6k tokensUpdated 2 days ago
    Knowledge ManagementAuto-check passed

More from logseq/logseq

All 12 skills in this repo

  • Logseq Review Workflow Eval

    logseq/logseq

    Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Logseq Plugin SDK

    logseq/logseq

    Build, debug, or review Logseq plugins with the @logseq/libs SDK (TypeScript/JavaScript, iframe/shadow sandboxed).

    45k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Logseq CLI

    logseq/logseq

    Operate the current Logseq command-line interface to inspect or modify graphs, pages, blocks, tasks, tags, and properties; run Datascript queries; show page/block trees; manage graphs; and manage…

    45k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Logseq Dependency Upgrade

    logseq/logseq

    Audit, plan, and refresh dependency upgrades for the Logseq repository by scanning every non-gitignored package.json, deps.edn, bb.edn and nbb.edn manifest, checking latest upstream versions…

    45k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Logseq I18n

    logseq/logseq

    Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings.

    45k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Logseq Debug Workflow

What does Logseq Debug Workflow do?

Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps. Logseq Debug Workflow is an agent skill from logseq/logseq. Debug Logseq bugs with the right runtime, concrete before/after evidence, and end-to-end reproduction steps.

When should I use Logseq Debug Workflow?

Logseq Debug Workflow fits situations like: tasks that involve Debugging.

How do I install Logseq Debug Workflow in Claude Code?

Run `npx skills add logseq/logseq --skill logseq-debug-workflow -a claude-code`. Or copy the skill folder (.agents/skills/logseq-debug-workflow in logseq/logseq) into .claude/skills/logseq-debug-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Logseq Debug Workflow in Codex?

Run `npx skills add logseq/logseq --skill logseq-debug-workflow -a codex`. Or copy the skill folder (.agents/skills/logseq-debug-workflow in logseq/logseq) into .agents/skills/logseq-debug-workflow in your project. Codex loads it when a task matches its description.

Can I use Logseq Debug Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add logseq/logseq --skill logseq-debug-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logseq-debug-workflow, .gemini/skills/logseq-debug-workflow, .github/skills/logseq-debug-workflow and .opencode/skills/logseq-debug-workflow in your project.

What does Logseq Debug Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Logseq Debug Workflow is instructions for the agent only.

Does Logseq Debug Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Logseq Debug Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Logseq Debug Workflow use?

Logseq Debug Workflow is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Logseq Debug Workflow use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Logseq Debug Workflow?

Skills that share tags, products or a category with Logseq Debug Workflow: Self Learn (Pratiyush/llm-wiki, 395 stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Karpathy LLM Wiki (Astro-Han/karpathy-llm-wiki, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logseq Debug Workflow?

logseq (a GitHub organization) maintains it in logseq/logseq, which has 45,158 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: logseq/logseq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.