GitHub collection
technicalpickles/pickled-claude-plugins
Imported from GitHub — is this yours?
50 skills imported from this repository.
- Stars
- 13
- Forks
- 4
- License
- MIT
Skills (50)
actually-lsp-doctor
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing
actually-lsp-ignore
Ignore actually-lsp nudges for an ecosystem in this project. Use when the user wants to silence, dismiss, or ignore the LSP setup nudges for a specific ecosystem (Rust, TypeScript, Ruby), or invokes `/actually-lsp-ignore` directly. Writes `dismissed=true` to `.claude/actually-lsp
harness-binary-spelunking
Use when investigating an agent-harness CLI's internals (Claude Code, codex, opencode, or similar): extracting the system prompt or tool descriptions, finding what code path produces a specific UI message, decoding minified function names or Rust symbols, understanding undocument
automic-vault-credentials
Use when a command mentions `av`, Automic Vault or automic-vault, when a task needs a credential (GitHub token, API key, SSH key, GPG signing) on a Mac that has Automic Vault installed, or when gh, git push, git commit signing or an `av` command fails with an approval, sandbox, "
developing-pipelines
Use when creating, modifying, or debugging Buildkite pipeline YAML files - ensures current syntax from official docs, validates configurations before proposing changes, and references Buildkite best practices instead of relying on training data
investigating-builds
Use when the user is working with an existing Buildkite CI run and wants to understand, diagnose, or act on it. Strong signals: a buildkite.com URL, the word "buildkite", the `bk` CLI, the `bktide` tool, or a reference to a specific pipeline, build, or job. Covers intents like: "
fixing-ci
Use when CI is failing on a branch, PR, or specific Buildkite build and the user wants to iteratively fix it through verify-locally → push → check → iterate. Strong signals: "fix CI", "make CI green", "CI is failing", "tests are failing in Buildkite", "iterate on this build", a B
come-on
Use when a reply will hand the user a result they'll act on or repeat to others. You MUST load this at the start of the turn, before other tools, when the user asks you to finish or fix something and confirm it works, report whether something is done, shipped, merged, fixed, or s
adopting-renovate
Use when adding Renovate to a repo, moving a repo's renovate.json onto the shared technicalpickles/renovate-config presets, or previewing what Renovate would open before a config merges. Detects ecosystems and CI, writes the one-line config, dry-runs it, and opens the PR.
colima
Use when Docker commands fail with "Cannot connect to Docker daemon", when starting/stopping container environments on macOS, when managing Docker contexts or profiles, or when running incus (system containers / VMs with nested virtualization) on macOS - provides Colima lifecycle
designing-clis
Use when building, improving, or reviewing command-line interfaces for better user experience - before implementing commands/output/errors, when users report confusion or frustration, or when CLI feels hard to use - provides UX principles, visual design techniques, and practical
api-documentation-discovery
Use when APIs fail repeatedly with version-related errors (method not found, wrong arguments, unknown flag) or when about to use library APIs with uncertain knowledge - guides finding current, accurate documentation instead of guessing from training data
working-in-scratch-areas
Use when creating one-off scripts, debug tools, analysis reports, or temporary documentation - ensures work is saved to persistent .scratch areas with proper documentation, organization, and executable patterns
scope
Guide for working with Scope, a developer environment management tool that automates environment checks, detects known errors, and provides automated fixes. Use when creating Scope configurations (ScopeKnownError, ScopeDoctorGroup, ScopeReportLocation), debugging environment issu
pull-feedback
Use when the user has authored a GitHub pull request and wants to work through review feedback on it. Triggers on phrases like "pull down the review on #N", "address the feedback", "what did @reviewer say on my PR", "let's work through the comments", or any request to triage, res
pull-request
Invoke this skill BEFORE running any gh pr create, gh pr edit, or gh pr comment command, or any task that will produce or modify a GitHub pull request. This is the skill for authoring outbound PR communication: creating, drafting, opening, filing, or starting a PR; updating a PR
push
Use when running git push or diagnosing why a push failed. Especially when output mixes SSH transport with hook output (lefthook, husky, pre-commit), errors include "Permission denied (publickey)" or "rejected/non-fast-forward", a pre-push hook fails, or about to debug SSH with `
update
Use when a branch or PR has merge conflicts, is behind main, or needs upstream changes pulled in. Triggers on "resolve the merge conflicts", "there's a merge conflict on the PR, fix it", "rebase this PR on main", "catch this branch up with main", "update my branch". Fetches, merg
investigating-runs
Use whenever the user mentions a GitHub Actions / GHA run, even casually — invoke this skill before reaching for raw `gh` commands, because the bundled `gha-snapshot` helper distills `gh run view --log-failed` (a firehose) into a readable block with per-job status, failed-step lo
hk-creating-checks
Use when adding, writing, or fixing a check (step) in an hk.pkl, picking a builtin or writing a custom command, declaring an effect for `--safe`, or when hk reports "effect is unknown", "unexpected argument '--safe'", or "Hook 'check' not found". Also use when a step's syntax dif
vault-capture
Use when Josh asks to write a note, make a note, or capture something for his "pickled-knowledge" Obsidian vault - triggers on "write a note about X", "make a note for this", "capture this", "note this up", "put together a note on X", or a bare URL/article/tweet handed over with
capture
Use when the user asks to read a source and make a note for it, create or find an atomic note, or check whether a note already exists or add to one that does. Triggers on "read <url> and make a note", "make a note for", "create (or find) an atomic note", "do we have notes about X
devlog
Use when finishing a feature, fixing a notable bug, wrapping up a work session, or discovering something non-obvious (a gotcha, undocumented behavior, a workaround that took several tries, a constraint you only noticed after hitting it). Write the entry immediately, in the same t
distill-rules
Review routing corrections and propose updates to vault CLAUDE.md routing rules.
link-daily
Link a processed note to today's daily note. Stage 5 of the processing pipeline.
process-inbox
Process accumulated inbox notes through the full pipeline (ingest, enrich, route, connect, link). User-facing orchestrator.
grill
Walk a depth-first decision tree anchored to a project's documented principles before brainstorming opens options. Reads docs/agents/principles.md (or probes docs/principles.md and docs/ops-principles.md directly), shortlists principles relevant to the topic, asks one question at
setup
Scaffolds principle-anchoring configuration for a project. Writes docs/agents/principles.md, adds a `### Principles` block to `## Agent skills` in CLAUDE.md or AGENTS.md, and optionally drafts hook integration snippets for settings.json or tool-routing. Run once per project befor
tailscale-cli
Use when running `tailscale` commands to debug connectivity, inspect status, or manage `tailscale serve`/`funnel`/Services — especially when `tailscale serve status` looks wrong, `tailscale` isn't found in a shell, `tailscale ping` fails against a host that's clearly up, you're w
tailscale-serve-patterns
Use when deciding how to expose a locally-running server over a tailnet (loopback bind + `tailscale serve` vs. binding directly to the tailnet interface), when a service is reachable at its Tailscale address but a request seems to bypass expected auth, when working with Tailscale
taskwarrior
Use when querying or modifying tasks via the taskwarrior CLI - dense recipes for listing, single-field lookups, multi-task batched lookups, full-text search, and the soft description-length convention. Activates on `task list`, `task add`, `task info`, `task done`, "what's on the
wait-for-it
Use when the user wants to be told when something happens later, or asks you to monitor or watch something still in progress: CI or a build finishing, PR checks or reviews landing, a deploy or release going out, a feature flag taking traffic, a log line appearing, a metric crossi
woodpecker-authoring-pipelines
Use when writing or editing `.woodpecker.yml` or `.woodpecker/*.yaml`, porting a GitHub Actions or other CI config to Woodpecker, checking whether a Woodpecker config is valid, or when a Woodpecker step behaves differently than it does locally (shell syntax, file permissions, a s
woodpecker-investigating-pipelines
Use when a Woodpecker CI pipeline failed or its status is unclear - a red `ci/woodpecker/...` check, "Pipeline failed" from `gh pr checks`, a Woodpecker `/repos/<id>/pipeline/<n>` URL, "why did CI fail" in a repo that builds with Woodpecker, or a push that has no CI result at all
working-in-monorepos
Use when working in repositories with multiple subprojects (monorepos) where commands need to run from specific directories - prevents directory confusion, redundant cd commands, and ensures commands execute from correct locations
checking-for-undisclosed-context
Use when reviewing or drafting a doc, PR/issue description, design doc, code-review prompt, or subagent persona that's supposed to stand on its own, to check whether it leans on vocabulary, acronyms, or structure pulled from other documentation or conversation the reader hasn't s
writing-for-scannability
Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert pr
Commands (13)
-
source
/cleanup-transcript— Clean up a video/audio transcript (SRT or plaintext) - identifies structure, fixes transcription errors, asks clarifying questions iteratively -
source
/connect— Connect a note to related notes in your vault using semantic search -
source
/fix-ci— Start an iterative CI fix session — resolve the input (build / PR / branch / cwd), then run the `fixing-ci` skill loop until CI is green or you've hit the iteration cap. -
source
/insight— Capture an insight from conversation to your second brain -
source
/link-project— Set up symlink from repo to vault folder -
source
/monorepo-init— Initialize monorepo configuration and activate working-in-monorepos skill -
source
/process-daily— Process voice transcriptions in today's daily note -
source
/reflect— Capture learnings from the current conversation through guided reflection -
source
/route— Route notes from inbox to appropriate vault destinations -
source
/search— Search your second brain using semantic search -
source
/setup— Set up second-brain vault configuration -
source
/validate— Validate tool-routing plugin installation and hooks format -
source
/validate— Run integration tests for the working-in-monorepos plugin.