{"id":9700,"plugin_id":"plugin_asdk_app_6a7074e91c008191942479b885fb0d9b","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:55:28.996Z","digest":"e87bfa1d004691ff8b867d8f4c8448d1c538c441b7218e69d8b31cb9cc48be03","against":null,"payload":{"name":"publora-linkedin-engagement","description":"Comment, react and reshare on LinkedIn through Publora, and mention people correctly. Use when the user wants to respond to a LinkedIn post rather than publish their own. Not for metrics — Publora exposes no LinkedIn analytics here.","included_files":[],"skill_md_contents":"---\nname: publora-linkedin-engagement\ndescription: >\n  Comment, react and reshare on LinkedIn through Publora, and mention people\n  correctly. Use when the user wants to respond to a LinkedIn post rather than\n  publish their own. Not for metrics — Publora exposes no LinkedIn analytics\n  here.\n---\n\n# LinkedIn engagement\n\nPublishing is only half of LinkedIn. This skill covers the other half:\nresponding to what is already there. Every action below happens on a live post\nunder the user's own name, in public, and the platform notifies people.\n\n## Before anything\n\n```\nlist_connections\n```\n\nEngagement needs a connected LinkedIn account, and the `platformId` goes into\neach call verbatim. If LinkedIn is not connected, say so and stop.\n\n## What is available\n\n| Action | Tool | Reversible? |\n|---|---|---|\n| React to a post | `linkedin_create_reaction` | Yes, `linkedin_delete_reaction` |\n| Remove a reaction | `linkedin_delete_reaction` | The original is gone |\n| Comment | `linkedin_create_comment` | Yes, `linkedin_delete_comment` |\n| Delete a comment | `linkedin_delete_comment` | **No** |\n| Reshare to the feed | `linkedin_create_reshare` | Delete the reshare as a post |\n\nReactions and comments need the target post's URN. Take it from what the user\ngives you — a link or an id — and never construct one. A guessed URN either\nfails or, worse, hits someone else's post.\n\n## Comments are text the user signs\n\nShow the exact comment text and the post it lands under, and wait for a yes.\n\"Leave a nice comment on that post\" is not consent to a specific sentence.\n\nKeep drafted comments short and specific to the post. Do not add hashtags,\nemoji or a pitch for the user's own product unless they asked.\n\n## Mentions\n\n`linkedin_list_mentionables` lists people captured from engagement on the\nuser's connected company pages, each with the app-scoped person id — the only\nid namespace LinkedIn resolves in a mention. Look the person up there and use\nthe returned id. A name typed into the text is plain text, not a mention, and a\nguessed id will not resolve.\n\nIf the person is not in the list, say so. They have not engaged with the\naccount, so there is nothing to mention them by.\n\n## Reshares\n\n`linkedin_create_reshare` puts an existing post on the user's own feed,\noptionally with commentary. The commentary is the user's public voice: draft\nit, show it, then post it. The original post is untouched.\n\nA scheduled reshare of the user's own upcoming post is set instead through\n`platformSettings.linkedin` on `create_post` — see the `publora-publishing`\nskill.\n\n## Never\n\n- React, comment or reshare without an explicit go-ahead on the exact content.\n- Delete a comment because it \"looks wrong\". It cannot be brought back.\n- Bulk-engage: no reacting to a list of posts, no repeated comments across a\n  feed. That is what platforms remove accounts for.\n- Claim engagement numbers or reach. Those are not available through this\n  connector.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}