Habilidades connecting-to-logseq
🔗

connecting-to-logseq

Riesgo bajo 🌐 Acceso a red🔑 Variables de entorno⚙️ Comandos externos

Connect Claude to Logseq graphs

Users need to integrate Claude with their Logseq knowledge graphs for querying and writing data. This skill provides automated connection management across HTTP API, CLI, and MCP Server backends with built-in troubleshooting support.

Soporta: Claude Codex Code(CC)
🥉 72 Bronce
1

Descargar el ZIP de la skill

2

Subir en Claude

Ve a Configuración → Capacidades → Skills → Subir skill

3

Activa y empieza a usar

Pruébalo

Usando "connecting-to-logseq". Find all pages tagged with "Books" in my Logseq graph

Resultado esperado:

  • Found 12 pages tagged with "Books":
  • - "Programming Books" - Last modified: Today
  • - "Science Fiction Reading List" - Last modified: Yesterday
  • - "Technical Book Notes" - Last modified: 3 days ago
  • - "Book Recommendations" - Last modified: Last week
  • The query returned pages with :block/tags referencing :db/ident :book tag.

Usando "connecting-to-logseq". Connect me to my Logseq graph

Resultado esperado:

  • Checking available backends...
  • HTTP API: Available at http://127.0.0.1:12315
  • CLI: Installed (version 1.0.0)
  • MCP Server: Ready
  • Selected backend: HTTP API
  • Connection test: SUCCESS
  • Your Logseq graph "My Knowledge Base" is connected and ready.

Auditoría de seguridad

Riesgo bajo
v5 • 1/16/2026

This skill is a legitimate Logseq API client for knowledge graph integration. All network calls go to localhost only (127.0.0.1:12315). Tokens are handled via environment variables using security best practices. Static findings are false positives triggered by documentation examples showing standard API client patterns and Datalog query syntax.

6
Archivos escaneados
1,188
Líneas analizadas
3
hallazgos
5
Auditorías totales

Factores de riesgo

🌐 Acceso a red (3)
SKILL.md:62 references/http-api-guide.md:26-27 references/http-api-guide.md:201-206
🔑 Variables de entorno (2)
SKILL.md:43-47 assets/env.example.json:4-5
⚙️ Comandos externos (2)
references/cli-guide.md:44-52 references/http-api-guide.md:177-187
Auditado por: claude Ver historial de auditorías →

Puntuación de calidad

59
Arquitectura
100
Mantenibilidad
85
Contenido
19
Comunidad
90
Seguridad
91
Cumplimiento de la especificación

Lo que puedes crear

Query your knowledge base

Ask Claude to search your Logseq graph using Datalog queries and retrieve structured information quickly.

Write notes to Logseq

Create new pages, blocks, and properties in your Logseq graph using natural language commands.

Set up CI/CD pipelines

Automate graph exports and validation using the Logseq CLI in continuous integration workflows.

Prueba estos prompts

Basic connection 
Connect me to my Logseq graph at /path/to/my-graph and test the connection.
Query data 
Find all pages in my Logseq graph tagged with "Project" and list their titles.
Write content 
Create a new page called "Meeting Notes" in my Logseq graph with today's date and add a block with my action items.
Troubleshoot 
I am getting "Connection refused" errors when trying to connect to Logseq. Help me diagnose and fix the issue.

Mejores prácticas

  • Store your Logseq API token in environment variables, never in config files or scripts
  • Always verify your Logseq HTTP API is enabled before attempting connections
  • Use absolute paths for graph directories to avoid relative path issues in automation
  • Restart Logseq after changing API settings to ensure changes take effect

Evitar

  • Hardcoding API tokens in configuration files or commit messages
  • Using relative paths for graph directories in automated workflows
  • Attempting connections without verifying Logseq is running
  • Sharing Logseq API tokens in chat messages, commits, or public forums

Preguntas frecuentes

What backends does this skill support?
HTTP API (requires running Logseq), CLI (offline support with limited writes), and MCP Server (Claude-native tools).
Does the skill work with remote Logseq instances?
No. The Logseq HTTP API only listens on localhost. All connections stay on your local machine.
What permissions does this skill need?
Read, Write, Edit for configuration files. Bash, Grep, Glob for script execution and environment detection.
Is my data safe with this skill?
Yes. All API calls stay on localhost. Tokens are handled via environment variables, never stored in plain text.
Why am I getting connection refused errors?
Common causes: Logseq not running, HTTP API not enabled, wrong port (default 12315), or firewall blocking localhost.
How is this different from other data skills?
This skill is specialized for Logseq's unique architecture including Datalog queries, datascript schema, and graph-based storage.

Detalles del desarrollador

Licencia

MIT

Repositorio

https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations/tree/main/logseq-expert/skills/connecting-to-logseq

Ref.

main

Estructura de archivos

📁 assets/

📄 env.example.json

📁 references/

📄 cli-guide.md

📄 http-api-guide.md

📄 troubleshooting.md

📄 SKILL.md