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 Repl

by logseq in logseq/logseq

Start and coordinate Logseq development REPL workflows for the Desktop renderer :app, Electron main-process :electron, and :db-worker-node runtimes through one unified workflow.

AGPL-3.0Auto-check passedKnowledge Management

Install Logseq Repl

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

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

GitHub CLI
$ gh skill install logseq/logseq logseq-repl --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-repl .claude/skills/logseq-repl && 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-repl
GitHub stars
45k
Token cost
~1.6k tokens
SKILL.md length
571 words
Files
8 (incl. scripts)
Skills in repo
12
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Start and coordinate Logseq development REPL workflows for the Desktop renderer :app, Electron main-process :electron, and :db-worker-node runtimes through one unified workflow.

  • Works in 3 steps: shared pnpm watch → Desktop dev app via pnpm dev-electron-app → db-worker-node via node…
  • Knowledge Management work in your project
  • SKILL.md covers Scripts, Standard Flow, Runtime Selection and Readiness Model, plus 6 more sections
  • Runs Shell and Python scripts from its folder; calls pnpm and node

What it does

Logseq Repl is an agent skill from logseq/logseq. Start and coordinate Logseq development REPL workflows for the Desktop renderer :app, Electron main-process :electron, and :db-worker-node runtimes through one unified workflow.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts (for example `scripts/cleanup-repl.sh`, `scripts/common.sh` and `scripts/start-repl.py`).

It sits in Knowledge Management. It works with pnpm. 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

  • Knowledge Management work in your project

Example prompts

  • “/logseq-repl”

Requirements

  • Python 3
  • Node.js
  • A Bash shell

Workflow steps

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

  1. shared pnpm watch
  2. Desktop dev app via pnpm dev-electron-app
  3. db-worker-node via node ./static/db-worker-node.js --repo --root-dir --owner-source cli

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

    Ships 5 files in scripts/ (Shell and Python), which the agent can run.

    Shell commands in SKILL.md call:

    • pnpm
    • node

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    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 Repl loads about 1.6k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 571 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/logseq-repl/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
logseq-repl
description
Start and coordinate Logseq development REPL workflows for the Desktop renderer `:app`, Electron main-process `:electron`, and `:db-worker-node` runtimes through one unified workflow.

Logseq REPL Workflow

Use this skill when the user needs a Logseq development REPL for:

  • Desktop renderer :app
  • Electron main process :electron
  • :db-worker-node
  • any combination of those runtimes

The workflow uses one shared state directory: <repo>/tmp/logseq-repl/.

Scripts

Start everything with the default Logseq data root ($LOGSEQ_CLI_ROOT_DIR or ~/logseq):

bash
<logseq-repl-skill-dir>/scripts/start-repl.sh --repo demo

Start everything with an explicit Logseq data root:

bash
<logseq-repl-skill-dir>/scripts/start-repl.sh --repo demo --root-dir ~/logseq

Clean up everything:

bash
<logseq-repl-skill-dir>/scripts/cleanup-repl.sh

Verify all REPL targets after startup:

bash
<logseq-repl-skill-dir>/scripts/verify-repls.sh

start-repl.sh starts:

  1. shared pnpm watch
  2. Desktop dev app via pnpm dev-electron-app
  3. db-worker-node via node ./static/db-worker-node.js --repo <name> --root-dir <path> --owner-source cli

start-repl.sh is a small shell wrapper around start-repl.py. The Python script verifies that :app, :electron, and :db-worker-node runtimes are live, runs verify-repls.sh to connect to each target REPL and print a small result, then prints attach commands. It does not attach an interactive REPL by itself and exits after verification.

cleanup-repl.sh stops all workflow-managed processes without requiring a target selection. It also removes legacy state files from older split workflows and attempts to stop repo-owned listeners on the standard REPL ports.

verify-repls.sh connects to app, electron, and db-worker-node with pnpm exec shadow-cljs cljs-repl, evaluates one target-specific expression in each REPL, and prints the output.

Standard Flow

