A Claude Code plugin marketplace: code navigation, a bench of opinionated agents, a status line, and a couple of small conveniences.
/plugin marketplace add dpep/claude
It shows up as dpep — install what you want from /plugin.
Skills for the two questions that come up constantly while programming — where is this defined? and how do I do this in git? — plus a couple of narrower lookups.
| skill | for |
|---|---|
git |
branches, PRs, worktrees, rebases, optimizations |
rq |
find code definitions, across Ruby/Rust/Go/Python/TypeScript/JavaScript |
gqls |
search a GraphQL schema by name or meaning, or jump to a resolver |
find-skill |
locate a Claude skill definition on disk |
find-gem |
locate a Ruby gem's source |
rq and gqls drive CLIs of the same name. Without those, the two skills have
nothing to call:
brew install dpep/tools/rq dpep/tools/gqlsfind-skill, find-gem and statusbar come from this repo, and adding the
marketplace already cloned it — nothing to fetch:
make -C ~/.claude/plugins/marketplaces/dpep installThat builds rust/ and symlinks the binaries into ~/.claude/bin — make sure
that's on your PATH. Working from your own clone? Run make install from its
root.
Agents with a point of view. Each is a self-contained system prompt: summon one for a critique, or hand it the work.
Craft and analysis — analyst, librarian, rubyist, scribe.
A decision council — product-manager, hacker, staff-engineer,
production-engineer, platform-expert, skeptic, chaired by a moderator.
A compact status line: working directory, git branch or PR, session, model, context-window use and rate-limit, configurable per segment.
It renders from a small Rust binary — the same make install as above — wired
into settings.json as a statusLine command. /statusbar-install does the
whole thing: builds it, writes the settings block, and smoke-tests the render.
Teaches Claude your team's jargon. Two shell hooks stream bash output and your
prompts through ae to mine acronyms, then inject
high-confidence expansions so "the RFR is blocked on PIE" means something.
brew install dpep/tools/ae # the engine
brew install jq # the hooks parse JSON with it; ae itself doesn't need itA SessionStart hook checks both are on PATH and says how to install them if not.
Curated reference data Claude can find: markdown, CSV, TSV, JSON or YAML under
~/.claude/datasets, each with frontmatter describing what it is and when to
use it. Slash commands and a skill to create, list, search and show them.
Nothing to build — the plugin is the whole thing.
The make install above is one of several targets. They all run from the repo
root and operate on the CLIs in rust/:
make build # cargo build --release --workspace
make check # fmt-check + clippy -D warnings + tests — the gate
make install # build, then symlink binaries onto PATH
make uninstallMIT — see LICENSE.