Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable skill body with clear tool sequences and parameters, weakened by redundant pitfall sections and a destructive delete workflow that lacks an explicit validation checkpoint.
Suggestions
Add a confirmation/validation step to the Delete workflow (e.g., 'Confirm the post_id with the user before deleting; deletion is permanent') so destructive operations have an explicit checkpoint.
Consolidate the duplicated pitfalls — fold 'Common Patterns' and 'Known Pitfalls' into the per-workflow sections or keep only net-new information to reduce redundancy.
Specify concrete values where possible (e.g., the post character limit, valid visibility enum values) to close the minor actionability gaps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and assumes Claude's familiarity with LinkedIn, but the 'Common Patterns' and 'Known Pitfalls' sections repeat information already covered in the per-workflow 'Pitfalls' lists (rate limits, URN formats, image upload flow). | 3 / 5 |
Actionability | Concrete, executable guidance is provided via named tools (LINKEDIN_CREATE_LINKED_IN_POST), ordered sequences, and specific parameters (text, visibility, actor, owner), with only minor gaps such as unstated exact character limits or enum values. | 4 / 5 |
Workflow Clarity | Multi-step processes are clearly sequenced and setup includes verification, but the destructive 'Delete a Post' workflow has no validation/confirmation checkpoint, which caps workflow clarity at 3 per the rubric. | 3 / 5 |
Progressive Disclosure | Content is well organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with a single one-level external link and no nested references; no bundle files are needed. | 4 / 5 |
Total | 14 / 20 Passed |