manage-commentslisted

# Work the comment section Replying is where reach turns into relationships. This skill covers the read → triage → reply loop on published content. For *automated* keyword-triggered DMs, use `/upload-post:autodm-setup` instead. ## 1. Find the post Comment tools identify a post by either `postId` or `postUrl`. Platform quirks: - **YouTube**: `postId` is the videoId. - **LinkedIn**: `postId` is the post urn. - **TikTok**: not supported for comments at all. Say so plainly rather than trying and failing. If the user does not have the id, `get_media` lists recent posts pulled from the connected account, and `get_history` lists what was published through Upload-Post. ## 2. Read `get_post_comments` with `user`, `platform` (instagram / facebook / youtube / linkedin), and the post identifier. `limit` caps at 50 — Meta's ceiling, not ours — and `after` pages through the rest. Do not paste the raw list back. Triage it: - **Questions** — deserve an answer, highest priority. - **Buying signals** — "how much", "link?", "where do I get this". These are leads; consider a private reply. - **Praise** — a short human reply, or nothing. - **Spam / abuse** — candidates for deletion. ## 3. Reply Three different tools, and picking the wrong one is the main failure mode here: | Intent | Tool | Notes | | :--- | :--- | :--- | | Public reply under an existing comment | `public_reply_to_comment` | `user`, `commentId`, `message`. Instagram only. | | Private DM to the person who commented | `r