Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A code-rich, highly actionable skill body held back by padding, absent validation checkpoints, and an orphaned reference file. The inline content is strong but redundant with the unused applications.md bundle.
Suggestions
Replace the marketing "Metrics" block and trim the Resources/Limitations tail to only what Claude needs to apply the skill, removing content that does not earn its tokens.
Add explicit validation/verification steps to the batch-processing and vector-database workflows (e.g., confirm embedding shapes, verify collection counts after insert, retry on failure) to lift workflow clarity.
Link references/applications.md from the body (e.g., a "## Advanced applications → See applications.md" section) and move the duplicated use-case recipes out of SKILL.md so the main file is a lean overview with one-level-deep references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient executable code, but the marketing "Metrics" block ("25,300+ GitHub stars", "Trained on 400M image-text pairs") and a Best practices/Limitations/Resources tail pad it unnecessarily, matching the mostly-efficient-but-could-be-tightened score-2 anchor rather than the lean score-3 anchor. | 2 / 3 |
Actionability | It provides abundant copy-paste-ready Python (zero-shot classification, similarity, search, moderation, batch, vector-DB integration) plus install commands, matching the fully-executable score-3 anchor. | 3 / 3 |
Workflow Clarity | Each recipe has a clear load→preprocess→encode→similarity sequence, but batch processing and vector-DB insertion lack any validation/verification checkpoints, so per the destructive/batch cap workflow clarity stays at the score-2 anchor rather than reaching score-3. | 2 / 3 |
Progressive Disclosure | A references/applications.md bundle exists but is never linked or signaled from the body, and the same use cases (zero-shot, semantic search, content moderation, best practices) are duplicated inline, matching the references-present-but-not-signaled score-2 anchor rather than the well-signaled one-level-deep score-3 anchor. | 2 / 3 |
Total | 9 / 12 Passed |