Skills reading-logseq-data

📦

reading-logseq-data

Name: reading-logseq-data
Author: C0ntr0lledCha0s

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

Read Logseq Graph Data

Logseq users often need reliable access to pages, blocks, properties, and relationships without hand-writing every query. This skill gives Claude, Codex, and Claude Code structured helpers for reading local Logseq graph data.

Supports: Claude Codex Code(CC)

📊 73 Adequate

Install with my Agent

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

Agent request

Review the Skillstore skill "reading-logseq-data" from https://skillstore.io/skills/c0ntr0lledcha0s-reading-logseq-data.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-reading-logseq-data/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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-reading-logseq-data.md Signed manifest GET /api/skills/c0ntr0lledcha0s-reading-logseq-data/manifest Signed lockfile GET /api/skills/c0ntr0lledcha0s-reading-logseq-data/lockfile

Test it

Using "reading-logseq-data". Get the Logseq page "Project Alpha".

Expected outcome:

A concise page summary with properties, top-level blocks, and any missing page notice.

Using "reading-logseq-data". Find backlinks to "Hiring Plan".

Expected outcome:

Referencing page names
Matched block excerpts
Counts grouped by page

Using "reading-logseq-data". List books rated at least 4 stars.

Expected outcome:

A table-style summary of matching book titles, authors, and ratings when those properties exist.

Security Audit

Medium Risk

v11 • 7/9/2026 Open versioned report

Static command, network, environment, and reconnaissance matches were mostly false positives from documented local Logseq API and CLI access. Two semantic risks remain: bearer tokens can be sent to a configurable API URL, and CLI search fallback builds Datalog with unescaped search text.

Files scanned

1,219

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

Medium

scripts/logseq-client.py:80-82 scripts/logseq-client.py:102-112 scripts/logseq-client.py:166-172

Configurable API Endpoint Can Receive Bearer Token

The client reads LOGSEQ_API_URL or .claude/logseq-expert/env.json and sends the bearer token to the configured URL. This supports custom deployments, but a malicious or mistaken configuration could disclose the Logseq API token to a non-local endpoint.

The code clearly combines configurable URLs with Authorization header transmission. The risk depends on user configuration, so confidence is high for the behavior but medium for exploitability.

Medium

scripts/logseq-client.py:335-340

Unescaped Search Text in Datalog Fallback

The CLI search fallback interpolates query_text directly into a Datalog string. A crafted search term containing quotes or Datalog syntax could alter the query or cause unexpected graph reads when CLI fallback is used.

The interpolation is direct and not parameterized. The impact is limited to local Logseq query behavior, but the injection pattern is concrete.

Risk Factors

⚙️ External commands (41)

🌐 Network access (10)

scripts/logseq-client.py:19 scripts/logseq-client.py:166 scripts/logseq-client.py:176 scripts/logseq-client.py:76 scripts/logseq-client.py:80 scripts/logseq-client.py:103 scripts/logseq-client.py:76 scripts/logseq-client.py:80 scripts/logseq-client.py:103 SKILL.md:156

🔑 Env variables (9)

scripts/logseq-client.py:80 scripts/logseq-client.py:81 scripts/logseq-client.py:82 scripts/logseq-client.py:110 scripts/logseq-client.py:102 scripts/logseq-client.py:104 scripts/logseq-client.py:106 scripts/logseq-client.py:115 scripts/logseq-client.py:117

Audited by: claude 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-reading-logseq-data/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-reading-logseq-data.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). reading-logseq-data security audit report (audit version 11) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-reading-logseq-data/audits/11

BibTeX citation

@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-reading-logseq-data-2026,
  author = {C0ntr0lledCha0s},
  title = {reading-logseq-data security audit report (audit version 11)},
  institution = {Skillstore},
  year = {2026},
  number = {11},
  url = {https://skillstore.io/skills/c0ntr0lledcha0s-reading-logseq-data/audits/11},
  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: "reading-logseq-data security audit report (audit version 11)"
version: "1.0.0"
type: report
authors:
  - name: "C0ntr0lledCha0s"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-reading-logseq-data/audits/11"
identifiers:
  - type: other
    value: "skillstore:c0ntr0lledcha0s-reading-logseq-data:audit:11"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Inspect research notes

Find pages, backlinks, and related blocks before summarizing a research topic.

Build graph reports

Run Datalog queries to list tasks, tagged items, ratings, or other structured Logseq data.

Support local automation

Use Claude Code to retrieve Logseq data through a reusable Python client in scripts.

Try These Prompts

Fetch a page

Use the Logseq reading skill to get the page named "Project Alpha" and summarize its blocks.

Find backlinks

Use Logseq to find backlinks to "Quarterly Planning" and group the results by source page.

Query tagged items

Run a Logseq Datalog query that finds all blocks tagged "Book" with a rating of 4 or higher.

Audit task metadata

Read my Logseq graph and list tasks with status "In Progress", including deadlines and parent pages when available.

Best Practices

Keep the Logseq API bound to localhost unless remote access is required.
Use parameterized Datalog queries for user-supplied values.
Request only the fields needed to keep graph reads fast and private.

Avoid

Do not paste sensitive graph exports into prompts when local API access is enough.
Do not use broad pull-all queries for large graphs without a limit.
Do not configure API tokens for remote URLs you do not control.