matryca-plumber

Name: matryca-plumber Review
Item: matryca-plumber
Rating: 3.0
Author: Aaron Matthews

Skill Documents & Content Usable

Works inClaude Code

Usable Scanned — metadata only

Enables teams to maintain semantic consistency and discoverability across Markdown documentation without vendor lock-in or external API dependencies, reducin…

Local-first AI daemon for Logseq OG: background semantic indexing, link hygiene, and agent-ready CLI/MCP — edits Markdown on disk (no cloud, no Logseq API). Karpathy LLM-Wiki inspired.

Ask Claude to automatically index and tag related notes in your Logseq vault for better discoverability.
Generate missing backlinks between markdown documents based on semantic similarity of content.
Automate cleanup of broken or orphaned links across your entire local knowledge base.

82 starsApache-2.0 (commercial OK)FreeQuick setup

Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Why it matters

Enables teams to maintain semantic consistency and discoverability across Markdown documentation without vendor lock-in or external API dependencies, reducing operational risk and keeping sensitive knowledge local.

Best for

Engineering teams managing large Markdown knowledge bases who need automated link maintenance and semantic search without cloud infrastructure.

Works in

Claude Code Claude Cowork Claude Chat

Source

https://github.com/MarcoPorcellato/matryca-plumber

By MarcoPorcellato

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → Plugins → Add plugin. Search and click Install. Skills work in Claude Code only.

Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.

Command

claude plugins install MarcoPorcellato/matryca-plumber

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Automatically index and tag related notes in my Logseq vault for better discoverability

CostFree

Trust Signals Auto-scanned

Stars82Last updated2026-07-23LicenseApache-2.0 (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-07-23 · scanner v1

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 82 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.

Things to check

Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use

3/5

Versatility

3/5

Reliability

3/5

Security

3/5

Overall score3.00 / 5.00 UsableEvaluatedJul 2026

Scored from trust signals (evidence-eval-v1): 82 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.

← Back to the Claude Observatory