Before starting or attaching:

bash
<logseq-repl-skill-dir>/scripts/cleanup-repl.sh

Then start all runtimes:

bash
<logseq-repl-skill-dir>/scripts/start-repl.sh --repo demo

Use --root-dir <path> if the target graph lives outside $LOGSEQ_CLI_ROOT_DIR or ~/logseq.

Attach only to the target you need:

bash
pnpm exec shadow-cljs cljs-repl app
pnpm exec shadow-cljs cljs-repl electron
pnpm exec shadow-cljs cljs-repl db-worker-node

Runtime Selection

  • Need DOM, UI, renderer state, or page rendering? Use :app.
  • Need Electron main process APIs, menus, window lifecycle, or main-process filesystem behavior? Use :electron.
  • Need Node worker behavior or db-worker-node code paths? Use :db-worker-node.

Runtime reminders:

  • :app = Electron renderer
  • :electron = Electron main process
  • :db-worker = browser worker
  • :db-worker-node = Node worker

Readiness Model

Keep these separate:

  1. watch alive: a shadow-cljs server or pnpm watch process exists
  2. build ready: the target build completed successfully
  3. runtime attached: a live JS runtime is connected for :app, :electron, or :db-worker-node

If runtime count is 0, do not attach yet. Fix runtime startup first.

Check runtime counts:

bash
pnpm exec shadow-cljs clj-eval "(do (require '[shadow.cljs.devtools.api :as api]) (println {:app (count (api/repl-runtimes :app)) :electron (count (api/repl-runtimes :electron)) :db-worker-node (count (api/repl-runtimes :db-worker-node))}))"

Interpretation:

  • :app > 0 means a Desktop renderer runtime is attached
  • :electron > 0 means an Electron main-process runtime is attached
  • :db-worker-node > 0 means a worker-node runtime is attached
  • 0 means not ready, even if watch/build logs look healthy
Show full SKILL.md (207 more words)Show less

Logs

Look here first:

  • <repo>/tmp/logseq-repl/shared-shadow-watch.log
  • <repo>/tmp/logseq-repl/desktop-electron.log
  • <repo>/tmp/logseq-repl/db-worker-node.log

Port Audit

After cleanup, verify standard ports if startup still reports conflicts:

bash
lsof -nP -iTCP:8701 -sTCP:LISTEN
lsof -nP -iTCP:3001 -sTCP:LISTEN
lsof -nP -iTCP:3002 -sTCP:LISTEN
lsof -nP -iTCP:9630 -sTCP:LISTEN
lsof -nP -iTCP:9631 -sTCP:LISTEN

Interpretation:

  • no listeners: clean enough to continue
  • listeners after cleanup: resolve the external conflict first
  • listeners only after startup: expected if owned by the workflow

Non-Interactive Verification Examples

Desktop :app:

bash
cat <<'EOF' | pnpm exec shadow-cljs cljs-repl app
(prn {:runtime :app :document? (some? js/document) :title (.-title js/document)})
:cljs/quit
EOF

Electron :electron:

bash
cat <<'EOF' | pnpm exec shadow-cljs cljs-repl electron
(prn {:runtime :electron :process? (some? js/process) :type (.-type js/process)})
:cljs/quit
EOF

db-worker-node:

bash
cat <<'EOF' | pnpm exec shadow-cljs cljs-repl db-worker-node
(prn {:runtime :db-worker-node :process? (some? js/process) :platform (.-platform js/process)})
:cljs/quit
EOF

Editor Attach Helpers

clojure
(shadow.user/cljs-repl)
(shadow.user/electron-repl)
(shadow.user/worker-node-repl)

Troubleshooting

Failure triage order:

  1. inspect tmp/logseq-repl/shared-shadow-watch.log
  2. inspect tmp/logseq-repl/desktop-electron.log
  3. inspect tmp/logseq-repl/db-worker-node.log
  4. inspect standard port listeners with lsof
  5. inspect runtime counts with shadow.cljs.devtools.api/repl-runtimes

