Agent skill · software engineering · aiskillstore
building-logseq-plugins
Expert guidance for building Logseq plugins compatible with the new DB architecture. Auto-invokes when users want to create Logseq plugins, work with the Logseq Plugin API, extend Logseq functionality, or need help with plugin development for DB-based graphs. Covers plugin structure, API usage, and DB-specific considerations.
Why this skill is useful
Adds specific code examples and API usage patterns for Logseq plugin development that are not widely documented.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Building Logseq Plugins When to Use This Skill This skill auto-invokes when: User wants to create a Logseq plugin Questions about the Logseq Plugin API Working with logseq.Editor, logseq.DB, logseq.App namespaces Slash command registration Plugin settings schema definition DB vs MD version compatibility for plugins User mentions "logseq plugin", "logseq extension", "@logseq/libs" You are an expert in Logseq plugin development, with special focus on DB-version compatibility. Plugin Architecture Overview Logseq plugins run in sandboxed iframes and communicate with the main app via the Plugin API. Plugin Structure package.json Manifest Plugin API Basics Initialization Key API Namespaces Namespace Purpose ----------- --------- logseq.Editor Block/page manipulation logseq.DB Database queries logseq.App App-level operations logseq.UI UI components logseq.Settings Plugin settings DB-Version Specific APIs Working with Properties Working with Classes/Tags Enhanced Block Properties APIs (2024+) Datalog Queries in Plugins Basic Query Query with Parameters DB vs MD Query Differences UI Components Slash Commands Block Context Menu Settings Schema DB-Version Compatibility Checklist When building plugins for DB version: [ ] Use :block/title instead of :block/content for page names [ ] Handle structured properties (not just strings) [ ] Support typed property values (numbers, dates, checkboxes) [ ] Use tag-based queries instead of namespace queries [ ] Test with both DB and MD graphs if supporting both [ ] Handle the unified node model (pages ≈ blocks) [ ] Use new block properties APIs when available Common Patterns Feature Detection Property Type Handling Development Workflow 1. Setup: Clone logseq-plugin-template or start fresh 2. Develop: Use npm run dev for hot reload 3. Test: Load unpacked plugin in Logseq 4. Build: npm run build for production 5. Publish: Submit to Logseq Marketplace Loading Development Plugin Resources Logseq Plugin SDK Plugin API Reference Plugin Examples
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/building-logseq-plugins