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.

Install with Tessl CLI

npx tessl i github:steebchen/proof-of-war --skill dojo-indexer

What are skills?

1.36x

Review — 75%

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/skill

Learn more

Evaluation — 100%

↑ 1.36x

Agent success when using this skill

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 defines both capabilities and usage triggers. The specificity around Torii indexer and the explicit 'Use when...' clause are strengths. The main weakness is that trigger terms lean heavily technical, which may miss users who describe their needs in more natural language.

Suggestions

Add more natural language trigger terms like 'query game data', 'subscribe to events', 'real-time data', or 'index blockchain data' to capture users who may not use technical terminology

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 variations users might say like 'query data', 'subscribe to events', 'database access', or 'indexing'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche with 'Torii indexer' and 'deployed world' terminology. The combination of Torii + GraphQL/gRPC/SQL creates a distinct fingerprint unlikely to conflict with generic database or API skills.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a functional skill with strong actionability - the code examples are executable and comprehensive. However, it suffers from verbosity with unnecessary explanatory sections and could benefit from better progressive disclosure by moving detailed GraphQL/client examples to separate reference files. The workflow lacks explicit validation checkpoints for confirming successful indexer setup.

Suggestions

Remove the 'What is Torii?' and 'When to Use This Skill' sections - Claude knows what indexers do and the description already covers use cases

Add validation steps to the Development Workflow: e.g., 'Verify Torii is indexing: curl http://localhost:8080/graphql and check for schema response'

Move detailed GraphQL query examples and client integration code to separate reference files (GRAPHQL_REFERENCE.md, CLIENT_INTEGRATION.md) and link from Quick Start

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanatory content like 'What is Torii?' section explaining concepts Claude would know (what an indexer does, why faster than RPC). The 'When to Use This Skill' section is redundant. However, most code examples are lean and practical.	2 / 3
Actionability	Provides fully executable commands and code examples throughout - bash commands for starting Torii, complete GraphQL queries, TypeScript client integration code, and SQL examples. All are copy-paste ready with realistic syntax.	3 / 3
Workflow Clarity	The Development Workflow section provides clear sequencing across terminals, but lacks validation checkpoints. No verification steps to confirm Torii is indexing correctly, no feedback loops for common failure scenarios, and troubleshooting is reactive rather than integrated into the workflow.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but the document is quite long (~250 lines) with detailed API examples that could be split into separate reference files. References to related skills and external docs exist but the main file contains too much inline detail.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: 15 days ago

Table of Contents

Discovery Implementation Validation

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.