crypdick

Use when managing the pynchy service on the server — deploying changes, observing logs, checking service status, restarting the service, setting up GitHub auth, rebuilding the agent container, or running commands on the live Pynchy host. Also use when interacting with the LiteLLM proxy — investigating failed requests, model routing errors, spend tracking, health checks, API gateway diagnostics, or modifying the LiteLLM configuration. Also use when the user mentions the LiteLLM UI, dashboard, proxy errors, or model availability.

Use when creating, scaffolding, or updating a pynchy plugin, including channels, MCP servers, skills, agent cores, workspace specs, and container runtime plugins. Also use when users ask how to register plugins via config.toml, add entry points, or validate plugin hook wiring.

Drive a host desktop through Pynchy's policy-mediated provider plugins when browser automation is inappropriate.

How to use browser tools for web navigation and interaction

Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.

Post tweets, like, reply, retweet, and quote on X (Twitter) using browser automation. Use when the user asks you to interact with X/Twitter.

When running multi-line Python code or code with quotes, apostrophes, or f-strings via Bash, always use heredoc syntax instead of python -c to avoid shell quoting issues.

Use when writing or reviewing pynchy documentation, deciding where to document things, updating the docs, checking doc consistency, or fixing broken links. Covers information architecture, writing philosophy, tree-shaped navigation, doc-code coupling, no hard-coded usernames, extensibility framing for pluggable subsystems, and when to add code comments.

Read, search, and create notes in the Obsidian vault/wiki memory store.

Selectively file durable, novel conversation outcomes as canonical vault notes. Use when a result will materially change future action or prevent repeated work and is not already recoverable elsewhere, or when the user explicitly asks to preserve it. Triggered by the Stop-hook decision gate or requests such as "file this", "save this conversation", and "remember this".

This skill should be used when the user asks to "organize the vault", "update indexes", "fix broken links", "rename ambiguous files", "fix filenames", "garden the vault", "sync indexes", "clean up the vault", "maintain the vault", or after making substantial structural edits (creating, moving, renaming, or deleting files) in an Obsidian vault. Also triggered by scheduled cron invocations for routine vault maintenance.

Clean up AI-sounding writing to read like a human wrote it. Use this skill whenever the user says "unslop", "de-slop", "remove AI writing", "make this sound human", "clean up AI tone", "fix AI voice", "sounds too AI", "sounds like ChatGPT", "too sloppy", "AI slop", or asks to remove, fix, or clean up signs of AI-generated text. Also trigger when the user pastes text that reads like obvious AI output and asks you to improve, rewrite, or edit it.

This skill should be used when the user asks to "strictify a repo", "add code quality enforcement", "make this repo strict", "add prek hooks", "add type checking", "enforce code quality", "set up linting", or runs the /strictify command.