Claude Skills by technicalpickles

github.com/technicalpickles

48 skillsA× 46B× 1C× 10 installs102 views

PlansAA skill for updating your current branch with upstream changes, with intelligent conflict resolution.toolsbashgitVotes: 0GitHub stars: 10
ParkASave current work context for later resumptiontoolsgobashVotes: 0GitHub stars: 10
SnapshotACapture current session state without stoppingtoolsgoVotes: 0GitHub stars: 10
UnparkAResume work from a parked handofftoolsgitVotes: 0GitHub stars: 10
ColimaAUse when Docker commands fail with "Cannot connect to Docker daemon", when starting/stopping container environments, or when managing multiple Docker contexts on macOS - provides Colima lifecycle management, profile handling, SSH commands, and troubleshootingtoolsbashdockerVotes: 0GitHub stars: 10
Designing ClisAUse 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 patterns for creating discoverable, delightful CLIsdata-airustci/cdVotes: 0GitHub stars: 10
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Finding Api DocsAUse 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 datadata-airustgoVotes: 0GitHub stars: 10
HkAUse when hk.pkl exists in project, hook output shows hk running, or working with git hooks in hk-managed projects. Also use when setting up, configuring, or troubleshooting hk git hooks.toolspythonbashVotes: 0GitHub stars: 10
Working In Scratch AreasAUse 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 patternsdevelopmentjavascriptpythonVotes: 0GitHub stars: 10
Working With MiseCUse 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 foundtoolspythonrustVotes: 0GitHub stars: 10
Working With ScopeAGuide 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 issues, or writing rules for error detection and remediation.developmentrustgoVotes: 0GitHub stars: 10
CheckoutAUse when checking out a PR, branch, or ref for local work - sets up worktree with contexttoolsbashcode-reviewVotes: 0GitHub stars: 10
CommitAUse when committing changes to git - provides best practices for staging, commit messages, signing, and handling hook failurescode-qualityshellgitVotes: 0GitHub stars: 10
InboxAUse when checking what PRs are waiting for your review, or when starting your day to see what needs attentiontoolsbashcode-reviewVotes: 0GitHub stars: 10
Pull RequestAInvoke 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 body or description; posting a comment or reply to review feedback. Trigger on short and casual phrasings, not only the literal word "create". Example triggers: "create a PR", "draft a PR", "open a PR", "file a PR", "...code-qualitygoshellVotes: 0GitHub stars: 10
TriageAUse when reviewing git state across worktrees, stashes, and branches - helps decide what to clean up, resume, or addresstoolsgobashVotes: 0GitHub stars: 10
UpdateAUse 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, merges the base branch (merge, not rebase), and resolves conflicts by reading the intent of both sides. Do NOT use for fast-forwarding a local main after a merge (just git pull).developmentpythonbashVotes: 0GitHub stars: 10
Working With McpBUse when user mentions MCPProxy/MCP tools (e.g., "check buildkite mcp", "use slack mcp") or when you need to discover or call tools through MCPProxy - immediately checks if mcp__MCPProxy__* tools are available, suggests /mcp reconnect if missing (MCPProxy MCP server not connected), explains when to use MCP tools vs HTTP API for debuggingdevelopmenttypescriptpythonVotes: 0GitHub stars: 10
ObsidianAObsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.documentationgoVotes: 0GitHub stars: 10
Working In MonoreposAUse 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 locationstoolspythonrustVotes: 0GitHub stars: 10
Developing PipelinesAUse 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 datadata-aigorubyVotes: 0GitHub stars: 10
Investigating BuildsAUse 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: "why did this build fail", "what's flaking", "summarize pass/fail rates across recent builds", "pull logs for this job", "figure out the exact command CI ran so I can reproduce it locally" (often via docker-compose), "...devopsjavascriptrustVotes: 0GitHub stars: 10
Fixing CiAUse 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 Buildkite build URL paired with intent to push fixes, a PR with a red check the user wants to make green, or repeat-push debugging. Covers verify-fix-locally workflows (rspec, jest, lint, type checking before pushing),...developmentjavascripttypescriptVotes: 0GitHub stars: 10
Pull FeedbackAUse 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, respond to, or systematically handle review threads on the user's own PR. Do NOT use for reviewing someone else's PR, authoring PR content or replies, or checking which PRs are waiting on the user for review.data-aigobashVotes: 0GitHub stars: 10
PushAUse 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`.data-aigodebuggingVotes: 0GitHub stars: 10
Investigating RunsAUse 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 log tails, and annotations. Specific triggers (any one is enough): a `github.com/.../actions/runs/...` URL; the phrase "GitHub Actions" or "GHA"; the `gh run` CLI; a failing workflow / job / step / check; a PR with red ...devopsgobashVotes: 0GitHub stars: 10
ConnectAFind related notes via semantic search and weave links. Stage 4 of the processing pipeline.data-aigobashVotes: 0GitHub stars: 10
Distill RulesAReview routing corrections and propose updates to vault CLAUDE.md routing rules.data-aigobashVotes: 0GitHub stars: 10
EnrichATurn an ingested insight into a proper zettelkasten note with clean prose. Stage 2 of the processing pipeline.data-aiVotes: 0GitHub stars: 10
IngestATurn 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.data-aibashVotes: 0GitHub stars: 10
Link DailyALink a processed note to today's daily note. Stage 5 of the processing pipeline.data-aibashVotes: 0GitHub stars: 10
Process InboxAProcess accumulated inbox notes through the full pipeline (ingest, enrich, route, connect, link). User-facing orchestrator.toolsgobashVotes: 0GitHub stars: 10
RouteAAnalyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.data-aigobashVotes: 0GitHub stars: 10
TaskwarriorAUse 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.data-airustgoVotes: 0GitHub stars: 10
Actually Lsp DoctorADiagnose 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.ai-agentstypescriptrustVotes: 0GitHub stars: 10
Actually Lsp IgnoreAIgnore 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.ai-agentstypescriptrustVotes: 0GitHub stars: 10
PlansA> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task. **Goal:** Create a skill that helps Claude assist users with Colima (Docker runtime for macOS) - lifecycle management, profile handling, Docker context integration, and troubleshooting. **Architecture:** Progressive disclosure structure - small SKILL.md (~100-150 lines) as navigation map, detailed content in `references/` directory. Follows the "200-line rule" from skill best practices. ...ai-agentsgobashVotes: 0GitHub stars: 10
Harness Binary SpelunkingAUse 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.toolsrustgoVotes: 0GitHub stars: 10
Gut CheckAUse 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.ai-agentsgoreactVotes: 0GitHub stars: 10
CaptureAUse 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 ...toolspythongoVotes: 0GitHub stars: 10
DevlogAUse 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).toolspythongoVotes: 0GitHub stars: 10
Checking For Undisclosed ContextAUse 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 seen. Read it cold, as the specific intended reader, and flag spots where following it depends on context they don't have access to. Trigger phrases: "cold read this", "does this stand alone", "check this doesn't assum...ai-agentsrustgoVotes: 0GitHub stars: 10
Writing For ScannabilityAUse 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 fo...ai-agentsgogitVotes: 0GitHub stars: 10
Vault CaptureAUse 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 intent to write it up. Do NOT use for generic writing help, drafting prose that isn't a vault note, or when Josh is just asking a question and not asking for a note.developmenttypescriptgoVotes: 0GitHub stars: 10
GrillAWalk 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 a time with a recommended answer per question, surfaces conflicts emergently, and outputs a brief that downstream brainstorming or planning can consume. Use when starting design work and the project has principles do...ai-agentsreactnodeVotes: 0GitHub stars: 10
SetupAScaffolds 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 before using stay-principled:grill. Re-run only if the principles file layout changes.ai-agentsgitVotes: 0GitHub stars: 10
Tailscale CliAUse 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 working across a mix of macOS (GUI app) and Linux (VM/container) nodes in the same tailnet, or a node/sidecar joins fine but something downstream (a grant, an app-level check) crash-loops or silently fails — that's oft...toolsgoshellVotes: 0GitHub stars: 10
Tailscale Serve PatternsAUse 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, containe...devopsrustgoVotes: 0GitHub stars: 10