Content
64%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a thorough CLI reference with excellent actionability — every command has executable examples and detailed flag documentation. However, it suffers from being overly long and monolithic without progressive disclosure, has a duplicated 'When to Use' section, and critically lacks multi-step workflow guidance with validation checkpoints for batch/sequential operations that the tool is designed to support.
Suggestions
Remove the duplicate 'When to Use' section and consolidate into a single concise block at the top.
Add a multi-step workflow example (e.g., 'Search → Fetch profiles → Send connection requests') with explicit validation checkpoints, rate-limit handling, and error recovery between steps.
Split detailed command references (Sales Navigator, Posts, Company) into separate bundle files and reference them from the main SKILL.md to improve progressive disclosure.
Add guidance on handling exit code 6 (rate limited) with retry/backoff logic, especially for bulk operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but has redundancy issues: 'When to Use' appears twice with overlapping content, and some explanations (e.g., what the tool does, how browser automation works) are repeated. The flag tables and examples are well-structured but the overall document could be tightened by ~20-30%. | 3 / 5 |
Actionability | Every command has fully executable, copy-paste ready examples with proper flags. The skill covers all major operations with concrete CLI invocations, flag tables with specific allowed values, output format examples, and exit code references. This is highly actionable. | 5 / 5 |
Workflow Clarity | The skill documents individual commands well but lacks multi-step workflow sequencing with validation checkpoints. For a tool that involves batch operations (bulk lead enrichment, outreach workflows), there are no feedback loops for error recovery, no guidance on handling rate limiting (exit code 6) retry logic, and no validation steps between sequential operations. The authentication recovery flow is the only multi-step sequence with clear guidance. | 3 / 5 |
Progressive Disclosure | The content is a long monolithic document (~400+ lines) with no bundle files to offload detailed reference material. Sales Navigator commands, company commands, and post commands could each be separate reference files. The single external link to workflow JSON schema documentation is appropriate, but the bulk of the flag tables and examples would benefit from being split into referenced files. | 3 / 5 |
Total | 14 / 20 Passed |