pickled-claude-plugins
starsforks
How to install pickled-claude-plugins?
technicalpickles/pickled-claude-plugins
$git clone https://github.com/technicalpickles/pickled-claude-pluginsPersonal collection of Claude Code skills for development workflows
README.md
| 1 | # Pickled Claude Plugins |
| 2 | |
| 3 | Personal plugin marketplace for Claude Code with curated skills, commands, and hooks organized by domain. |
| 4 | |
| 5 | ## Repository Structure |
| 6 | |
| 7 | ``` |
| 8 | pickled-claude-plugins/ |
| 9 | ├── .claude-plugin/ |
| 10 | │ ├── plugin.json # Root marketplace metadata |
| 11 | │ └── marketplace.json # Plugin registry (source of truth for the Plugins list) |
| 12 | ├── plugins/ |
| 13 | │ └── <plugin-name>/ # One directory per local plugin (see Plugins below) |
| 14 | └── docs/ |
| 15 | ``` |
| 16 | |
| 17 | ## Installation |
| 18 | |
| 19 | ### Add the Marketplace |
| 20 | |
| 21 | ```bash |
| 22 | /plugin marketplace add technicalpickles/pickled-claude-plugins |
| 23 | ``` |
| 24 | |
| 25 | ### Install a Plugin |
| 26 | |
| 27 | ```bash |
| 28 | /plugin install <plugin-name>@pickled-claude-plugins |
| 29 | ``` |
| 30 | |
| 31 | For example: |
| 32 | |
| 33 | ```bash |
| 34 | /plugin install git@pickled-claude-plugins |
| 35 | /plugin install dev-tools@pickled-claude-plugins |
| 36 | ``` |
| 37 | |
| 38 | See individual plugin READMEs for details on what each plugin provides. |
| 39 | |
| 40 | ## Plugins |
| 41 | |
| 42 | <!-- BEGIN GENERATED PLUGINS (run scripts/generate-plugin-table.sh) --> |
| 43 | | Plugin | Description | Skills | |
| 44 | |--------|-------------|--------| |
| 45 | | [actually-lsp](plugins/actually-lsp) | Closes the LSP activation gap end-to-end (detection, setup, activation, failure diagnosis) for Rust, TypeScript, and Ruby projects | actually-lsp-doctor, actually-lsp-ignore | |
| 46 | | [agent-meta](plugins/agent-meta) | Meta-development tools for agentic workflows | harness-binary-spelunking, park, snapshot, unpark | |
| 47 | | [buildkite](plugins/buildkite) | Buildkite CI tools: build investigation, pipeline development, and tool preference enforcement | developing-pipelines, investigating-builds | |
| 48 | | [ci-cd-tools](plugins/ci-cd-tools) | CI/CD pipeline tools and integrations | fixing-ci | |
| 49 | | [cq](https://github.com/technicalpickles/cq) | Query past Claude Code sessions via the cq CLI (SQL over session transcripts) | [see repo](https://github.com/technicalpickles/cq) | |
| 50 | | [dev-tools](plugins/dev-tools) | Developer productivity tools and utilities | colima, designing-clis, finding-api-docs, hk, working-in-scratch-areas, working-with-mise, working-with-scope | |
| 51 | | [git](plugins/git) | Git workflow tools: commits, PRs, review inbox, checkout, and work triage | checkout, commit, inbox, pull-feedback, pull-request, push, triage, update | |
| 52 | | [github-actions](plugins/github-actions) | GitHub Actions CI tools: investigate failing runs via gh + a structured snapshot helper | investigating-runs | |
| 53 | | [gut-check](plugins/gut-check) | Ground before you act: catch decisions and factual claims made from a thin basis (memory, the handoff, an unexamined pick) | gut-check | |
| 54 | | [mcpproxy](plugins/mcpproxy) | MCP server management and integration tools | working-with-mcp | |
| 55 | | [petri-dish](https://github.com/technicalpickles/petri-dish) | Author Claude Code experiments (petri-dish cultures) with disciplined schema, baselines, and multi-run averaging | [see repo](https://github.com/technicalpickles/petri-dish) | |
| 56 | | [sandbox-advisor](plugins/sandbox-advisor) | Turns Claude Code sandbox EPERMs into crisp re-run-unsandboxed guidance | – | |
| 57 | | [second-brain](plugins/second-brain) | Knowledge management for Obsidian vaults and structured markdown repositories | connect, distill-rules, enrich, ingest, link-daily, obsidian, process-inbox, route | |
| 58 | | [stay-on-target](plugins/stay-on-target) | Focused development mode - clarify, plan, verify, detect drift | – | |
| 59 | | [taskwarrior](plugins/taskwarrior) | Token-dense recipes for taskwarrior CLI: dense listings, single-field lookups, batched exports, full-text search | taskwarrior | |
| 60 | | [tool-routing](plugins/tool-routing) | Route tool calls to better alternatives (e.g., gh CLI instead of WebFetch for GitHub PRs) | – | |
| 61 | | [working-in-monorepos](plugins/working-in-monorepos) | Navigate and execute commands in monorepo subprojects | working-in-monorepos | |
| 62 | | [writing-tools](plugins/writing-tools) | Prose skills plus a send-time hook that keeps em-dashes out of content you author | writing-for-scannability | |
| 63 | <!-- END GENERATED PLUGINS --> |
| 64 | |
| 65 | ## Usage |
| 66 | |
| 67 | ### Using Skills |
| 68 | |
| 69 | Skills are available in Claude Code via the Skill tool: |
| 70 | |
| 71 | ``` |
| 72 | Use the technicalpickles:working-in-monorepos skill |
| 73 | ``` |
| 74 | |
| 75 | Or reference them in custom skills: |
| 76 | |
| 77 | ```markdown |
| 78 | @technicalpickles:buildkite-status for checking CI status |
| 79 | ``` |
| 80 | |
| 81 | ### Using Commands |
| 82 | |
| 83 | Slash commands are available directly: |
| 84 | |
| 85 | ``` |
| 86 | /monorepo-init |
| 87 | ``` |
| 88 | |
| 89 | ### Using Hooks |
| 90 | |
| 91 | Hooks run automatically on configured events (like SessionStart for monorepo detection). |
| 92 | |
| 93 | ## Development |
| 94 | |
| 95 | To modify plugins: |
| 96 | |
| 97 | 1. Edit files in `plugins/` within this repository |
| 98 | 2. Reinstall the plugin to pick up changes: |
| 99 | ```bash |
| 100 | /plugin uninstall <plugin>@pickled-claude-plugins |
| 101 | /plugin install <plugin>@pickled-claude-plugins |
| 102 | ``` |
| 103 | 3. Restart Claude Code |
| 104 | 4. Commit and push to share across machines |
| 105 | |
| 106 | ### Plugin Structure |
| 107 | |
| 108 | Each plugin follows this layout: |
| 109 | |
| 110 | ``` |
| 111 | plugins/{plugin-name}/ |
| 112 | ├── .claude-plugin/ |
| 113 | │ └── plugin.json |
| 114 | ├── skills/ |
| 115 | │ └── {skill-name}/ |
| 116 | │ ├── SKILL.md |
| 117 | │ ├── scripts/ |
| 118 | │ ├── references/ |
| 119 | │ └── examples/ |
| 120 | ├── commands/ # Optional |
| 121 | │ └── {command}.md |
| 122 | └── hoo |
People who liked this also viewed
6 picksType
- claude-codeClaude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.WorkflowsJul 2026
- TrellisThe best agent harness.WorkflowsJul 2026
- reflyThe first open-source agent skills builder. Define skills by vibe workflow, run on Claude Code, Cursor, Codex & more. Build Clawdbot 🦞· APIs for Lovable · Bots for Slack & Lark/Feishu · Skills are infrastructure, not prompts.WorkflowsMar 2026
- pyspurA visual playground for agentic workflows: Iterate over your agents 10x fasterWorkflowsJun 2026
- claude-code🚀 Open source Claude Code CLI source code. Advanced AI Agent for developers. Includes TypeScript codebase for LLM tool-calling, agentic workflows, and terminal UI. Remember this is just the skeleton not the brain itself. Found by Chaofan Shou. WorkflowsApr 2026
- claude-codeClaude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.WorkflowsApr 2026
