orchardcore-unit-test

Writes and runs OrchardCore tests — xUnit unit tests, SiteContext-based integration tests, Moq mocking, and Playwright functional tests. Use when the user needs to add a test, set up a test harness/tenant for tests, mock OrchardCore services, or run the test suite.

Quality

89%

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

86%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, highly actionable testing skill with clear workflows and good progressive disclosure. The main improvements are removing minor Quick-Reference duplication and adding an explicit test-failure feedback loop.

Suggestions

Add a short 'If a test fails' feedback loop under Running tests (read the assertion failure → fix the code or test → rerun the filtered test → then the full project).

De-duplicate the Moq usage shown in Workflow A Step 2 against the Moq cheatsheet — keep one canonical example and cross-reference it.

Trim the opening 'This skill guides you through…' sentence, which restates the description without adding new information.

Dimension	Reasoning	Score
Conciseness	The body is lean, table-driven, and assumes Claude's competence (no 'xUnit is a framework…' preamble), but there is minor duplication between the Moq example in Workflow A and the Moq cheatsheet in Quick Reference that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready C# for unit, integration, and functional tests plus concrete run commands ('dotnet test test/OrchardCore.Tests/OrchardCore.Tests.csproj --filter …'), covering the common cases.	5 / 5
Workflow Clarity	A clear decision table feeds three sequenced, numbered workflows (A/B/C) with a Gotchas section, but there is no explicit failure→fix→rerun feedback loop for the test-run step, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The SKILL.md body is an overview with the deeper SiteContext internals, fixture details, and project layout correctly split into the one-level-deep, clearly-signaled references/testing.md (verified to exist).	5 / 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, third-person description that clearly states capabilities and provides explicit 'Use when' triggers. The only gap is trigger-term breadth — a few synonyms and file extensions would round it out.

Suggestions

Add natural synonyms and file extensions to the trigger clause (e.g. 'write/author tests', '.cs/.csproj test files', 'unit-test or integration-test an OrchardCore module').

Consider including a couple of user-style phrases like 'test my OrchardCore module' or 'set up a tenant for testing' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with comprehensive coverage — 'xUnit unit tests, SiteContext-based integration tests, Moq mocking, and Playwright functional tests' — matching the multiple-specific-actions anchor.	5 / 5
Completeness	Explicitly answers both what ('Writes and runs OrchardCore tests — …') and when ('Use when the user needs to add a test, set up a test harness/tenant for tests, mock OrchardCore services, or run the test suite') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('add a test', 'set up a test harness/tenant', 'mock OrchardCore services', 'run the test suite') are present, but it lacks common synonyms and file extensions, stopping short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Clearly niched to OrchardCore testing with distinct tooling triggers (SiteContext, Moq, Playwright), giving it minimal conflict risk 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-unit-test/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.