technicalpickles

@technicalpickles source repo

27 skills
0 followers
1 week ago last updated

▌
Actually Lsp Doctor · technicalpickles
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.

0 installs
▌
Actually Lsp Ignore · technicalpickles
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.

0 installs
▌
Tailscale Serve Patterns · technicalpickles
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 identity headers (`Tailscale-User-Login` and friends) for browser auth, or when a "bind is loopback-only" security check doesn't seem to reflect what's actually reachable (Docker port publish, reverse proxy, container networking).

0 installs
▌
Connect · technicalpickles
Find related notes via semantic search and weave links. Stage 4 of the processing pipeline.

0 installs
▌
Obsidian · technicalpickles bundle
Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.

0 installs
▌
Link Daily · technicalpickles
Link a processed note to today's daily note. Stage 5 of the processing pipeline.

0 installs
▌
Tailscale CLI · technicalpickles bundle
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.

0 installs
▌
Taskwarrior · technicalpickles
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 backlog", "find a task", or any taskwarrior interaction.

0 installs
▌
Distill Rules · technicalpickles
Review routing corrections and propose updates to vault CLAUDE.md routing rules.

0 installs
▌
Process Inbox · technicalpickles
Process accumulated inbox notes through the full pipeline (ingest, enrich, route, connect, link). User-facing orchestrator.

0 installs
▌
Working With Mise · technicalpickles bundle
Use when adding, configuring, or troubleshooting mise-managed tools - ensures proper CLI usage, detects existing config files, and diagnoses PATH/activation issues when commands aren't found

0 installs
▌
Developing Pipelines · technicalpickles bundle
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

0 installs
▌
Push · technicalpickles
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 `-v`.

0 installs
▌
Commit · technicalpickles
Use when committing changes to git - provides best practices for staging, commit messages, signing, and handling hook failures

0 installs
▌
Triage · technicalpickles
Use when reviewing git state across worktrees, stashes, and branches - helps decide what to clean up, resume, or address

0 installs
▌
Update · technicalpickles
Use when updating your branch with upstream changes - fetches, merges, and intelligently resolves conflicts

0 installs
▌
Checkout · technicalpickles
Use when checking out a PR, branch, or ref for local work - sets up worktree with context

0 installs
▌
Park · technicalpickles bundle
Save current work context for later resumption

0 installs
▌
Colima · technicalpickles bundle
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

0 installs
▌
Pull Feedback · technicalpickles bundle
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

0 installs
▌
Route · technicalpickles
Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.

0 installs
▌
Snapshot · technicalpickles
Capture current session state without stopping

0 installs
▌
Gut Check · technicalpickles bundle
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.

0 installs
▌
Devlog · technicalpickles bundle
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 turn - don't ask permission, don't offer, just do it. Do NOT use for routing, connecting, or moving notes (that's process-inbox), and do NOT use for one-off external-source capture (that's second-brain:capture).

0 installs
▌
Enrich · technicalpickles
Turn an ingested insight into a proper zettelkasten note with clean prose. Stage 2 of the processing pipeline.

0 installs
▌
Ingest · technicalpickles
Turn a raw session notes file into an ingested note, ready for the enrich stage. Defaults to keeping it whole; only splits when bullets show a real cross-topic signal. Stage 1 of the processing pipeline.

0 installs
▌
Capture · technicalpickles bundle
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. Triggers on "read <url> and make a note", "make a note for", "create (or find) an atomic note", "do we have notes about X?", "check if we have a note for", "capture this", "put together a note", "distill this", and on a bare URL/PDF/tweet/thread handed over with intent to write it up. Covers the whole loop as one arc - search the vault first, read the primary source, write the note through the sb CLI, then offer connections. Use inside an Obsidian vault or anywhere a vault is configured. Do NOT use for draining an accumulated inbox backlog (that is process-inbox), for extracting insights from the current conversation (that is devlog), or for routing already-captured notes to their homes (that is route).

0 installs

27 published skills