[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M716EPZCWCEDCDJVX2SXFPM1":3,"skill-same:01M716EPZCWCEDCDJVX2SXFPM1":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M716EPZCWCEDCDJVX2SXFPM1","linkedin-automation",null,"Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Flinkedin-automation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"linkedin automation","automation","linkedin","2026","via","first","info","create","uploads","tasks","comments","unknown","image","MCP","company","search","manage","for","posts","community","2026-11-10 10:12:30",false,"---\nname: linkedin-automation\ndescription: \"Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# LinkedIn Automation via Rube MCP\n\nAutomate LinkedIn operations through Composio's LinkedIn toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active LinkedIn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linkedin`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linkedin`\n3. If connection is not ACTIVE, follow the returned auth link to complete LinkedIn OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create a LinkedIn Post\n\n**When to use**: User wants to publish a text post on LinkedIn\n\n**Tool sequence**:\n1. `LINKEDIN_GET_MY_INFO` - Get authenticated user's profile info [Prerequisite]\n2. `LINKEDIN_REGISTER_IMAGE_UPLOAD` - Register image upload if post includes an image [Optional]\n3. `LINKEDIN_CREATE_LINKED_IN_POST` - Publish the post [Required]\n\n**Key parameters**:\n- `text`: Post content text\n- `visibility`: 'PUBLIC' or 'CONNECTIONS'\n- `media_title`: Title for attached media\n- `media_description`: Description for attached media\n\n**Pitfalls**:\n- Must retrieve user profile URN via GET_MY_INFO before creating a post\n- Image uploads require a two-step process: register upload first, then include the asset in the post\n- Post text has character limits enforced by LinkedIn API\n- Visibility defaults may vary; always specify explicitly\n\n### 2. Get Profile Information\n\n**When to use**: User wants to retrieve their LinkedIn profile or company details\n\n**Tool sequence**:\n1. `LINKEDIN_GET_MY_INFO` - Get authenticated user's profile [Required]\n2. `LINKEDIN_GET_COMPANY_INFO` - Get company page details [Optional]\n\n**Key parameters**:\n- No parameters needed for GET_MY_INFO (uses authenticated user)\n- `organization_id`: Company\u002Forganization ID for GET_COMPANY_INFO\n\n**Pitfalls**:\n- GET_MY_INFO returns the authenticated user only; cannot look up other users\n- Company info requires the numeric organization ID, not the company name or vanity URL\n- Some profile fields may be restricted based on OAuth scopes granted\n\n### 3. Manage Post Images\n\n**When to use**: User wants to upload and attach images to LinkedIn posts\n\n**Tool sequence**:\n1. `LINKEDIN_REGISTER_IMAGE_UPLOAD` - Register an image upload with LinkedIn [Required]\n2. Upload the image binary to the returned upload URL [Required]\n3. `LINKEDIN_GET_IMAGES` - Verify uploaded image status [Optional]\n4. `LINKEDIN_CREATE_LINKED_IN_POST` - Create post with the image asset [Required]\n\n**Key parameters**:\n- `owner`: URN of the image owner (user or organization)\n- `image_id`: ID of the uploaded image for GET_IMAGES\n\n**Pitfalls**:\n- The upload is a two-phase process: register then upload binary\n- Image asset URN from registration must be used when creating the post\n- Supported formats typically include JPG, PNG, and GIF\n- Large images may take time to process before they are available\n\n### 4. Comment on Posts\n\n**When to use**: User wants to comment on an existing LinkedIn post\n\n**Tool sequence**:\n1. `LINKEDIN_CREATE_COMMENT_ON_POST` - Add a comment to a post [Required]\n\n**Key parameters**:\n- `post_id`: The URN or ID of the post to comment on\n- `text`: Comment content\n- `actor`: URN of the commenter (user or organization)\n\n**Pitfalls**:\n- Post ID must be a valid LinkedIn URN format\n- The actor URN must match the authenticated user or a managed organization\n- Rate limits apply to comment creation; avoid rapid-fire comments\n\n### 5. Delete a Post\n\n**When to use**: User wants to remove a previously published LinkedIn post\n\n**Tool sequence**:\n1. `LINKEDIN_DELETE_LINKED_IN_POST` - Delete the specified post [Required]\n\n**Key parameters**:\n- `post_id`: The URN or ID of the post to delete\n\n**Pitfalls**:\n- Deletion is permanent and cannot be undone\n- Only the post author or organization admin can delete a post\n- The post_id must be the exact URN returned when the post was created\n\n## Common Patterns\n\n### ID Resolution\n\n**User URN from profile**:\n```\n1. Call LINKEDIN_GET_MY_INFO\n2. Extract user URN (e.g., 'urn:li:person:XXXXXXXXXX')\n3. Use URN as actor\u002Fowner in subsequent calls\n```\n\n**Organization ID from company**:\n```\n1. Call LINKEDIN_GET_COMPANY_INFO with organization_id\n2. Extract organization URN for posting as a company page\n```\n\n### Image Upload Flow\n\n- Call REGISTER_IMAGE_UPLOAD to get upload URL and asset URN\n- Upload the binary image to the provided URL\n- Use the asset URN when creating a post with media\n- Verify with GET_IMAGES if upload status is uncertain\n\n## Known Pitfalls\n\n**Authentication**:\n- LinkedIn OAuth tokens have limited scopes; ensure required permissions are granted\n- Tokens expire; re-authenticate if API calls return 401 errors\n\n**URN Formats**:\n- LinkedIn uses URN identifiers (e.g., 'urn:li:person:ABC123')\n- Always use the full URN format, not just the alphanumeric ID portion\n- Organization URNs differ from person URNs\n\n**Rate Limits**:\n- LinkedIn API has strict daily rate limits on post creation and comments\n- Implement backoff strategies for bulk operations\n- Monitor 429 responses and respect Retry-After headers\n\n**Content Restrictions**:\n- Posts have character limits enforced by the API\n- Some content types (polls, documents) may require additional API features\n- HTML markup in post text is not supported\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get my profile | LINKEDIN_GET_MY_INFO | (none) |\n| Create post | LINKEDIN_CREATE_LINKED_IN_POST | text, visibility |\n| Get company info | LINKEDIN_GET_COMPANY_INFO | organization_id |\n| Register image upload | LINKEDIN_REGISTER_IMAGE_UPLOAD | owner |\n| Get uploaded images | LINKEDIN_GET_IMAGES | image_id |\n| Delete post | LINKEDIN_DELETE_LINKED_IN_POST | post_id |\n| Comment on post | LINKEDIN_CREATE_COMMENT_ON_POST | post_id, text, actor |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# LinkedIn Automation via Rube MCP\n\nAutomate LinkedIn operations through Composio's LinkedIn toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active LinkedIn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linkedin`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linkedin`\n3. If connection is not ACTIVE, follow the returned auth link to complete LinkedIn OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create a LinkedIn Post\n\n**When to use**: User wants to publish a text post on LinkedIn\n\n**Tool sequence**:\n1. `LINKEDIN_GET_MY_INFO` - Get authenticated user's profile info [Prerequisite]\n2. `LINKEDIN_REGISTER_IMAGE_UPLOAD` - Register image upload if post includes an image [Optional]\n3. `LINKEDIN_CREATE_LINKED_IN_POST` - Publish the post [Required]\n\n**Key parameters**:\n- `text`: Post content text\n- `visibility`: 'PUBLIC' or 'CONNECTIONS'\n- `media_title`: Title for attached media\n- `media_description`: Description for attached media\n\n**Pitfalls**:\n- Must retrieve user profile URN via GET_MY_INFO before creating a post\n- Image uploads require a two-step process: register upload first, then include the asset in the post\n- Post text has character limits enforced by LinkedIn API\n- Visibility defaults may vary; always specify explicitly\n\n### 2. Get Profile Information\n\n**When to use**: User wants to retrieve their LinkedIn profile or company details\n\n**Tool sequence**:\n1. `LINKEDIN_GET_MY_INFO` - Get authenticated user's profile [Required]\n2. `LINKEDIN_GET_COMPANY_INFO` - Get company page details [Optional]\n\n**Key parameters**:\n- No parameters needed for GET_MY_INFO (uses authenticated user)\n- `organization_id`: Company\u002Forganization ID for GET_COMPANY_INFO\n\n**Pitfalls**:\n- GET_MY_INFO returns the authenticated user only; cannot look up other users\n- Company info requires the numeric organization ID, not the company name or vanity URL\n- Some profile fields may be restricted based on OAuth scopes granted\n\n### 3. Manage Post Images\n\n**When to use**: User wants to upload and attach images to LinkedIn posts\n\n**Tool sequence**:\n1. `LINKEDIN_REGISTER_IMAGE_UPLOAD` - Register an image upload with LinkedIn [Required]\n2. Upload the image binary to the returned upload URL [Required]\n3. `LINKEDIN_GET_IMAGES` - Verify uploaded image status [Optional]\n4. `LINKEDIN_CREATE_LINKED_IN_POST` - Create post with the image asset [Required]\n\n**Key parameters**:\n- `owner`: URN of the image owner (user or organization)\n- `image_id`: ID of the uploaded image for GET_IMAGES\n\n**Pitfalls**:\n- The upload is a two-phase process: register then upload binary\n- Image asset URN from registration must be used when creating the post\n- Supported formats typically include JPG, PNG, and GIF\n- Large images may take time to process before they are available\n\n### 4. Comment on Posts\n\n**When to use**: User wants to comment on an existing LinkedIn post\n\n**Tool sequence**:\n1. `LINKEDIN_CREATE_COMMENT_ON_POST` - Add a comment to a post [Required]\n\n**Key parameters**:\n- `post_id`: The URN or ID of the post to comment on\n- `text`: Comment content\n- `actor`: URN of the commenter (user or organization)\n\n**Pitfalls**:\n- Post ID must be a valid LinkedIn URN format\n- The actor URN must match the authenticated user or a managed organization\n- Rate limits apply to comment creation; avoid rapid-fire comments\n\n### 5. Delete a Post\n\n**When to use**: User wants to remove a previously published LinkedIn post\n\n**Tool sequence**:\n1. `LINKEDIN_DELETE_LINKED_IN_POST` - Delete the specified post [Required]\n\n**Key parameters**:\n- `post_id`: The URN or ID of the post to delete\n\n**Pitfalls**:\n- Deletion is permanent and cannot be undone\n- Only the post author or organization admin can delete a post\n- The post_id must be the exact URN returned when the post was created\n\n## Common Patterns\n\n### ID Resolution\n\n**User URN from profile**:\n```\n1. Call LINKEDIN_GET_MY_INFO\n2. Extract user URN (e.g., 'urn:li:person:XXXXXXXXXX')\n3. Use URN as actor\u002Fowner in subsequent calls\n```\n\n**Organization ID from company**:\n```\n1. Call LINKEDIN_GET_COMPANY_INFO with organization_id\n2. Extract organization URN for posting as a company page\n```\n\n### Image Upload Flow\n\n- Call REGISTER_IMAGE_UPLOAD to get upload URL and asset URN\n- Upload the binary image to the provided URL\n- Use the asset URN when creating a post with media\n- Verify with GET_IMAGES if upload status is uncertain\n\n## Known Pitfalls\n\n**Authentication**:\n- LinkedIn OAuth tokens have limited scopes; ensure required permissions are granted\n- Tokens expire; re-authenticate if API calls return 401 errors\n\n**URN Formats**:\n- LinkedIn uses URN identifiers (e.g., 'urn:li:person:ABC123')\n- Always use the full URN format, not just the alphanumeric ID portion\n- Organization URNs differ from person URNs\n\n**Rate Limits**:\n- LinkedIn API has strict daily rate limits on post creation and comments\n- Implement backoff strategies for bulk operations\n- Monitor 429 responses and respect Retry-After headers\n\n**Content Restrictions**:\n- Posts have character limits enforced by the API\n- Some content types (polls, documents) may require additional API features\n- HTML markup in post text is not supported\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get my profile | LINKEDIN_GET_MY_INFO | (none) |\n| Create post | LINKEDIN_CREATE_LINKED_IN_POST | text, visibility |\n| Get company info | LINKEDIN_GET_COMPANY_INFO | organization_id |\n| Register image upload | LINKEDIN_REGISTER_IMAGE_UPLOAD | owner |\n| Get uploaded images | LINKEDIN_GET_IMAGES | image_id |\n| Delete post | LINKEDIN_DELETE_LINKED_IN_POST | post_id |\n| Comment on post | LINKEDIN_CREATE_COMMENT_ON_POST | post_id, text, actor |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":38,"source":46,"date_added":52,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcursor\u002Flinkedin-automation","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill linkedin-automation",{"tool":65,"command":66},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill linkedin-automation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill linkedin-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Flinkedin-automation\u002FSKILL.md",true,[],[74,97,123,133,146,163],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":85,"publishedAt":47},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[86,87,42,88,89,90,91,92,93,94,95,96],"wechat search","wechat","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":47},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[104,105,106,107,108,109,42,110,111,112,113,114,115,116,117,118,119,120,121,122],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":47},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[130,131,104,115,116,117,118,108,42,120,132,121,122,114,112,111,110,119,109,107],"trend radar","radar","pulse",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":47},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[140,141,142,143,144,145],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":47},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[148,93,156,157,158,96,115,159,160,161,106,162,119],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":47},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[165,170,171,172,119,173,160,174,175,176,177,178],"status","play","go","latest","github","discover","control","cmd","volume"]