Plugins

from mlaugharn/plugin-marketplace

Sync project-locally installed (vendored) plugins with the upstream mekari-tools marketplace repo. Three-way merges upstream changes into local plugin copies while preserving project-specific tailoring. Update-only: never adds or removes plugins.

Topic-Synergy Outreach Engine — find the people writing about your topics (and the people you cited) and reach them without pitching. Builds a topic fingerprint from your own content, then runs THREE discovery centers. AUTHOR center (named profiles via Apify harvestapi/linkedin-profile-posts) and CONTENT center (keyword/hashtag search via Apify harvestapi/linkedin-post-search) are comment-first, starting from who's posting; discovered posts are scored against the fingerprint, deduped against an xlsx tracker, and queued, then /synergy-run executes the comment-first decision tree (like + a practitioner comment, the cite-then-tell lever, and a connection note) with a hard human gate and a guard against the LinkedIn 'Post as' identity selector. The new CITATION center starts from who you cited: /synergy-cite-harvest parses your paper's bibliography, triages by reachability, resolves authors via OpenAlex/ORCID, dedups against Clarify, enriches person + org via Apollo (LinkedIn-first match + a verify gate against wrong-person matches), verifies LinkedIn identity via Apify, and drafts a 'we cited you' email + a hook-free connect note into a citation registry; /synergy-cite-run sends email first (Mailtrap as you, BCC you) then the LinkedIn connect, with the hard-won send discipline (type the note in separate click+type calls to beat the focus-race truncation bug, zoom-verify the note's start and end before Send, 2nd/3rd/high-follower button geography, the email-verification gate, never withdraw to re-send); /synergy-cite-accept-check follows through on accepted invites. /synergy-schedule stands up an every-other-day prep task. Cadence + guardrails baked in: comment same-day/connect later, the ~20-25/day LinkedIn connect ceiling, cite-don't-pitch, voice (no em-dashes, contractions, practitioner register), verified citations only. The plugin never auto-sends. v0.2.0.

Multi-agent deliberation system with 3-round structured debate, SID confidence scoring, CortexDebate Trust Score, and 5 specialized modes (review, design, debug, idea, general)

Pre-release multi-language impact, native enforcement, secure sandbox, reversible compression, durable sessions and paired benchmarking

General-purpose synthetic data toolkit — generate, extract, extend, and anonymize tabular datasets across domains

Interactive synthetic data generator. Builds a data model through dialog, generates with Faker + NL extras, outputs CSV/XLSX/SQLite.

Set up synthetic monitoring for proactive performance tracking

Deploy and operate synthkit: first-run onboarding, deployment verification, blueprint authoring, PDC and Fleet Management setup.

Design production-grade software systems with expert knowledge of architecture patterns, distributed systems, cloud platforms, and operational excellence. Use this skill when architecting complex systems, evaluating technology choices, designing scalable infrastructure, or making critical architectural decisions requiring trade-off analysis.

System design knowledge for AI coding agents. 1 skill, 13 self-contained commands, and 14 original-prose reference files — no external links.

System specs served read-only over MCP, with authoring conventions, deterministic gates, and three skills driving the authoring, implement-service and consume-service journeys.

from ghostmind-dev/system

Skills that operate and maintain the skill system itself.

System Architecture Capture. The what-is-running second brain (139 architecture/runtime nouns). Fail-closed 1/4-window ContextPack token budget.

Cloud-agnostic system design across AWS, Azure, Google Cloud, and Cloudflare: a six-step Well-Architected loop, grounded in each cloud's live documentation MCP when connected. Auto-engages for architecture and service-selection work.

System-design interview frameworks and 28 worked designs, loaded on demand. Invoke with /system-design or ask a system-design question.

Run a structured system design interview that turns a rough product idea into a complete, installable Claude skill capturing everything needed to build the system.

Automated daily system health report. /system-report:init scaffolds config + tooling into any repo; /system-report:run collects multi-instance logs, runs a READ-ONLY AI triage (known-issues + watchlist + code correlation) and delivers a severity-ranked digest via webhook + dated file. Project-agnostic; project specifics live in the repo's ops/system-report/config.yml.

File organization and cleanup utilities - sort messy folders, find duplicates, and restructure directory hierarchies

File organization and cleanup utilities - sort messy folders, find duplicates, and restructure directory hierarchies

4-phase root cause investigation methodology: investigate, analyze patterns, test hypotheses, implement fix. Prevents random fix attempts.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

4-phase root cause debugging protocol: understand bugs before fixing. Use for ANY technical issue — test failures, production bugs, unexpected behavior, performance problems, build failures, or integration issues. ESPECIALLY when under time pressure, when "one quick fix" seems obvious, or when previous fix attempts have failed.

Reproducible systematic-search and screening workflow with explicit eligibility criteria, stable record deduplication, and an auditable decision trail.

Systems architecture and distributed systems skills including Designing Data-Intensive Applications (Martin Kleppmann), System Design Interview (Alex Xu), Clean Architecture (Robert C. Martin), Release It! (Michael Nygard), High Performance Browser Networking (Ilya Grigorik), and Team Topologies (Skelton & Pais)

Systems programming with Rust, Go, C, and C++ for performance-critical and low-level development

Systems programming with Rust, Go, C, and C++ for performance-critical and low-level development

Systemic root-cause analysis via the Questions of a Systems Thinker and Causal Loop Diagrams. By Agile Pain Relief (CC BY-SA 4.0), packaged for this marketplace.

Systemic root-cause analysis via the Questions of a Systems Thinker and Causal Loop Diagrams. By Agile Pain Relief (CC BY-SA 4.0), packaged for this marketplace.