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 delivers a clear five-step job-search workflow with concrete API commands, but most curl payloads contain malformed JSON (searchParams placed outside the request body, stray characters), making them non-executable as written, and the workflow has no validation or error-handling guidance. Structure and progressive disclosure are good, with mild padding from a duplicated example section and generic tips.
Suggestions
Fix the curl payloads so searchParams is inside the JSON body: '-d '{"api":"fiber","path":"/v1/job-search","searchParams":{"job_titles":[...],"locations":[...]}}'' — currently Steps 1, 2, 4 and both examples close the JSON before searchParams, leaving unbalanced braces/quotes.
Remove stray characters that break the final commands: the trailing 'api show fiber' text in Discover More and the stray backtick/unclosed quote in the olostep example ('/v1/scrapes`"').
Add basic validation checkpoints to the workflow: check HTTP/error responses before proceeding, and handle empty search results (e.g., suggest broadening job titles or locations) instead of assuming every step returns data.
Trim the duplicate Example Usage section (it re-runs Steps 1-2) and the generic Tips, or replace them with concrete guidance such as example response fields to look at when ranking results.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is code-dominant with almost no concept explanation, but contains unnecessary padding: a restated intro line under Setup ("Search for jobs matching your skills, experience level, and location preferences"), an Example Usage section that duplicates Workflow Steps 1-2, and generic Tips ("Research company culture before applying"). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trims-only level. | 3 / 5 |
Actionability | Concrete curl commands with working auth setup are provided, but most payloads are malformed as written: Steps 1, 2, 4 and both Example Usage commands terminate the JSON before "searchParams" ("-d '{\"api\":\"fiber\",\"path\":\"/v1/job-search\"}' \"searchParams\": {...}'" leaves unbalanced braces and quotes), the first Discover More command has stray text ("' api show fiber"), and the final example has a stray backtick and unclosed quote ("/v1/scrapes`"). This matches 'some concrete guidance but incomplete; missing key details' rather than a 4, since the breakage affects most commands, not a minor gap; it is above a 2 because the structure, auth, and Steps 3 and 5 are genuinely executable. | 3 / 5 |
Workflow Clarity | The five steps (search jobs, research companies, get company intel, find hiring managers, get contact info) are clearly sequenced, but there are no validation checkpoints at all: no error handling, no guidance on parsing responses, and no handling of empty results. This matches 'steps listed but validation gaps; checkpoints missing or implicit'. The operations are read-only searches, so the destructive/batch cap is not the limiter; a 4 would require most checkpoints to be present. | 3 / 5 |
Progressive Disclosure | The single-file skill is organized into coherent sections (Setup, Workflow, Example Usage, Tips, Discover More), and Discover More correctly delegates full endpoint discovery to API calls (orthogonal/search, orthogonal/details) instead of inlining an API reference. This matches 'good structure; most content appropriately placed; minor organization gaps' — the gap being the Workflow/Example Usage redundancy. Not a 5: the body exceeds 50 lines and that redundancy shows content is not optimally placed. | 4 / 5 |
Total | 13 / 20 Passed |