Threads Messages
Purpose and entry points
Use this skill to inspect the authenticated Threads Direct message surfaces without changing message state. Start at /messages/ or the visible 訊息 navigation entry, and load message-pages.md for stable routes and boundaries.
Confirm the page is Threads, the URL is on threads.com, the page has loaded, and authentication is visibly present. If not, stop after public exploration and ask the user to sign in manually before protected inspection.
Workflow
- Open the inbox and record the URL, title, heading, search field, navigation links, onboarding dialog, and loading state.
- If the
網頁版現已推出 Direct 訊息 onboarding dialog appears, record it as an onboarding state and do not click 繼續 unless the user explicitly asks.
- Open
陌生訊息 at /messages/requests and verify its heading, 返回, 新訊息, 隱藏, and 管理設定 links. Read the visible explanation that messages from people the user does not follow appear there.
- Open
/messages/hidden or /settings/messages only when requested and only read visible structure.
- Open
/messages/new/ only to inspect its entry state. If recipients or the composer are loading, record that state and stop.
- Report message-page structure and loading/onboarding state, never message bodies or account-specific previews unless the user explicitly requests a safe read-only summary.
Verification and safety
- Navigating between message pages is read-only.
- Never type a recipient, message, search query, or reply in this skill. Never send, accept, hide, delete, forward, or change message settings.
- Do not click
繼續 in an onboarding dialog unless explicitly requested.
- Treat conversation previews and timestamps as dynamic private data; do not write them into stable references.
- A visible new-message route is not proof that a composer is ready; verify the actual field state.
Drift maintenance
If Threads changes message routes, labels, onboarding text, or request controls, recheck the visible UI and update message-pages.md and the site map. Keep conversation identifiers and message content out of the skill.
References
1---2name: threads-messages3description: Inspect authenticated Threads Direct message inbox, requests, hidden messages, and new-message entry points through the Codex in-app browser. Use when the user asks to review message navigation or message-page structure; never send or modify messages as part of this read-only skill.4---56# Threads Messages78## Purpose and entry points910Use this skill to inspect the authenticated Threads Direct message surfaces without changing message state. Start at `/messages/` or the visible `訊息` navigation entry, and load [message-pages.md](references/message-pages.md) for stable routes and boundaries.1112Confirm the page is Threads, the URL is on `threads.com`, the page has loaded, and authentication is visibly present. If not, stop after public exploration and ask the user to sign in manually before protected inspection.1314## Workflow15161. Open the inbox and record the URL, title, heading, search field, navigation links, onboarding dialog, and loading state.172. If the `網頁版現已推出 Direct 訊息` onboarding dialog appears, record it as an onboarding state and do not click `繼續` unless the user explicitly asks.183. Open `陌生訊息` at `/messages/requests` and verify its heading, `返回`, `新訊息`, `隱藏`, and `管理設定` links. Read the visible explanation that messages from people the user does not follow appear there.194. Open `/messages/hidden` or `/settings/messages` only when requested and only read visible structure.205. Open `/messages/new/` only to inspect its entry state. If recipients or the composer are loading, record that state and stop.216. Report message-page structure and loading/onboarding state, never message bodies or account-specific previews unless the user explicitly requests a safe read-only summary.2223## Verification and safety2425- Navigating between message pages is read-only.26- Never type a recipient, message, search query, or reply in this skill. Never send, accept, hide, delete, forward, or change message settings.27- Do not click `繼續` in an onboarding dialog unless explicitly requested.28- Treat conversation previews and timestamps as dynamic private data; do not write them into stable references.29- A visible new-message route is not proof that a composer is ready; verify the actual field state.3031## Drift maintenance3233If Threads changes message routes, labels, onboarding text, or request controls, recheck the visible UI and update [message-pages.md](references/message-pages.md) and the site map. Keep conversation identifiers and message content out of the skill.3435## References3637- [Message pages map](references/message-pages.md)38- [Threads site map](../../sites/threads/references/site-map.md)39- [Threads data model](../../sites/threads/references/data-model.md)40- [Threads operating guidance](../../sites/threads/AGENTS.md)
lloyd3126