Logseq graph toolkit for a local classic (file-based) graph: capture notes/TODOs into journals or pages (capture), answer questions from the graph (query), find consistency problems (lint), merge/dedupe and restructure pages (organize), and import notes from an Obsidian vault (from-obsidian). Hybrid file/HTTP-API access with automatic graph discovery.
Plugin logseq from marketplace efitz-skills in ericfitz/skills. Commands read from the repo's manifest — 8 days ago.
captureCapture a note, TODO, or meeting summary into the user's local Logseq graph — today's journal by default, or a named page. Use when the user says "add this to Logseq", "log this in my journal", "note this down in Logseq", or wants a TODO captured.
from-obsidianConvert and import notes from a local Obsidian vault into the user's Logseq graph — a single note, a folder, or the whole vault. Repeatable; already-imported unchanged notes are skipped. Use when the user asks to transfer, migrate, or import Obsidian notes into Logseq.
lintFind consistency problems in the user's local Logseq graph — broken links, case-conflicting link spellings, orphan pages, near-duplicate page names, unparseable pages — and apply chosen fixes. Use when the user asks to lint, clean up, or check their Logseq graph for consistency.
organizeMerge/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.
queryAnswer 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.
Dependency discovery toolkit: enumerate what a system depends on across six categories — packages, out-of-project services, configuration, secrets and permissions, OS and cloud resources, and network paths — each with the failure-relevant declarations (timeout, retry, fallback, health check) found for it. Static and read-only; emits a versioned JSON contract consumed by downstream analysis.
8 skills
Localization/i18n toolkit: analyze missing keys, measure coverage, detect non-localizable strings, translate, validate translations, update JSON locale files, and backfill every locale. Use for i18n auditing, translation, and locale-file maintenance.
7 skills
Portable CATS API fuzzing toolkit: bootstrap per-repo config (init), run fuzz campaigns through config-declared shell hooks (run), query and render results from SQLite (report), triage true positives into a remediation plan (analyze), and manage declarative false-positive rules (fp). Repo-specific setup lives in .local/cats/config.yaml; false-positive rules live in a committed YAML file.
5 skills · 1 agent
Developer toolkit (sem-powered): annotate code with durable SEM@<sha> intent markers (sem-annotate), keep them maintained via a project convention (sem-auto), and find dead code + duplication and produce a ranked plan (dedupe). Uses the sem CLI entity graph. Supports Go, TypeScript/JavaScript, and Python.
3 skills · 3 agents
Project discovery toolkit: identify what a codebase is built with (stack), what its requirements documents, PRDs, specs, and wiki pages say it must do (docs), how it deploys and what it depends on (topology), and what workflows its users actually perform (journeys). Read-only inference backed by a deterministic inventory script; emits versioned JSON contracts consumed by other plugins.
5 skills
Integration test design toolkit: discover a project's test conventions and how integration tests are separated (conventions), assess the quality of existing tests for over-mocking and misleading coverage (critique), find state-establishment and teardown affordances (state), and synthesize a prioritized scenario plan from confirmed customer journeys and documented requirements (design). Reports conflicts between what the documentation requires and what the code does. Read-only discovery; requires the profile plugin.
4 skills
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.