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.

1.36x

Quality

75%

Does it follow best practices?

Impact

100%

1.36x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/dojo-indexer/SKILL.md

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 a strong skill description that clearly identifies the specific tool (Torii indexer), lists concrete capabilities (GraphQL, gRPC, SQL), and provides explicit trigger guidance via a 'Use when' clause. The only minor issue is the use of second person ('your deployed world') which the rubric notes should be penalized, but the description is otherwise well-constructed and distinctive.

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, concrete 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 an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Torii', 'indexer', 'GraphQL', 'gRPC', 'SQL', 'subscriptions', 'queries', 'real-time updates', 'deployed world', 'client queries'. Good coverage of domain-specific terms.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific technology references (Torii indexer, deployed world) that clearly carve out a niche. Unlikely to conflict with generic database or API skills due to the domain-specific terminology.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

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

The skill provides comprehensive, actionable coverage of Torii indexer setup and usage with excellent executable examples across GraphQL, SQL, TypeScript, and bash. However, it is significantly bloated with explanatory content Claude doesn't need (what an indexer is, why it's useful), redundant sections, and would benefit greatly from splitting detailed reference material into separate files while keeping the SKILL.md as a lean overview with navigation.

Suggestions

Remove the 'What is Torii?', 'When to Use This Skill', and 'What This Skill Does' sections — Claude doesn't need to be told what an indexer does or why it's useful.

Move detailed GraphQL query examples, subscription examples, and client integration code into separate reference files (e.g., GRAPHQL.md, SUBSCRIPTIONS.md, CLIENT.md) and link to them from a concise overview.

Add validation checkpoints to the Development Workflow: e.g., 'Verify Torii is running: curl http://localhost:8080/graphql' after starting Torii, and a health check before proceeding to client integration.

Remove the 'Next Steps' and 'Related Skills' sections or compress them into a single line of cross-references to reduce token waste.

Dimension	Reasoning	Score
Conciseness	The skill is very verbose with sections like 'What is Torii?' explaining concepts Claude already knows (what an indexer does, why it's faster than RPC), 'When to Use This Skill' and 'What This Skill Does' sections that repeat information, and a 'Next Steps' section that adds little value. The 'Why use Torii' bullet list is unnecessary context padding.	1 / 3
Actionability	The skill provides fully executable code examples across multiple languages and tools: bash commands for starting Torii, complete GraphQL queries, SQL examples, TypeScript client integration code, and TOML configuration files. All examples are copy-paste ready with realistic syntax.	3 / 3
Workflow Clarity	The Development Workflow section provides a clear 3-terminal sequence, and the Slot Deployment section has ordered steps. However, there are no validation checkpoints — no steps to verify Torii is running correctly, no health check commands, and no feedback loops for error recovery during setup. The troubleshooting section is separate rather than integrated into the workflow.	2 / 3
Progressive Disclosure	The content is mostly monolithic — extensive GraphQL examples, client integration code, and configuration details are all inline rather than split into separate reference files. There's one external reference to the Torii configuration guide, but the bulk of content (pagination examples, subscription examples, client integration) could be better organized into separate files with clear navigation links.	2 / 3
	Total	8 / 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

Repository: dojoengine/book
Commit: 52a1507

Reviewed: 3 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.