hefgi/ponder
Build EVM blockchain data indexers using Ponder (ponder.sh) - an open-source TypeScript framework for indexing smart contract events, transactions, and traces into custom database schemas with type-safe APIs. Use when the user mentions ponder, blockchain/EVM indexing, onchain data pipelines, subgraph replacement, or wants to index smart contract events into a queryable database.
98
99%
Does it follow best practices?
Impact
98%
1.25xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that hits all the marks. It provides specific concrete actions, includes a comprehensive set of natural trigger terms that developers would use, explicitly states both what the skill does and when to use it, and carves out a clear niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'indexing smart contract events, transactions, and traces into custom database schemas with type-safe APIs'. Also specifies the technology (Ponder, TypeScript framework) and domain (EVM blockchain). | 3 / 3 |
Completeness | Clearly answers both what ('Build EVM blockchain data indexers...indexing smart contract events, transactions, and traces') AND when ('Use when the user mentions ponder, blockchain/EVM indexing, onchain data pipelines, subgraph replacement...'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ponder', 'blockchain/EVM indexing', 'onchain data pipelines', 'subgraph replacement', 'smart contract events', 'queryable database'. These are terms developers in this space would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: Ponder framework, EVM blockchain, smart contract indexing. The mention of 'subgraph replacement' and 'ponder.sh' creates clear differentiation from generic database or blockchain skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent technical writing for Claude. It provides comprehensive coverage of the Ponder framework while maintaining extreme conciseness through tables, compact code examples, and well-organized sections. The decision heuristics and gotchas sections add significant value by encoding expert knowledge that prevents common mistakes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of concepts Claude would know. Every section delivers actionable information without padding. The architecture flow is a single line, decision tables are compact, and examples are minimal but complete. | 3 / 3 |
Actionability | Provides fully executable code examples with exact imports, complete configurations, and copy-paste ready snippets. The minimal working example spans all four required files with real code. CLI commands, environment variables, and tsconfig are all concrete and specific. | 3 / 3 |
Workflow Clarity | Common task checklists provide clear numbered sequences for all major workflows (scaffold, add contract, factory setup, deployment). Each checklist has explicit steps with validation points like 'run ponder dev' and health check endpoints for production verification. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick start overview, decision heuristics for common choices, gotchas section, and a clear reference navigation table pointing to one-level-deep specialized files. Content is appropriately split between the main skill and reference documents. | 3 / 3 |
Total | 12 / 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 | |
Reviewed
Table of Contents