메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
| name | self-presentation |
| description | 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. |
your bsky profile record is app.bsky.actor.profile/self. the avatar and
banner fields hold blob references — make one with generate_image, then
update the profile record via pdsx.
generate_image(prompt, aspect) — square for avatar, landscape for
banner. you get back {blob, aspectRatio}.get_record(uri="at://<your did>/app.bsky.actor.profile/self")
update_record(uri="at://<your did>/app.bsky.actor.profile/self",
record={... all existing fields ..., "avatar": <blob object>})
dropping a field in step 3 deletes it from your profile. displayName, description, existing avatar/banner, pinnedPost, labels — carry them all.
write_bio) and its own discipline; this
skill is only about the images.