buildkite-bc59c1 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited buildkite-bc59c1 (Plugin) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Personal plugin marketplace for Claude Code with curated skills, commands, and hooks organized by domain.
pickled-claude-plugins/
├── .claude-plugin/
│ ├── plugin.json # Root marketplace metadata
│ └── marketplace.json # Plugin registry (source of truth for the Plugins list)
├── plugins/
│ └── <plugin-name>/ # One directory per local plugin (see Plugins below)
└── docs//plugin marketplace add technicalpickles/pickled-claude-plugins/plugin install <plugin-name>@pickled-claude-pluginsFor example:
/plugin install git@pickled-claude-plugins
/plugin install dev-tools@pickled-claude-pluginsSee individual plugin READMEs for details on what each plugin provides.
<!-- BEGIN GENERATED PLUGINS (run scripts/generate-plugin-table.sh) -->
| Plugin | Description | Skills |
|---|---|---|
| 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 |
| agent-meta | Meta-development tools for agentic workflows | park, snapshot, unpark |
| buildkite | Buildkite CI tools: build investigation, pipeline development, and tool preference enforcement | developing-pipelines, investigating-builds |
| ci-cd-tools | CI/CD pipeline tools and integrations | fixing-ci |
| cq | Query past Claude Code sessions via the cq CLI (SQL over session transcripts) | see repo |
| dev-tools | Developer productivity tools and utilities | colima, designing-clis, finding-api-docs, hk, working-in-scratch-areas, working-with-mise, working-with-scope |
| git | Git workflow tools: commits, PRs, review inbox, checkout, and work triage | checkout, commit, inbox, pull-feedback, pull-request, push, triage, update |
| github-actions | GitHub Actions CI tools: investigate failing runs via gh + a structured snapshot helper | investigating-runs |
| gut-check | Ground before you act: catch decisions and factual claims made from a thin basis (memory, the handoff, an unexamined pick) | gut-check |
| mcpproxy | MCP server management and integration tools | working-with-mcp |
| petri-dish | Author Claude Code experiments (petri-dish cultures) with disciplined schema, baselines, and multi-run averaging | see repo |
| sandbox-advisor | Turns Claude Code sandbox EPERMs into crisp re-run-unsandboxed guidance | – |
| second-brain | Knowledge management for Obsidian vaults and structured markdown repositories | connect, distill-rules, enrich, ingest, link-daily, obsidian, process-inbox, route |
| stay-on-target | Focused development mode - clarify, plan, verify, detect drift | – |
| taskwarrior | Token-dense recipes for taskwarrior CLI: dense listings, single-field lookups, batched exports, full-text search | taskwarrior |
| tool-routing | Route tool calls to better alternatives (e.g., gh CLI instead of WebFetch for GitHub PRs) | – |
| working-in-monorepos | Navigate and execute commands in monorepo subprojects | working-in-monorepos |
| writing-tools | Skills for structuring and formatting prose so it reads well | writing-for-scannability |
<!-- END GENERATED PLUGINS -->
Skills are available in Claude Code via the Skill tool:
Use the technicalpickles:working-in-monorepos skillOr reference them in custom skills:
@technicalpickles:buildkite-status for checking CI statusSlash commands are available directly:
/monorepo-initHooks run automatically on configured events (like SessionStart for monorepo detection).
To modify plugins:
plugins/ within this repository /plugin uninstall <plugin>@pickled-claude-plugins
/plugin install <plugin>@pickled-claude-pluginsEach plugin follows this layout:
plugins/{plugin-name}/
├── .claude-plugin/
│ └── plugin.json
├── skills/
│ └── {skill-name}/
│ ├── SKILL.md
│ ├── scripts/
│ ├── references/
│ └── examples/
├── commands/ # Optional
│ └── {command}.md
└── hooks/ # Optional
├── hooks.json
└── scripts/MIT License - see LICENSE for details.
Josh Nichols (@technicalpickles)
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.