Skills connecting-to-logseq

📦

connecting-to-logseq

Name: connecting-to-logseq
Author: C0ntr0lledCha0s

v1.0.0 Content revision r2 High Risk 🌐 Network access⚙️ External commands🔑 Env variables

Connect Claude and Codex to Logseq

Connecting an AI assistant to Logseq requires choosing and configuring the correct backend. This skill provides focused setup, request, and troubleshooting guidance.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "connecting-to-logseq" from https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-connecting-to-logseq/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/c0ntr0lledcha0s-connecting-to-logseq.md Signed manifest GET /api/skills/c0ntr0lledcha0s-connecting-to-logseq/manifest Signed lockfile GET /api/skills/c0ntr0lledcha0s-connecting-to-logseq/lockfile

Test it

Using "connecting-to-logseq". Which backend supports offline batch queries?

Expected outcome:

Use the Logseq CLI with a local graph path. It supports offline queries and exports, but write operations are limited.

Using "connecting-to-logseq". My local API returns an authentication error.

Expected outcome:

Confirm that the API is enabled and the token variable is present. Create a new token if needed, without displaying its value.

Using "connecting-to-logseq". Plan a safe MCP connection.

Expected outcome:

Enable the local Logseq API and create a dedicated token.
Build and configure the MCP server only after reviewing its dependencies.
Require confirmation and backup before every write operation.

Security Audit

High Risk

v9 • 7/23/2026 Open versioned report

Most alerts are false positives from Markdown backticks, loopback addresses, documented database names, and targeted environment access. Confirmed issues include unpinned package or script execution and a command that prints the API token. Unsafe write defaults and advice to disable host protections create additional high-risk concerns.

Files scanned

926

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:130-134 assets/env.example.json:15-18

Write safeguards disabled by default

The example configuration disables write confirmation and backups while the documented HTTP and MCP backends support full writes. Unapproved changes could damage graph data.

Both configuration examples explicitly set confirmWrites and backupBeforeWrite to false. The backend table states that HTTP and MCP provide full write access.

High

references/troubleshooting.md:218-225

Troubleshooting weakens host protections

The guide recommends elevated execution and temporarily disabling antivirus for a connection error. These steps expand privileges and reduce endpoint protection without scoped safeguards.

The instructions explicitly recommend running Logseq as Administrator and disabling antivirus. No restoration step or narrower diagnostic alternative accompanies the advice.

Capability review items (8)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

SKILL.md:157-161

Ruby/shell backtick execution

3. **Environment variable**: Check `echo $LOGSEQ_API_TOKEN`

The troubleshooting instruction prints LOGSEQ_API_TOKEN directly. Terminal or assistant logs could retain a credential that permits graph access.

Medium

SKILL.md:52-54

Ruby/shell backtick execution

```bash

The setup guidance directs execution of a local Python script that is absent from the audited files. Its behavior cannot be verified here.

Medium

SKILL.md:86-88

Ruby/shell backtick execution

```bash

The cited command installs an unpinned npm package globally. Package lifecycle code can execute and modify the host environment.

Medium

SKILL.md:106-110

Ruby/shell backtick execution

```bash

The instructions run npm install and build scripts for an unaudited MCP server. Dependency lifecycle and build scripts can execute arbitrary code.

Medium

SKILL.md:161-162

Ruby/shell backtick execution

1. **Install globally**: `npm install -g @logseq/cli`

The instruction performs a global installation of an unpinned npm package. This changes the host and executes package installation logic.

Medium

SKILL.md:162-167

Ruby/shell backtick execution

2. **Or use npx**: `npx @logseq/cli --help`

The npx command can download and execute the current unpinned package release. No version pin or confirmation requirement is provided.

Medium

SKILL.md:167-175

Ruby/shell backtick execution

1. **Build server**: `cd servers/logseq-mcp && npm run build`

The instruction executes an npm build script from an MCP server outside the audited files. The invoked script cannot be verified here.

Medium

SKILL.md:181-183

Ruby/shell backtick execution

```bash

The command runs a Python setup wizard that is absent from the audited files. Its filesystem and environment effects cannot be verified.

Risk Factors

🌐 Network access (26)

⚙️ External commands (40)

🔑 Env variables (2)

references/http-api-guide.md:161 references/http-api-guide.md:161

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/c0ntr0lledcha0s-connecting-to-logseq/security.svg)](https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-connecting-to-logseq/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-connecting-to-logseq.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

C0ntr0lledCha0s. (2026). connecting-to-logseq security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq/audits/9

BibTeX citation

@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-connecting-to-logseq-2026,
  author = {C0ntr0lledCha0s},
  title = {connecting-to-logseq security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq/audits/9},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "connecting-to-logseq security audit report (audit version 9)"
version: "1.0.0"
type: report
authors:
  - name: "C0ntr0lledCha0s"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-connecting-to-logseq/audits/9"
identifiers:
  - type: other
    value: "skillstore:c0ntr0lledcha0s-connecting-to-logseq:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Connect a personal graph

Set up a local HTTP connection for reading and updating a personal Logseq graph.

Automate graph queries

Choose CLI commands for offline queries, exports, validation, or continuous integration.

Repair an integration

Trace authentication, port, graph path, query, or MCP startup failures.

Try These Prompts

Choose a backend

Recommend a Logseq backend for my needs. I need [read or write access], and Logseq is [running or offline].

Set up local HTTP access

Guide me through enabling Logseq HTTP access and storing the API token without printing or committing it.

Diagnose a connection

Diagnose this Logseq connection error: [error]. Ask before running commands and do not reveal credentials.

Design an automated workflow

Plan a Logseq automation for [goal] using [CLI, HTTP, or MCP]. Include permissions, backups, confirmations, and failure recovery.

Best Practices

Keep the API bound to localhost and never expose its port publicly.
Store tokens in environment variables and test only whether each variable exists.
Require confirmation and a current backup before modifying graph data.

Avoid

Do not print API tokens in terminal output or assistant transcripts.
Do not disable antivirus or run Logseq with elevated privileges for routine troubleshooting.
Do not execute unpinned packages or unaudited setup scripts automatically.