solana-compression
For client and program development on Solana ~160x cheaper and without rent-exemption for per-user state, DePIN registrations, or custom compressed accounts. Create, update, close, burn, and reinitialize compressed accounts.
57
68%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/solana-compression/SKILL.mdQuality
Discovery
67%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 is strong in specificity and distinctiveness, clearly identifying a niche Solana compressed accounts skill with concrete CRUD-like operations. However, it lacks an explicit 'Use when...' clause which would help Claude know exactly when to select this skill, and could benefit from additional natural trigger terms that users might employ when requesting this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about compressed accounts on Solana, ZK compression, state compression, or reducing on-chain storage costs.'
Include additional natural trigger terms and synonyms like 'ZK compression', 'state compression', 'Light Protocol', 'cheap on-chain storage', or 'account compression' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, update, close, burn, and reinitialize compressed accounts.' Also specifies concrete use cases like 'per-user state, DePIN registrations, or custom compressed accounts.' | 3 / 3 |
Completeness | Clearly answers 'what' (create, update, close, burn, reinitialize compressed accounts on Solana) and provides context on use cases, but lacks an explicit 'Use when...' clause with trigger guidance. The when is only implied through the listed use cases. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'Solana', 'compressed accounts', 'DePIN', and 'rent-exemption' which are relevant but quite technical. Missing common variations a user might say like 'ZK compression', 'state compression', or 'light protocol'. The cost comparison '~160x cheaper' is informational but not a trigger term. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Solana compressed accounts is a very specific domain unlikely to conflict with other skills. The combination of 'Solana', 'compressed accounts', 'rent-exemption', and 'DePIN' creates a clear, unique identity. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%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 skill with excellent progressive disclosure and workflow clarity, properly delegating detailed content to reference files and providing clear build/test guardrails. Its main weakness is that the SKILL.md itself lacks any executable code examples for the core compressed PDA operations, making the overview less immediately actionable—users must navigate to reference files for any concrete implementation guidance. The reference repos section, while comprehensive, is verbose and could be more concise.
Suggestions
Add a minimal inline code example showing a basic compressed PDA creation (even 5-10 lines) so the skill is immediately actionable without navigating to reference files.
Condense the reference repos section—consider grouping them into a simple table or shorter list rather than detailed descriptions of each repo, moving detailed descriptions to a separate reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts Claude would know, but includes some sections that could be tightened—the extensive reference repos listing is quite long and the security section restates some obvious points. The comparison table and flow diagram earn their place, but the overall length (~150 lines) could be trimmed. | 2 / 3 |
Actionability | The skill provides concrete build/test commands and forbidden shortcuts, but the actual program development guidance (creating, updating, closing compressed accounts) is entirely delegated to reference files. The SKILL.md itself lacks executable code examples for the core task—there's no inline code showing how to create a compressed PDA, only a flow diagram and pointers to other files. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with 5 explicit steps, includes validation checkpoints (resolve questions before execution, plan must be complete before execution, do not proceed until tests pass), and has a failure recovery loop with explicit rules (max 5 attempts, each tries something different). Build commands have explicit forbidden shortcuts acting as guardrails. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, well-organized domain references table pointing to one-level-deep reference files, categorized reference repos, and SDK documentation links. Content is appropriately split between the overview skill file and detailed reference documents. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 8 / 11 Passed | |
- Repository
- Lightprotocol/skills
- Commit
e149bdc
- Reviewed
Table of Contents
Is this your skill?
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.