Technicalpickles Pickled Claude Plugins
technicalpickles-pickled-claude-plugins is a Claude Code plugin for the Build phase that packages ten development-workflow skills for git, monorepos, CI, and MCP tool routing.
by technicalpickles · github.com/technicalpickles/pickled-claude-plugins
Install ten personal Claude Code skills covering git, monorepos, Buildkite, MCP proxy routing, and meta agent tooling for daily dev.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install technicalpickles-pickled-claude-plugins@technicalpickles/pickled-claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:technicalpickles/pickled-claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:technicalpickles/pickled-claude-plugins").
What it does
technicalpickles-pickled-claude-plugins is a community-sourced Claude Code marketplace bundling ten skills tuned by a practitioner for real engineering loops. The keyword surface—git, monorepos, Buildkite, mcpproxy, routing, target, stay, working—points to meta-layer concerns: which repo, which tool, which CI context, and how to keep the agent from wandering across a large workspace. Rather than one vertical feature, the collection acts like a personal operating system for Claude Code: dev shortcuts, agent brain prompts, and glue between MCP servers and everyday edits. Solo builders juggling monorepos or polyglot folders benefit when sessions need consistent guardrails without rewriting system instructions each time. journey-wide scope fits because git hygiene and tool routing matter from first commit through production fixes. Intermediate complexity reflects optional MCP proxy setup and CI familiarity. It is a plugin bundle, not a hosted marketplace directory—install when you trust curated personal patterns over generic defaults.
Highlights
- Ten-plugin personal marketplace for Claude Code development workflows
- Git and monorepo-oriented skills for branch and target routing
- Buildkite CI awareness for agent-assisted pipeline context
- MCP proxy and meta tooling for consolidating external agent tools
- Second-brain and working-set patterns to keep Claude on the right repo scope
Why builders use it
Large repos and many MCP tools make Claude sessions drift across the wrong packages, branches, or CI jobs without repeatable routing skills.
After registration you get ten skills that steer Claude toward the right git targets, monorepo scope, Buildkite context, and proxied tools during daily work.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 8 stars, 0 votes.
FAQ
Who is technicalpickles-pickled-claude-plugins for?
It is for Claude Code users maintaining complex git layouts, CI with Buildkite, and multiple MCP tools who want a personal skill library.
When should I use technicalpickles-pickled-claude-plugins?
Use it whenever you start a coding session and need consistent agent routing across monorepos, branches, and external tools—not only during initial scaffolding.
How do I add technicalpickles-pickled-claude-plugins to my agent?
Add technicalpickles/pickled-claude-plugins as a Claude Code marketplace source, install the ten plugins you need, and configure MCP proxy skills if you route external servers.
Comments
Share how you use technicalpickles-pickled-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.