orchardcore-display-management

Controls how OrchardCore renders content — placement.json rules, display drivers, shapes, zones, alternates, and editor groupings (tabs/cards/columns). Use when the user needs to position or hide a part/field, move a shape to another zone, add alternates or wrappers, build admin editor layouts, or write a display driver.

Quality

86%

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

84%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: executable code, lookup tables, and two clearly signaled reference files keep the overview lean while details live one level deep. Only minor conciseness and validation-checkpoint gaps prevent top marks.

Suggestions

Add an explicit validation/feedback step to Workflow B (e.g. 'build the module and confirm the new shape appears in shape tracing before relying on placement') to match the verify step in Workflow A.

Tighten the driver-vs-placement section by either relying on the decision table or the trailing one-liner, avoiding the slight restatement of the same guidance.

Consider listing the two reference files once in a dedicated 'References' intro pointer rather than only inline, so the available bundle is discoverable up front.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich with almost no padding of concepts Claude already knows; minor instances of slightly redundant explanation (e.g. re-stating the driver-vs-placement guidance in both the table and the sentence after it) keep it just shy of perfectly lean.	4 / 5
Actionability	Provides copy-paste-ready code (full TextFieldDisplayDriver with Display/Edit/UpdateAsync, Startup registration) and concrete placement.json snippets, plus precise lookup tables (placement keys, position values, grouping modifiers) that cover the common cases with executable specifics.	5 / 5
Workflow Clarity	Workflows A and B are clearly sequenced with numbered steps and a verify step in Workflow A (run the site, use ?display/shape tracing), but Workflow B (writing a driver) lacks an explicit validation checkpoint and the destructive-cap cap note does not apply since driver authorship is not a destructive/batch operation; minor validation gap keeps it at 4.	4 / 5
Progressive Disclosure	SKILL.md is a well-organized overview that points to two real one-level-deep references (references/placement.md, references/drivers.md) with inline pointers at the relevant steps, and lists repo docs separately; bundle files confirmed present and appropriately scoped, with navigation clearly signaled.	5 / 5
	Total	18 / 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, specific description that clearly states what the skill controls and gives an explicit, multi-trigger 'Use when' clause. Voice is appropriately third person and buzzword-free; only minor synonym coverage is missing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (placement.json rules, display drivers, shapes, zones, alternates, editor groupings) and enumerates specific triggers (position/hide a part/field, move a shape to another zone, add alternates/wrappers, build admin editor layouts, write a display driver), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (controls how OrchardCore renders content via placement.json, drivers, shapes, zones, alternates, editor groupings) and 'when' with a concrete 'Use when the user needs to...' trigger clause enumerating several scenarios.	5 / 5
Trigger Term Quality	Includes natural user phrases like 'position or hide a part/field', 'move a shape to another zone', and 'add alternates or wrappers', plus concrete artifact names (placement.json, display drivers, shapes, zones); a few common phrasings a user might say (e.g. 'reorder fields', 'change template') are implied rather than surfaced as synonyms.	4 / 5
Distinctiveness Conflict Risk	The OrchardCore display-management niche is highly specific, with named subsystems (placement.json, display drivers, shapes/zones, alternates) that are unlikely to collide with other skills; trigger phrases are tightly scoped to rendering/layout tasks.	5 / 5
	Total	19 / 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-display-management/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.