Merge/dedupe and restructure pages in the user's local Logseq graph — combine duplicate topic pages (rewriting inbound links), split overgrown pages, promote journal content into topic pages. Use when the user asks to merge, dedupe, reorganize, restructure, or consolidate Logseq pages.
Answer questions from the user's local Logseq graph — search pages and journals, follow backlinks, surface TODOs and tagged content. Read-only. Use when the user asks "what do my notes say about…", "find in my Logseq", "which pages link to…", or similar.
OpenAPI workflow toolkit: locate and record the project's OpenAPI and Arazzo specs (init), and generate an Arazzo 1.0 workflow spec from the confirmed customer-journeys doc mapped onto real operations (arazzo). Prose-driven with human gates; validators used when installed.
Generate an Arazzo workflow spec (arazzo.yaml) from the confirmed customer-journeys doc, mapping each journey's steps onto real operations in the project's OpenAPI spec. Use when asked to create an Arazzo spec, generate API workflow descriptions, or turn journeys into executable workflow definitions.
Project discovery toolkit: identify what a codebase is built with (stack), what its documentation says it must do (docs), how it deploys and what it depends on (topology), and what workflows its users actually perform (journeys). Read-only; emits versioned JSON contracts for downstream consumers.
Read a project's documentary record — PRDs, requirements documents, specifications, design docs, ADRs, wiki pages — and extract the requirements, user-workflow evidence, domain vocabulary, and invariants it states. Use when profiling an unfamiliar project, gathering requirements, or establishing what a system was…
Identify the key workflows users actually perform with a system, mined from documentation evidence, routes, CLI commands, and UI entry points, ranked by business criticality with dependency edges between them. Use when profiling an unfamiliar project for test design, documentation, or product understanding. Emits the…
Identify what a codebase is built with — languages, runtimes, package managers, build commands, and monorepo layout. Use when profiling an unfamiliar project, before test design, dependency work, or onboarding documentation. Emits the profile:stack contract.
Determine how a system deploys and what it depends on — components, real dependencies, third-party services, configuration, startup order, and how hard each component is to stand up. Read-only. Use when profiling an unfamiliar project for test design, deployment documentation, or onboarding. Emits the profile:topology…
Security toolkit: vet plugins/skills before install (vet-plugin) and audit code for race conditions and concurrency bugs (race-cond). Use before installing third-party agent extensions or when reviewing concurrent code.
Systematic identification of race conditions, concurrency bugs, and thread-safety issues across codebases. Use when asked to find race conditions, audit concurrent code, debug non-deterministic behavior, review thread safety, find data races, or analyze async/parallel code. Supports TypeScript, JavaScript, Python, Go…
Security-first plugin vetting for AI agents. Use before installing any plugin (skill, plugin, command, etc.) from any Marketplace, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.