Content
72%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.
Highly actionable, copy-paste-ready CLI documentation with excellent exit-code and error-schema coverage. Weaknesses are structural: a duplicated 'When to Use' section, no validation checkpoints before destructive/batch operations, and a monolithic ~530-line body whose Sales Navigator and command reference content should be split into bundle files.
Suggestions
Remove the duplicate 'When to Use' section (keep one) and consolidate the repeated 'not instant' timing warnings into 'Important Behavior' to tighten the body.
Add validation checkpoints before destructive and batch operations: e.g., confirm the target URL before 'connection remove' and 'linkedin reset --all', and verify workflow JSON before 'workflow run' with a status check loop after.
Move the Sales Navigator command reference (and optionally the full per-command flag tables) into a references/ file (e.g., references/sales-navigator.md) with clearly signaled links from SKILL.md, keeping the main file as a lean overview plus core commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and efficient — commands, flag tables, and copy-paste examples with almost no explanation of concepts Claude already knows. Minor redundancy could be trimmed: the 'When to Use' section appears twice (lines 9-10 and 38-45), and the 'not instant / 30 seconds to several minutes' warning is repeated in the intro and 'Important Behavior'. | 4 / 5 |
Actionability | Every command is fully executable with copy-paste-ready invocations ('linkedin person fetch https://www.linkedin.com/in/username --experience --education --json -q'), concrete flag tables, documented exit codes, JSON output/error schemas, and a complete auth-setup command sequence. Specific examples cover the common cases for every subcommand. | 5 / 5 |
Workflow Clarity | Sequences are present for multi-step flows (auth recovery via exit code 2, workflow run then status/wait) and error feedback exists ('always check the success field', exit-code table), but this cap applies: destructive and batch operations — 'linkedin reset --all', 'connection remove', and 'workflow run' batch execution — have no validation/verification steps before execution. Per the rubric, batch/destructive workflows without validation cap at 3. | 3 / 5 |
Progressive Disclosure | Section headers organize the content and there is one clearly signaled external doc link ('See [Building Workflows](https://linkedapi.io/docs/building-workflows/)'), but no bundle files exist and roughly 400 lines of per-command API reference are inlined in SKILL.md. The Sales Navigator and full command reference clearly belong in separate reference files, matching the 'content that should be separate is inline' anchor. | 3 / 5 |
Total | 15 / 20 Passed |