dojo-indexer
Set up and configure Torii indexer for GraphQL queries, gRPC subscriptions, and SQL access. Use when indexing your deployed world for client queries or real-time updates.
84
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
85%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 that clearly identifies the specific tool (Torii indexer) and its capabilities (GraphQL, gRPC, SQL). The 'Use when...' clause provides explicit trigger guidance. The main weakness is that trigger terms are somewhat technical and may not match how users naturally phrase requests.
Suggestions
Add more natural user phrases like 'query game state', 'subscribe to world events', or 'access indexed data' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Set up and configure Torii indexer', 'GraphQL queries', 'gRPC subscriptions', and 'SQL access'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Set up and configure Torii indexer for GraphQL queries, gRPC subscriptions, and SQL access') and when ('Use when indexing your deployed world for client queries or real-time updates') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Torii indexer', 'GraphQL', 'gRPC', 'SQL', but these are fairly technical. Missing more natural user phrases like 'query my world', 'subscribe to events', or 'database access'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Torii indexer' is a specific tool name, and the combination of 'deployed world', 'GraphQL', 'gRPC', and 'SQL' creates a clear niche that is unlikely to conflict with generic database or API skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable examples for GraphQL queries, subscriptions, and client integration. The main weakness is verbosity - the 'What is Torii?' explanatory section and some rationale text could be removed since Claude understands indexers. The content would benefit from splitting detailed API examples into separate reference files.
Suggestions
Remove the 'What is Torii?' and 'Why use Torii' sections - Claude understands indexer concepts and this adds ~15 lines of unnecessary explanation
Move detailed GraphQL query examples and Client Integration code to separate reference files (e.g., GRAPHQL_EXAMPLES.md, CLIENT_INTEGRATION.md) and link from Quick Start
Consolidate the configuration table and Slot deployment into a separate CONFIGURATION.md file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'What is Torii?' section explaining concepts Claude likely knows, 'Why use Torii' rationale). The content is mostly efficient but could be tightened by removing explanatory sections and focusing purely on actionable guidance. | 2 / 3 |
Actionability | Provides fully executable commands, complete GraphQL queries, TypeScript code examples, and SQL queries. All examples are copy-paste ready with concrete syntax and real patterns. | 3 / 3 |
Workflow Clarity | The Development Workflow section provides clear sequenced steps across three terminals. Configuration progression from basic to production is well-structured. Troubleshooting section provides clear diagnostic steps. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~300 lines) with detailed API examples that could be split into separate reference files. References to external docs exist but inline content is heavy. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.