A Claude Code plugin marketplace
npx claudepluginhub acostanzo/quickstopAudit and optimize Claude Code configurations with dynamic best-practice research
A Claude Code plugin marketplace.
Memory system for AI agents — capture, consolidate, and recall knowledge across sessions and machines.
/heimdall/odin — quick grep first, deep agent search if neededCommands: /setup, /status, /heimdall, /odin <topic>
Enforce conventional commits, conventional comments, and engineering ownership for commits, PRs, and code reviews.
Auto-invokes on: commits, pull requests, code reviews
Audit and optimize Claude Code configurations with dynamic best-practice research.
~/.cache/claudit/ with version-based + 7-day TTL invalidation/claudit:knowledge exposes cached research to other plugins — auto-refreshes stale domainsCommands: /claudit — run audit, /claudit:refresh — refresh cache, /claudit:status — show cache state, /claudit:knowledge — retrieve cached research
Build, audit, and improve Claude Code skills with research-first architecture and opinionated structure.
Commands: /skillet:build <name>, /skillet:audit <path>, /skillet:improve <path>
Automatic documentation-as-code engine. Maintains project documentation as a side effect of development — config-driven, no manual invocation needed.
.inkwell.json controls all detection patterns and output paths — no hardcoded assumptions/inkwell:prime setup wizard detects your stack and generates config with sensible defaultscode-comments rule enforces meaningful comments across source filesCommands: /inkwell:prime, /inkwell:capture, /inkwell:adr <title>, /inkwell:changelog, /inkwell:index, /inkwell:stale
Repo-level skills for plugin authors (not distributable plugins — these live in .claude/):
| Command | Purpose |
|---|---|
/smith <name> | Scaffold a new plugin with correct structure and conventions |
/hone <name> | Audit an existing plugin's quality (8-category scoring with interactive fixes) |
Both tools dispatch research agents to fetch the latest Anthropic plugin docs before operating, ensuring scaffolds and audits reflect the current spec.
If you're building a plugin or skill that needs Claude Code ecosystem knowledge (plugin specs, skill authoring, MCP, hooks), you can consume claudit's cached research instead of fetching docs yourself.
| Domain | Content |
|---|---|
ecosystem | Plugin system, skills, agents, hooks, MCP servers |
core-config | Settings, permissions, CLAUDE.md, memory system |
optimization | Performance patterns, over-engineering detection |
In your skill's research phase, invoke the knowledge skill and fall back to your own research if claudit isn't installed:
### Step 1: Load Expert Context
Invoke `/claudit:knowledge ecosystem` to retrieve ecosystem knowledge.