Content
53%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 is a well-structured, mostly lean walkthrough of an investor-research workflow, but its curl examples are not executable as written due to broken JSON quoting, and the workflow lacks any validation or error-recovery checkpoints. Fixing the command syntax and adding verification steps would most improve the score.
Suggestions
Fix the curl JSON payloads so each -d argument is a single complete quoted JSON object (the 'searchParams'/'query' blocks currently fall outside the closing quote), making every example copy-paste executable.
Add validation/feedback checkpoints between steps, e.g. confirm investor-search results match the target space before pulling contacts, and verify an email was found before drafting outreach.
Trim the 'Example Usage' section to only cases not already covered by the workflow, and repair the malformed 'Discover More' curl block at the end of the file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and command-forward, but the 'Example Usage' section repeats near-identical curl calls already shown in the workflow and the 'Discover More' section contains stray/malformed tokens, so it could be tightened. It is not a 4 because of this redundancy and the broken trailing block. | 3 / 5 |
Actionability | Each step ships a concrete curl command, but the JSON payloads are malformed: the -d string closes with '}' before 'searchParams'/'query' continue on later lines, so the examples are not copy-paste executable as written. This matches the 'concrete guidance but incomplete / not executable' anchor. | 3 / 5 |
Workflow Clarity | There is a clear four-step sequence (search → portfolio → contacts → email) but no validation checkpoints, error handling, or feedback loops (e.g. confirming an investor match before emailing a partner). Steps are listed but checkpoints are missing, matching the score-3 anchor. | 3 / 5 |
Progressive Disclosure | The body is a single file with well-organized sections (Setup, Workflow, Example Usage, Tips, Discover More) and no nested external references; there are no bundle files to split out. It is 4 rather than 5 because some inlined example/discovery curls read like API reference material that could live in a separate file. | 4 / 5 |
Total | 13 / 20 Passed |