[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSMF8K7B7EWH2WFR6WNE49":3,"skill-same:01M6FSMF8K7B7EWH2WFR6WNE49":78},{"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":56,"commitSha":57,"skillDirectory":58,"forksCount":14,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6FSMF8K7B7EWH2WFR6WNE49","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.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\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],"automation","linkedin automation","linkedin","profile","posts","comments","via","info","composio","community","manage","uploads","MCP","automate","first","Tools","search","create","tasks","image","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.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\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":52,"source":36,"requires":53,"description":7},"unknown",{"mcp":54},[55],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Flinkedin-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add reikiplanet\u002Fdaoskills --skill linkedin-automation",{"tool":70,"command":71},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill linkedin-automation",{"tool":73,"command":74},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill linkedin-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Flinkedin-automation\u002FSKILL.md",true,[],[79,105,117,132,152,175],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":47},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[86,87,88,89,90,91,36,92,93,94,95,96,97,98,99,100,101,102,103,104],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":47},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[112,113,103,114,115,36,93,94,95,89,116,90],"ar","vr ar","interaction","requirements","performance",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":47},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[119,124,125,126,127,128,36,129,95,130,131,89],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":47},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[139,140,141,142,143,36,144,145,146,147,129,148,149,150,151],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":47},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[159,160,161,162,163,164,165,166,36,95,89,167,90,168,169,170,171,172,173,174],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":47},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[182,183,184,185,186,187,188,189,172,129,190,191,192,36,193,194,195,169,196,197],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]