Content
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional skill with strong actionability—concrete curl commands, clear URL patterns, and a complete response schema make it easy for Claude to execute. However, it suffers from moderate verbosity with redundant sections (Best Practices largely repeats earlier content, Notes restates obvious points), and the workflow lacks explicit error handling/validation steps for API failures. Trimming redundancy and adding a validation checkpoint would meaningfully improve it.
Suggestions
Add an explicit error-handling step in the workflow (e.g., 'If curl returns empty or error JSON, inform the user the post may be unavailable or the URL may be malformed').
Remove or consolidate the 'Best Practices' and 'Notes' sections—most of their content is already covered in the workflow and response schema sections.
Remove the 'Overview' paragraph explaining why the API is superior to scraping; Claude doesn't need persuasion, just instructions.
Consider removing the 'Installation' section from the skill body, as it's about setting up the skill itself rather than instructing Claude on how to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Overview' explaining why the API is 'far superior' to scraping, 'Best Practices' that largely repeat earlier content, and 'Notes' with obvious guidance. The installation section is also arguably out of scope for the skill body. However, the core content is reasonably focused. | 2 / 3 |
Actionability | Provides fully executable curl commands, concrete URL parsing examples with a clear table of URL formats, a complete JSON response schema, and worked examples showing the full flow from user input to API call to response extraction. | 3 / 3 |
Workflow Clarity | The 3-step workflow is clear and well-sequenced, but there is no validation or error handling step in the workflow itself. The notes mention checking for errors, but there's no explicit feedback loop (e.g., 'if curl fails or returns empty, try X'). For an API-calling workflow, missing error handling in the sequence is a gap. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but everything is inline in a single file with no bundle files to reference. The response schema, examples, and best practices could be more tightly organized. For a skill with no bundle, the structure is acceptable but the file is longer than necessary due to redundant sections. | 2 / 3 |
Total | 9 / 12 Passed |