Personal plugin marketplace for Claude Code and Claude Cowork — review agents, workflow orchestrators, and specialized skills.
Note
This is a personal workflow repo. The plugins here are built around my specific setup: they load cross-project code standards and preferences from a personal Obsidian-vault MCP server (vault-cortex) and use external skills (fable-mode) that live outside this repo. Installed as-is, they won't work for anyone else without adaptation. That said, the plugin structure, agent/skill design, and the ship-check review-pipeline pattern may be useful as a reference for building your own.
| Plugin | Description |
|---|---|
| ship-check | Post-implementation review pipeline: four fresh-eyes review agents (pr-reviewer, code-quality-reviewer, test-auditor, bug-checker) plus six skills covering PR review, code quality, test audit, bug hunting, and PR monitoring |
.claude-plugin/marketplace.json— marketplace manifest listing all pluginsplugins/— the plugins themselves (agents, skills, manifests).github/workflows/— release automation (version validation, artifact builds, GitHub releases)
Register the marketplace, then install a plugin:
claude plugin marketplace add aliasunder/agent-plugins
claude plugin install ship-check@agent-plugins
Or browse via /plugin > Discover.
For local development, register the repo directory instead:
claude plugin marketplace add ~/Code/agent-plugins
If you want to use these plugins as a starting point:
- Replace the vault-cortex loading steps (vault-cortex) in the agents and skills —
vault_read_notecalls onReference/code-standards-*.mdandvault_memory_recall/vault_get_memorypreference retrieval — with your own standards docs and memory/preference source (or remove them) - Remove
mcp__claude_ai_Vault_Cortex__*entries from the agents'tools:allowlists if you dropped vault-cortex - Install fable-mode as a skill, or remove it from the agents'
skills:lists - Install the sequential-thinking MCP server — the agents use it for triage reasoning (or drop it from their
tools:allowlists) - The pipeline structure, review dimensions, and procedural triggers in the skills are workflow-agnostic and should transfer as-is