Content
42%Scale 1-5Reviews 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 catalog of LinkedIn API operations via Rube MCP with clear tool naming and sequencing, but suffers from significant verbosity, repeated information, and lack of validation steps for destructive operations. Many pitfalls explain concepts Claude already knows, and the absence of executable code or concrete examples (beyond tool slug names) limits actionability.
Suggestions
Remove redundant pitfalls sections—consolidate into one section and eliminate explanations of obvious concepts (e.g., 'deletion is permanent', what URN formats look like).
Add validation/confirmation steps for destructive operations like DELETE_LINKED_IN_POST (e.g., verify post exists first, confirm with user before deletion).
Add concrete executable examples showing actual tool invocation with sample parameters and expected response shapes, rather than just listing parameter names.
Remove the duplicated image upload flow (appears in both Workflow 3 and Common Patterns) and the vacuous 'When to Use' footer section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. Many pitfalls sections explain things Claude already knows (e.g., 'Deletion is permanent and cannot be undone', 'HTML markup in post text is not supported', explaining what URNs are). The 'When to use' descriptions are unnecessary padding. The Known Pitfalls section at the bottom repeats information already covered in individual workflow pitfalls. The final 'When to Use' section is completely vacuous. | 2 / 5 |
Actionability | Tool sequences are clearly listed with named tool slugs and key parameters, which is useful. 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 (step 2 in workflow 3) lacks concrete guidance on how to actually perform the upload. | 3 / 5 |
Workflow Clarity | Multi-step workflows are sequenced with clear numbered steps and labeled as Required/Optional/Prerequisite, which is good. However, there are no validation checkpoints or error recovery steps. The delete post workflow is a destructive operation with no confirmation or verification step, and the image upload flow lacks explicit validation before proceeding to post creation. Per rubric rules, missing validation for destructive operations caps this at 3. | 3 / 5 |
Progressive Disclosure | The content is structured with headers and a quick reference table, but everything is inlined in a single file with substantial repetition (e.g., image upload flow described in workflow 3 and again in Common Patterns). No bundle files exist, and no external references are provided. The pitfalls are duplicated between individual workflows and the consolidated Known Pitfalls section, suggesting the content would benefit from better organization. | 3 / 5 |
Total | 11 / 20 Passed |