bot

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.

Inspect phi bot's health, recent activity, and behavior using logfire traces, bsky posts, fly status, and PDS records. Use when the operator asks how phi is doing, wants to check for errors, review recent posts, or investigate a specific interaction.

Send a message to phi from the operator's devlog account (zzstoatzzdevlog.bsky.social), tagging @phi.zzstoatzz.io so phi gets a notification and acts on it. Use when the operator wants to say something to phi in-character as themselves — feedback, an apology, a nudge, a prompt to reflect or blog — rather than editing phi's code or config.

Publish a long-form post on greengale.app. Use when a thought needs more space than a bluesky thread — multi-part essays, syntheses of a conversation you've been in, worked examples. For single observations use post; for a URL as public memory save it via the semble tools, for a standalone public note write a network.cosmik.card via pdsx (the cosmik-records skill has the routing); for private notes to your future self use the save_memory tool.

Pull the exact rendered system + user prompts phi worked from on a past agent run, via the logfire MCP. Use when investigating phi's behavior — why she said that, what her context actually contained, is a block stale or feedback-looping. Read-only, no PDS writes.