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 is reasonably strong in specificity and distinctiveness, clearly identifying LinkedIn as the domain and listing concrete actions. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms could also be expanded to cover more natural user phrasings.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about LinkedIn posts, updating their LinkedIn profile, managing company pages, or automating social media on LinkedIn.'
Include additional natural trigger terms users might say, such as 'social media', 'LinkedIn article', 'share update', 'LinkedIn connection', or 'publish on LinkedIn'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create posts, manage profile, company info, comments, and image uploads.' Also includes a procedural instruction ('Always search tools first for current schemas'). | 3 / 3 |
Completeness | Clearly answers 'what' (automate LinkedIn tasks including posts, profile, comments, etc.) but lacks an explicit 'Use when...' clause. The 'when' is only implied by the nature of the tasks described, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes 'LinkedIn', 'posts', 'profile', 'comments', 'image uploads' which are natural terms users might say. However, it's missing common variations like 'social media', 'publish', 'share update', 'LinkedIn article', or 'networking' that users might naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: LinkedIn automation via a specific tool (Rube MCP / Composio). The combination of platform (LinkedIn) and integration method (Rube MCP) makes it very 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 comprehensive catalog of LinkedIn operations via Rube MCP with clear tool sequences, but suffers from significant verbosity and repetition. Information like URN formats, rate limits, and obvious API behaviors are over-explained for Claude's capabilities. The lack of concrete tool call examples (with actual parameter formats) and missing validation/error-recovery steps weaken both actionability and workflow clarity.
Suggestions
Remove obvious/redundant pitfalls that Claude already knows (e.g., 'deletion is permanent', 'tokens expire', 'HTML not supported') and consolidate the image upload flow to appear only once.
Add concrete, executable tool call examples showing actual parameter values and expected response shapes, e.g., a complete RUBE_SEARCH_TOOLS call followed by a CREATE_LINKED_IN_POST call with real parameter structure.
Add explicit validation checkpoints to workflows, such as checking API response status after post creation and implementing a retry/fix loop for common errors (401, 429).
Consider splitting the detailed pitfalls and common patterns into a separate reference file, keeping SKILL.md as a lean overview with tool sequences and the quick reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. Many pitfalls are things Claude already knows (e.g., 'Deletion is permanent and cannot be undone', 'Tokens expire', 'HTML markup in post text is not supported'). The document repeats the image upload flow three times (in workflows, common patterns, and known pitfalls). Much content describes obvious API behavior rather than adding unique knowledge. | 1 / 3 |
Actionability | Tool names and sequences are clearly listed, and key parameters are specified, which is helpful. However, there's no executable code or concrete examples of actual tool calls with real parameter values. The instruction to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' somewhat undermines the specificity of the documented parameters since they may change. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Required/Optional/Prerequisite). However, there are no explicit validation checkpoints or error recovery loops. The image upload workflow involves destructive-adjacent operations (publishing posts) but lacks verification steps like 'confirm post was created successfully' or 'if creation fails, check error response and retry'. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with sections and a quick reference table, but it's monolithic — all content is inline in a single file with no references to supporting files. The repeated image upload flow and extensive pitfalls sections could be split out. The external link to Composio docs is helpful but the skill itself is quite long for what it covers. | 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
d065ead
- 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.