orchardcore-docs-writer

Authors OrchardCore documentation — MkDocs Material pages, module README docs, nav entries, admonitions, tabbed content, and redirects. Use when the user needs to add or edit a docs page, document a new module, build/serve the docs site, or wire a page into the navigation.

Quality

91%

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

90%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 highly actionable, concise skill body with clear workflows and well-organized references. Adding an explicit validation/verification step to the workflows and moving more detail into the reference would push it to the top anchor.

Suggestions

Add an explicit verify step to Workflow A (e.g., after build, confirm the new page appears in nav and no build warning is emitted) to form a validate→fix→retry loop.

Trim the inlined Quick Reference / extensions detail into references/docs-structure.md (which already covers most of it) to shorten the SKILL.md body.

In Workflow B, add a checkpoint to verify the new module link resolves in the served site before considering the task complete.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — uses tables for page locations and toolchain, gives no padding or explanation of what MkDocs/Material are, and assumes Claude's competence throughout.	5 / 5
Actionability	Copy-paste ready executable commands (pip install, mkdocs serve/build), exact nav YAML format, module-header convention, redirect_maps syntax, and admonition/tabbed snippets cover the common cases.	5 / 5
Workflow Clarity	Two clear numbered workflows (write MD → add to nav → build/preview; new-module 4 steps) are well sequenced, but verification checkpoints are implicit rather than explicit validate→fix→retry loops.	4 / 5
Progressive Disclosure	Good structure with well-signaled one-level-deep references (docs-structure.md verified to exist) holding the bulk of the directory/nav detail, though the ~150-line body retains some content that could move to the reference.	4 / 5
	Total	18 / 20 Passed

Description

92%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 both capabilities and concrete trigger phrases tied to a distinct niche. Minor room to add file-extension synonyms for trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'MkDocs Material pages, module README docs, nav entries, admonitions, tabbed content, and redirects' — giving comprehensive coverage of what the skill authors.	5 / 5
Completeness	Explicitly answers both what (authors pages/READMEs/nav/admonitions/tabs/redirects) and when ('Use when the user needs to add or edit a docs page, document a new module, build/serve the docs site, or wire a page into the navigation').	5 / 5
Trigger Term Quality	Natural phrases users would say are present ('add or edit a docs page', 'document a new module', 'build/serve the docs site', 'wire a page into the navigation'), though file-extension synonyms like .md are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (OrchardCore documentation authoring) with distinct, project-specific triggers and minimal overlap with other skills.	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-docs-writer/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.