Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.
.claude/skills/linkedin-automation/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | — | — |
| case-11 | ✗→✗ | ＝ Same ✗ | — | — |
| case-02 | ✗→✗ | ＝ Same ✗ | — | — |
| case-13 | ✗→✗ | ＝ Same ✗ | — | — |
| case-22 | ✗→✗ | ＝ Same ✗ | — | — |
Automate LinkedIn operations through Composio's LinkedIn toolkit via Rube MCP.
RUBE_MANAGE_CONNECTIONS with toolkit linkedinRUBE_SEARCH_TOOLS first to get current tool schemasGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit linkedinWhen to use: User wants to publish a text post on LinkedIn
Tool sequence:
LINKEDIN_GET_MY_INFO - Get authenticated user's profile info Prerequisite]LINKEDIN_REGISTER_IMAGE_UPLOAD - Register image upload if post includes an image Optional]LINKEDIN_CREATE_LINKED_IN_POST - Publish the post Required]Key parameters:
text: Post content textvisibility: 'PUBLIC' or 'CONNECTIONS'media_title: Title for attached mediamedia_description: Description for attached mediaPitfalls:
When to use: User wants to retrieve their LinkedIn profile or company details
Tool sequence:
LINKEDIN_GET_MY_INFO - Get authenticated user's profile Required]LINKEDIN_GET_COMPANY_INFO - Get company page details Optional]Key parameters:
organization_id: Company/organization ID for GET_COMPANY_INFOPitfalls:
When to use: User wants to upload and attach images to LinkedIn posts
Tool sequence:
LINKEDIN_REGISTER_IMAGE_UPLOAD - Register an image upload with LinkedIn Required]LINKEDIN_GET_IMAGES - Verify uploaded image status Optional]LINKEDIN_CREATE_LINKED_IN_POST - Create post with the image asset Required]Key parameters:
owner: URN of the image owner (user or organization)image_id: ID of the uploaded image for GET_IMAGESPitfalls:
When to use: User wants to comment on an existing LinkedIn post
Tool sequence:
LINKEDIN_CREATE_COMMENT_ON_POST - Add a comment to a post Required]Key parameters:
post_id: The URN or ID of the post to comment ontext: Comment contentactor: URN of the commenter (user or organization)Pitfalls:
When to use: User wants to remove a previously published LinkedIn post
Tool sequence:
LINKEDIN_DELETE_LINKED_IN_POST - Delete the specified post Required]Key parameters:
post_id: The URN or ID of the post to deletePitfalls:
User URN from profile:
1. Call LINKEDIN_GET_MY_INFO
2. Extract user URN (e.g., 'urn:li:person:XXXXXXXXXX')
3. Use URN as actor/owner in subsequent callsOrganization ID from company:
1. Call LINKEDIN_GET_COMPANY_INFO with organization_id
2. Extract organization URN for posting as a company pageAuthentication:
URN Formats:
Rate Limits:
Content Restrictions:
| Task | Tool Slug | Key Params | |------|-----------|------------| | Get my profile | LINKEDIN_GET_MY_INFO | (none) | | Create post | LINKEDIN_CREATE_LINKED_IN_POST | text, visibility | | Get company info | LINKEDIN_GET_COMPANY_INFO | organization_id | | Register image upload | LINKEDIN_REGISTER_IMAGE_UPLOAD | owner | | Get uploaded images | LINKEDIN_GET_IMAGES | image_id | | Delete post | LINKEDIN_DELETE_LINKED_IN_POST | post_id | | Comment on post | LINKEDIN_CREATE_COMMENT_ON_POST | post_id, text, actor |
This skill is applicable to execute the workflow or actions described in the overview.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-11 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 6 counted toward the lift figure. The other 16 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of 0 percentage points is the difference between those two pass rates over the 6 comparable cases. 7 cases got worse with the skill loaded, and they are included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.