Content
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 overview of LinkedIn automation via Rube MCP with clear tool sequences and a useful quick reference table. However, it suffers from significant verbosity—repeating information across sections, explaining concepts Claude already knows, and listing obvious pitfalls. The lack of validation checkpoints in destructive operations and the absence of concrete executable examples (relying on tool names rather than actual invocation patterns) weaken its practical utility.
Suggestions
Cut redundant content: the image upload flow is described three times (workflows 1, 3, and Common Patterns). Consolidate into one canonical workflow and reference it.
Remove pitfalls Claude already knows (token expiration, deletion being permanent, rate limit concepts) and keep only LinkedIn-specific gotchas like URN format requirements and the two-phase image upload.
Add explicit validation/confirmation steps to destructive workflows (delete post) and the image upload flow—e.g., verify image status before creating the post as a required step.
Provide concrete tool invocation examples showing actual parameter values rather than just listing parameter names, so Claude can copy-paste patterns directly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. Many pitfalls are things Claude already knows (e.g., 'Deletion is permanent and cannot be undone', 'HTML markup in post text is not supported', 'Tokens expire'). The skill repeats the image upload flow three times (in workflows 1, 3, and Common Patterns). Explanations of URN formats and rate limits are general knowledge Claude possesses. The document could be cut by 50%+ without losing actionable information. | 1 / 3 |
Actionability | Tool names and sequences are clearly listed, and the quick reference table is helpful. However, there is no executable code—just tool names with parameter lists. The skill instructs to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' which undermines providing concrete schemas here. The image upload binary step ('Upload the image binary to the returned upload URL') lacks specifics on how to actually do 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 a confirmation step despite being destructive. The image upload workflow doesn't include verification as a required step despite the two-phase nature being flagged as a pitfall. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and a quick reference table, which aids navigation. However, with no bundle files, all content is inline in a single long document (~150 lines). The pitfalls sections are repeated across individual workflows and then again in a consolidated 'Known Pitfalls' section, creating redundancy. The content could benefit from splitting detailed pitfalls and patterns into separate reference files. | 2 / 3 |
Total | 7 / 12 Passed |