Content
57%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.
The skill has a clear four-step structure and concrete endpoint-level intent, but every curl example is syntactically invalid JSON-in-shell that would fail if executed, which undercuts its core value as a copy-paste playbook. Validation and step-chaining are absent, and the tail sections add duplication rather than progressive disclosure.
Suggestions
Fix all curl payloads so the full JSON body (api, path, and searchParams/query/lead) sits inside a single quoted -d '...' string; as written, every example breaks shell quoting and would not execute.
Add validation checkpoints and chaining: check each response for errors or empty results, and use Step 1's investor/firm output to parameterize Steps 2-4 instead of hardcoded Sequoia examples.
Merge the redundant "Example Usage" into the workflow steps as parameter variations, and clean up the "Discover More" section (remove the stray "api show fiber" token and the misquoted olostep example) or move endpoint discovery into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and code-forward with no over-explanation of known concepts ("Find investors in your space", "Get contact info for partners"), matching 'efficient; minor instances that could be trimmed'. It is not 5 because the "Example Usage" section re-runs the Step 1 and Step 2 commands with only parameter variations, which is redundant. | 4 / 5 |
Actionability | Commands name concrete endpoints (/v1/investor-search, /v1/people-search, /find-email) with realistic parameters, but every curl payload is syntactically broken: the JSON closes after '"path":"..."' and the "searchParams"/"query" object sits outside the quoted -d string with stray unmatched '}' tokens (and '"path":"/v1/scrapes`"}' misquotes in Discover More), so nothing is copy-paste executable. This matches 'concrete guidance but incomplete; pseudocode instead of executable code'. | 3 / 5 |
Workflow Clarity | Steps 1-4 are clearly headed and sequenced, but there are no validation checkpoints (no error or empty-result handling on API responses) and steps do not chain (Step 2 hardcodes "Sequoia Capital" instead of using Step 1 output), matching 'sequence present but checkpoints missing or implicit'. It is not 4 because checkpoint gaps are pervasive, and not 2 because the sequence itself is well defined. | 3 / 5 |
Progressive Disclosure | The single file has reasonable section headers, but the ~130-line body inlines endpoint-discovery material in a muddled "Discover More" section (with a stray "api show fiber" token) and duplicates workflow content in "Example Usage", matching 'some structure but could be better organized'. No bundle files exist to provide one-level-deep references. | 3 / 5 |
Total | 13 / 20 Passed |