linkedin-automation
Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.
65
51%
Does it follow best practices?
Impact
87%
1.45xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/linkedin-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description does a good job listing specific LinkedIn capabilities and identifying the integration mechanism (Rube MCP/Composio), making it distinctive. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be broader to capture more natural user phrasings like 'social media post' or 'share on LinkedIn'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to post on LinkedIn, update their LinkedIn profile, manage LinkedIn comments, or upload images to LinkedIn.'
Include additional natural trigger terms like 'social media', 'LinkedIn post', 'share on LinkedIn', 'publish to LinkedIn', 'LinkedIn update' to improve matching with user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create posts, manage profile, company info, comments, and image uploads.' Also includes the operational guidance to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific LinkedIn actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the action list. | 2 / 3 |
Trigger Term Quality | Includes 'LinkedIn', 'posts', 'profile', 'comments', 'image uploads' which are natural terms, but misses common variations like 'social media', 'LinkedIn post', 'update profile', 'share on LinkedIn', or 'publish'. The mention of 'Rube MCP (Composio)' is technical jargon that wouldn't be user-facing trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to LinkedIn tasks via a specific integration (Rube MCP/Composio). The combination of platform (LinkedIn) and integration method makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable structural overview of LinkedIn automation workflows with clear tool sequencing, but suffers from significant verbosity and repetition. Many pitfalls state obvious facts Claude already knows, and the image upload flow is documented three separate times. The lack of validation checkpoints on destructive operations and the absence of concrete executable examples weaken the skill's practical utility.
Suggestions
Cut redundant pitfalls that Claude already knows (token expiry, deletion permanence, rate limits) and consolidate the image upload flow to a single canonical description instead of repeating it three times.
Add explicit validation/confirmation steps for destructive operations like delete, and make image upload verification a required gate rather than optional.
Provide a concrete example of a full RUBE_SEARCH_TOOLS call and its response format so Claude knows exactly how to discover current schemas, since the skill emphasizes this as the first step.
Consider splitting the detailed workflow sections into a separate reference file and keeping SKILL.md as a concise overview with the quick reference table and setup instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. Many pitfalls are generic knowledge Claude already has (e.g., 'Deletion is permanent and cannot be undone', 'Tokens expire', 'HTML markup in post text is not supported'). The content repeats the image upload flow three times across different sections. The 'Known Pitfalls' section largely restates pitfalls already listed in individual workflows. Much of this could be cut by 50%+ without losing actionable information. | 1 / 3 |
Actionability | Tool sequences are clearly named and ordered, which is helpful. However, there's no executable code — just tool names and parameter lists. The skill instructs to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' which undermines the specificity of the documented parameters. The image upload binary step ('Upload the image binary to the returned upload URL') lacks concrete guidance on how to actually perform this. | 2 / 3 |
Workflow Clarity | Multi-step workflows are sequenced with clear ordering and labeled as Required/Optional/Prerequisite, which is good. However, there are no validation checkpoints or error recovery loops. The delete workflow lacks any confirmation step despite being destructive. The image upload workflow mentions verifying status as 'Optional' rather than making it a validation gate before proceeding to post creation. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and a quick reference table, which aids navigation. However, it's monolithic — all content is inline in one file with no references to separate detailed docs. The repeated image upload flow and duplicated pitfalls suggest content that could be better organized. The link to Composio toolkit docs is good but underutilized; more detail could be deferred there. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.