Content
68%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.
A lean, well-structured overview with executable setup commands and a clear capability map, but it stops short of showing how to actually invoke the API: there is no sample request and no step-by-step workflow for the batch extraction and monitoring operations the skill centers on. Adding a worked API call example and an extraction workflow with polling/validation would address the weakest dimensions.
Suggestions
Add a copy-paste-ready sample request, e.g. a curl call to /x/tweets/search with the x-api-key header and a representative JSON response, so the API reference is directly actionable.
Document the bulk-extraction workflow end to end (POST /extractions → poll status → verify results, using /extractions/estimate up front) with validation checkpoints to lift workflow clarity past the batch-operation cap.
Consolidate the capability lists repeated across Overview, When to Use, and the Capabilities table into one authoritative section to trim duplicate tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient — compact tables, no explanations of concepts Claude already knows — but capability listings are repeated across the Overview, "When to Use This Skill", and the Capabilities table, and the 19 tools are enumerated twice, so a few tokens could be trimmed. It is not a 5 because of this duplication, and not a 3 since there is no padding or unnecessary explanation. | 4 / 5 |
Actionability | Concrete executable guidance is present ("npx skills add Xquik-dev/x-twitter-scraper", "export XQUIK_API_KEY=...", base URL, auth header, full endpoint table with methods), but there is no sample API request or response showing how to actually call an endpoint, leaving a minor gap. Not a 3 because the commands given are genuinely executable rather than pseudocode. | 4 / 5 |
Workflow Clarity | Setup is clearly sequenced (install → get key → export), but operational workflows like bulk extraction and monitoring are not sequenced (no start → poll → verify steps) and validation/verification steps are absent. Since the skill includes batch operations ("19 Extraction Tools", "/extractions"), the batch-operation cap limits workflow clarity to 3; it is above 2 because setup steps and an endpoint map do exist. | 3 / 5 |
Progressive Disclosure | The single file is well-organized into clear sections (Overview, When to Use, Setup, Capabilities, Examples, API Reference) with no nested references and no buried content. It is not a 5 because the file exceeds 50 lines and the API reference table is a candidate for a separate reference file, but structure and placement are otherwise good. | 4 / 5 |
Total | 15 / 20 Passed |