orchardcore-query-indexing

Works with OrchardCore queries and indexing — SQL/Lucene/Elasticsearch queries, full-text index profiles, content part/field index handlers, and search. Use when the user needs to define a query, index content for search, write an index handler, register an indexing source, or add query/index recipe steps.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

76%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with executable code and a clear one-level reference. The main weakness is the absence of validation/verification checkpoints around the destructive RebuildIndex/ResetIndex operations, which caps workflow clarity.

Suggestions

Add an explicit verification checkpoint after RebuildIndex/ResetIndex (e.g. check IIndexManager.ExistsAsync or query the index for a known item) before declaring the rebuild complete, and note the destructive 'drops all indexed documents' nature of RebuildIndex up front.

De-duplicate the AliasPartIndexHandler example between the body and references/indexing.md — keep the minimal pattern inline and point to the reference for the full handler/field variants to tighten conciseness and organization.

Trim the inline Quick Reference API tables to only the most-used members, or move the full API list entirely into references/indexing.md with a one-line pointer, to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Largely lean and token-efficient with tables and tight code blocks; no padding with concepts Claude already knows. Phrases like 'Two distinct systems, often confused' and 'SQL templates are Liquid-rendered ... parsed by SqlParser, then run via Dapper' add genuinely non-obvious domain detail rather than filler; mild handler-example duplication with references/indexing.md keeps it just below a 5.	4 / 5
Actionability	Copy-paste-ready recipe JSON and C# for creating/executing queries, implementing and registering part/field index handlers, and adding indexing sources; the common cases are covered with executable, complete code rather than pseudocode.	5 / 5
Workflow Clarity	Both workflows are clearly numbered and sequenced, but Step 4 (Reset/RebuildIndex) involves destructive and batch operations (drop + rebuild) with no validation or verification checkpoint, so workflow clarity is capped at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	Clear overview body with a well-signaled one-level reference (references/indexing.md) and a Quick Reference section; the bulk of the API surface is appropriately delegated. The inline Quick Reference API tables and a handler example duplicated in the reference file are minor organization gaps rather than a clean 5.	4 / 5
	Total	16 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capabilities and use-when triggers with concrete, domain-specific actions. Minor room to add boundary disambiguation against the data-migration skill and a few more natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'define a query, index content for search, write an index handler, register an indexing source, or add query/index recipe steps' — alongside named sources (SQL/Lucene/Elasticsearch) and component types, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (queries and indexing — SQL/Lucene/Elasticsearch, index profiles, handlers, search) and 'when' ('Use when the user needs to define a query, index content for search, write an index handler, register an indexing source, or add query/index recipe steps') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-domain keywords ('query', 'index content for search', 'index handler', 'recipe steps') but misses common synonyms and user-facing phrasings like 'search box', 'full-text search', or specific file/feature terms; solid but not exhaustive.	4 / 5
Distinctiveness Conflict Risk	The OrchardCore query/indexing niche is well-scoped with distinct triggers, but the bare term 'indexing' carries minor overlap risk with the related orchardcore-data-migration skill (YesSql MapIndex tables); the boundary is not stated in the description itself.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: OrchardCMS/OrchardCore
Path: .agents/skills/orchardcore-query-indexing/SKILL.md
Commit: b0e1e44

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.