zzstoatzz

Render the system prompts phi actually shipped to prod (from logfire) and hone them at their source. Use when the operator wants to review, edit, or debug any of phi's system prompts — the main agent or a sub-agent (policy judge, extractor, reconciler, episodic synth, posting inventory) — and needs to see the real composed prompt, not just the static personality file.

Wayfinding for writing to cosmik (your public knowledge graph on atproto, indexed by semble). The capability lives in the semble tools (semble_search / semble_get_schema / semble_execute) for URLs, collections, and connections, and in pdsx for standalone NOTE cards. Load when saving a URL, writing a public note, creating a typed connection, or curating collections.

How to maintain the editorial-context record that grounds coral's trending curator. Load this during an editorial pass — when refreshing your grounding notes about currently-trending entities, or when someone asks about your role in coral.

Publish photos to grain (grain.social) — generate_image output as social.grain.photo / gallery / gallery.item records via pdsx, plus the actor.profile signal record that makes grain index you. Load when posting photos to grain. For your bsky avatar/banner, load self-presentation instead.

Change how you look on bsky — avatar (profile picture) and banner (header image) on app.bsky.actor.profile/self, using a blob from generate_image. Load when you want to change your profile picture or header. Bio TEXT goes through write_bio, not this path.

How to use the pdsx MCP for atproto record CRUD on arbitrary lexicons. Load this when you want to do something on atproto that doesn't have a dedicated tool — saving to a custom lexicon, opening a tangled issue, writing a leaflet comment, etc.

Query your own execution traces (logfire) to answer "what did I actually do" — every tool call, argument, error, and silent failure across all your runs. Load before using query_traces. Use for postmortems, retro receipts, auditing your own trading discipline, and noticing failures your runs never surfaced. Not for deciding what to post.

How to read the atproto publications network (pub-search) and recommend documents you endorse. Load this when you want to see what's circulating among publications, find writing worth reading, or put your own weight behind a piece — curation, not just consumption.

Register, change, or debug Prefect deployments in this repo — schedules, triggers, parameters, work pools, job variables, secret injection, or dependency/python-version problems in flow runs. Use when editing prefect.yaml or when a flow run fails during pull or dependency install.

Read or debug the daily infra cost snapshot across Fly, Hetzner, Cloudflare, and Neon. Use when asked whether a teardown reduced spend, why a provider total moved, how a resource is attributed to a project, or when adding a cost connector. Also covers Fly volume and snapshot cleanup.

Execute a flow in this repo by hand — locally for debugging, or through the API to exercise the real production worker. Use when asked to run, test, or trigger a flow outside its schedule, and to avoid corrupting production write paths while doing it.

Diagnose the home-pool process worker on heavypad, where all flow runs actually execute. Use when a flow run is stuck in RUNNING, a run died without logs, the worker seems down, or you need to reach the worker box or restart it safely.

Query or inspect the self-hosted Prefect server at prefect-server.waow.tech, or the k3s cluster it runs on. Use when you need flow-run/deployment/block state, are told you have no credentials, are unsure which kubectl context is prod, or an /api/ call returns Unauthorized.

Read permissioned data (com.atproto.space.*) with pdsx. Experimental and served by almost no PDS — use when working with private records in a space, or when you need to know whether a given PDS supports permissioned data at all.

Read AT Protocol records and blobs from any repo with pdsx — authenticated or not, including pagination, identity resolution, and fetching blob content. Use when inspecting what an account has published, pulling records out of a PDS, or exploring an unfamiliar lexicon.

Create, update and delete AT Protocol records with pdsx, including blob upload and batch operations over JSONL. Covers what the server fills in for you, how updates merge rather than replace, and how to verify a write actually did what you meant.

bump version, update changelog, tag and push a release

reflect on recent changes through the lens of zig zen

Contributing to plyr.fm — an audio streaming app built on ATProto. Use when making changes to the plyr.fm codebase, fixing bugs, adding features, or opening pull requests.

Use this when you need to perform mutations on plyr.fm - uploading, deleting, liking tracks. The MCP server is read-only - use this skill when you need to trigger uploads, delete tracks, or modify likes.