Calculate NFT rarity scores and rank tokens by trait uniqueness. Use when analyzing NFT collections, checking token rarity, or comparing NFTs. Trigger with phrases like "check NFT rarity", "analyze collection", "rank tokens", "compare NFTs".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-nft-rarity88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong trigger term coverage and clear completeness. The explicit 'Use when' and 'Trigger with' clauses make it easy for Claude to know when to select this skill. The main weakness is that the capability description could be more specific about what concrete outputs or analyses are produced.
Suggestions
Add more specific capabilities like 'generates rarity rankings', 'calculates trait frequency percentages', or 'outputs rarity scores in JSON format' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (NFT rarity) and some actions ('Calculate rarity scores', 'rank tokens'), but lacks comprehensive detail about specific capabilities like which rarity algorithms are used, what outputs are generated, or what collection formats are supported. | 2 / 3 |
Completeness | Clearly answers both what ('Calculate NFT rarity scores and rank tokens by trait uniqueness') and when ('Use when analyzing NFT collections, checking token rarity, or comparing NFTs') with explicit trigger guidance including example phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'check NFT rarity', 'analyze collection', 'rank tokens', 'compare NFTs', 'NFT collections', 'token rarity'. These are phrases users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on NFT rarity analysis. The combination of 'NFT', 'rarity', 'tokens', and 'trait uniqueness' creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that efficiently documents an NFT rarity analysis tool. The content is concise, provides executable commands, and appropriately delegates detailed examples and error handling to reference files. The main weakness is the lack of validation steps or feedback loops for verifying analysis results or recovering from API failures.
Suggestions
Add a validation step after collection analysis (e.g., 'Verify output contains expected token count before proceeding')
Include a brief troubleshooting workflow for common API failures inline, with reference to errors.md for details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands and options without explaining what NFTs are or how rarity calculations work conceptually. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable bash commands with clear options and flags. Each use case has copy-paste ready examples with specific collection names and token IDs. | 3 / 3 |
Workflow Clarity | Steps are clearly listed and sequenced, but there are no validation checkpoints or feedback loops for error recovery. For batch operations like analyzing collections, there's no guidance on verifying results or handling partial failures. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear command sections, and well-signaled one-level-deep references to errors.md and examples.md for detailed content. The algorithm table provides quick reference without bloating the main content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
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.