technicalpickles

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 undocumented config keys, or otherwise spelunking a shipped binary (or its pinned source) to figure out how the tool actually behaves.

Use when about to lock in a non-trivial or hard-to-reverse decision, fire AskUserQuestion to offload a call, proceed on your own preferred option, or assert something is done / found / tested / fixed / "that's how it works" — especially when the basis is memory, the handoff, the first framing, or an unchecked assumption rather than something verified this session. Also invoked as /gut-check. Use even when you feel confident; confidence is the symptom, not the all-clear.

Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.

Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.

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, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.

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 prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that's distinct from", "versus"), bolded terms followed by colons, or an embedded "X, Y, and Z" series. Composes with prose-clarity skills (concision) and voice skills (personality) rather than replacing them. Skip for source code and for casual one-line replies where formatting reads as overkill.

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.json`. Persistent across sessions for this project only.

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 management, profile handling, SSH commands, and troubleshooting

Query past Claude Code sessions using the cq CLI (SQL over session transcripts via DuckDB). You MUST use this skill whenever the user asks about their Claude session history, tool usage, errors, or past commands. This includes questions like "what tools have I used", "how many sessions today", "what was that command I ran", "show me errors", "which files have I been editing", "what skills get invoked", or any question about what happened in previous Claude Code sessions. Also use when doing meta-work (skill development, plugin analysis, workflow review) where querying past session data would be informative. If the user mentions sessions, transcripts, tool calls, or wants to recall something from a past conversation, this is the skill to use.

Build, run, test, and smoke-drive cq — the SQL-over-Claude-Code-transcripts CLI (Rust + DuckDB). Use when asked to build cq, run it, try a subcommand, verify a change works end-to-end, or run its tests.

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, or you're working across a mix of macOS (GUI app) and Linux (VM/container) nodes in the same tailnet.

Use this skill when the user asks to create a release, cut a release, publish a new version, or perform release-related tasks for the envsense project. This skill provides comprehensive guidance for the automated release process, including: - Version bumping in Cargo.toml - Pre-release verification (tests, formatting, linting) - Monitoring the automated CI/CD pipeline - Multi-platform binary builds (Linux x64/ARM64, macOS Universal) - Cryptographic signing with cosign - Release verification and troubleshooting - Schema version considerations The envsense project uses an automated workflow triggered by version changes on the main branch. This skill walks through the entire process from start to finish.

Build, run, and smoke-test bktide (Buildkite CLI). Use when asked to run bktide, build it, verify it works, or check that a change to the CLI didn't break anything. Covers the token-free command surface (--help, prime, completions, error paths); authenticated commands need a real Buildkite API token, see Auth section.

Build and run the sb CLI (Second Brain / Obsidian vault manager) against a disposable vault, or drive individual commands directly. Use when asked to run sb, test it, smoke-test it, verify a change to a command, or exercise the note/vault/daily/inbox pipeline end to end.

Build, run, and smoke-test the cenv CLI (manages isolated Claude Code config directories, like virtualenv for Claude Code). Use when asked to run cenv, build it, test it, or verify its subcommands (create/list/path/remove/settings/trust/run/login) work.

Use when authoring a petri-dish culture (Claude Code experiment), designing an A/B variant, picking a baseline cell, or shaping a probe prompt. Triggers on "write a culture", "petri-dish culture", "author a probe", "design an experiment for Claude Code", "A/B variant of <culture>", "baseline cell for <question>", or any task that produces a `config.yml` + `prompt.md` pair under `cultures/`. Also use when reasoning about whether a probe is well-shaped: multi-run discipline, structured result blocks, sequential-not-batched wording, preamble selection. Skip for running existing cultures (`petri-dish run`) and gem-internal code changes.

Use when editing lua/plugins/, lua/config/, or any nvim config file. Use when asked about keymaps, plugin options, or LazyVim settings. Use when you need to verify config changes work.