Automated content similarity and grouping analysis. Groups related documents by topic, purpose, or content similarity.
49
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cluster-documents/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides a reasonable overview of the skill's purpose but suffers from missing explicit trigger guidance, which is critical for skill selection. It names the domain adequately but lacks the concrete action details and natural user keywords that would help Claude confidently choose this skill over alternatives.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks to cluster documents, find similar content, group files by topic, or identify duplicate content.'
Include more natural trigger terms users would say: 'cluster', 'categorize', 'organize by similarity', 'find duplicates', 'group similar files'.
Add specific concrete actions: 'Calculates similarity scores, generates topic clusters, produces grouping reports, identifies near-duplicates.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (content similarity/grouping) and some actions ('groups related documents'), but lacks comprehensive concrete actions like specific algorithms, output formats, or detailed operations. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('content similarity', 'grouping', 'documents', 'topic'), but misses common user variations like 'cluster', 'categorize', 'organize', 'deduplicate', or 'find similar'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to similarity/grouping analysis, but 'documents' and 'content' are generic enough to potentially overlap with document processing, search, or organization skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level framework for document clustering but fails to deliver actionable, executable guidance. It describes concepts Claude already understands (clustering, TF-IDF, embeddings) without providing the specific code, libraries, or commands needed to actually implement the workflow. The lack of concrete examples and validation steps significantly limits its practical utility.
Suggestions
Add executable Python code examples using specific libraries (e.g., scikit-learn for clustering, sentence-transformers for embeddings) instead of abstract descriptions
Include a concrete example showing sample input documents and the expected output JSON structure for the CLUSTERING_REPORT
Add validation checkpoints such as 'Verify at least N documents were successfully parsed before proceeding to clustering'
Specify how to handle edge cases: empty files, binary documents, documents with no extractable text
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory text like 'This skill helps organize large collections' and could be tighter. The Quick Reference section adds minimal value. | 2 / 3 |
Actionability | The skill describes what to do at a high level but provides no executable code, no specific library recommendations, no concrete commands, and no examples of actual implementation. Steps like 'Generate embeddings or TF-IDF vectors' and 'Apply clustering algorithms' are vague directions, not actionable guidance. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. There's no guidance on what to do if clustering fails, how to verify results are meaningful, or how to handle edge cases like empty documents or unsupported formats. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~50 lines), the structure is appropriate with clear sections for inputs, workflow steps, and outputs. No unnecessary nesting or monolithic walls of text. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4d132c7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.