Common cases:

  • No available JS runtime: the build may be ready, but the runtime has not connected. Check runtime counts before retrying attach.
  • multiple :app runtimes: close browser dev app instances so only the Desktop renderer remains.
  • ports already in use after cleanup: another Logseq/shadow-cljs dev session is still running.
  • db-worker-node repo mismatch: rerun start-repl.sh --repo <name>; it restarts the worker runtime for the requested repo.

When helping a user connect to a REPL:

  1. identify whether they need :app, :electron, :db-worker-node, or a combination
  2. run cleanup-repl.sh
  3. if standard ports remain occupied, resolve that conflict first
  4. run start-repl.sh --repo <name>
  5. verify runtime counts if attach fails
  6. attach to the matching build or helper
  7. run cleanup-repl.sh when finished

© 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

SKILL.md and 7 other files (scripts) in .agents/skills/logseq-repl of logseq/logseq.

  • SKILL.md
  • scripts/cleanup-repl.sh
  • scripts/common.sh
  • scripts/start-repl.py
  • scripts/start-repl.sh
  • scripts/verify-repls.sh
  • tests/test-lib.sh
  • tests/test-logseq-repl.sh

Open the folder on GitHubat commit 22a29b3

Compare with similar skills

Logseq Repl 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 Repl compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logseq Repl this skilllogseq/logseq45k—~1.6kAutomated safety check: PassAGPL-3.0
Developing Electron DesktopTriliumNext/Trilium38k—~5.7kAutomated safety check: PassAGPL-3.0
Figma Design Knowledge GraphEgonex-AI/Understand-Anything85k—~1kAutomated safety check: PassMIT
Relaunchnaveedharri/baalda153—~870Automated safety check: PassApache-2.0
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

Similar skills

  • Developing Electron Desktop

    TriliumNext/Trilium

    A skill your agent uses when working on the Trilium Electron desktop app (apps/desktop) — adding or changing an electronApi method / IPC channel, touching preload.ts, main.ts, services/window.ts or…

    38k GitHub stars~5.7k tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Figma Design Knowledge Graph

    Egonex-AI/Understand-Anything

    Scans a Figma file through the Figma REST API and builds an interactive knowledge graph of its pages, screens, components and tokens for the design dashboard.

    85k GitHub stars~1k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed

  • Relaunch

    naveedharri/baalda

    Kill the running Baalda desktop (Tauri) dev instance AND the backend server, then launch fresh instances of both.

    153 GitHub stars~870 tokensUpdated today
    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

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

Works with

Categories

Questions about Logseq Repl

What does Logseq Repl do?

Start and coordinate Logseq development REPL workflows for the Desktop renderer :app, Electron main-process :electron, and :db-worker-node runtimes through one unified workflow. Logseq Repl is an agent skill from logseq/logseq. Start and coordinate Logseq development REPL workflows for the Desktop renderer :app, Electron main-process :electron, and :db-worker-node runtimes through one unified workflow.

When should I use Logseq Repl?

Logseq Repl fits situations like: knowledge Management work in your project.

How do I install Logseq Repl in Claude Code?

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

How do I install Logseq Repl in Codex?

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

Can I use Logseq Repl 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-repl -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-repl, .gemini/skills/logseq-repl, .github/skills/logseq-repl and .opencode/skills/logseq-repl in your project.

What does Logseq Repl need to run?

Going by SKILL.md and its folder, Logseq Repl needs a shell and Python for the scripts in its folder and the command-line tools its instructions call (pnpm and node). Our summary lists: Python 3; Node.js; A Bash shell.

Does Logseq Repl 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 Repl 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Logseq Repl use?

Logseq Repl 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 Repl use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 Repl?

Skills that share tags, products or a category with Logseq Repl: Developing Electron Desktop (TriliumNext/Trilium, 38k stars), Figma Design Knowledge Graph (Egonex-AI/Understand-Anything, 85k stars), Relaunch (naveedharri/baalda, 153 stars) and Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logseq Repl?

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.