CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orchardcore-tester

Tests OrchardCore CMS features through browser automation. Use when the user needs to build, run, setup, or test OrchardCore functionality including admin features, content management, media library, and module testing.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

The skill body is excellent: executable end-to-end commands, a well-sequenced workflow with validation at every phase, and clean one-level-deep reference files confirmed to exist and hold real content. The only slack is modest duplication between the TL;DR and the detailed steps, and dual-shell command variants.

Suggestions

Have the TL;DR reference Step 2's run/poll details instead of re-inlining the full env-var block twice, keeping the fast path to a few lines.

Give the PowerShell ready-poll loop an explicit timeout-failure branch (it currently exits the while loop silently when 60s elapse) and mirror it in bash so the wait-and-fail behavior is symmetric.

DimensionReasoningScore

Conciseness

The body is command-dominated with tight annotations and no explanations of concepts Claude already knows. Minor trim opportunities exist: the TL;DR duplicates Steps 2–3, and both PowerShell and bash variants double several blocks (though the cross-shell note justifies this) — matching the score-4 anchor of minor over-content that could be trimmed.

4 / 5

Actionability

Fully executable copy-paste commands throughout: exact dotnet build/run invocations, the complete AutoSetup env-var block, concrete curl/grep confirmations, the exact native-setter eval expression with a specific selector, and real admin URL paths. The <username-ref> placeholders are inherent to the playwright-cli snapshot workflow and explicitly explained, matching the score-5 anchor.

5 / 5

Workflow Clarity

A clear 5-step sequence (Build → Run → Setup → Test → Verify) with explicit validation checkpoints at every fragile point: ready-polling, grep for the provisioning log line, login verified via the /Admin pathname, console error checks, and log-file error search with a debugging reference for error recovery — the score-5 anchor. The destructive rm -rf App_Data reset is scoped and followed by re-validation, so no cap applies.

5 / 5

Progressive Disclosure

Clear overview structure (TL;DR → steps → quick-reference tables) with all six references/*.md files verified to exist as real, one-level-deep files containing actual content rather than pointer chains. Each is signaled inline at the point of need and listed in a descriptive References index — the score-5 anchor.

5 / 5

Total

19

/

20

Passed

Description

82%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.

The description is strong: explicit what-and-when structure with concrete trigger verbs anchored to a distinctive product name. Its only weakness is that the capability description relies on one action verb plus a scope enumeration rather than several distinct concrete actions.

Suggestions

Replace the scope enumeration ("including admin features, content management, media library, and module testing") with distinct concrete actions, e.g. "Tests OrchardCore CMS features via browser automation: builds and runs the app, provisions a test site, and drives admin, content, and media workflows."

Add common user synonyms such as "debug" or "verify" alongside "build, run, setup, or test" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Tests OrchardCore CMS features through browser automation" names the domain and one concrete action mechanism, then enumerates scope areas ("admin features, content management, media library, and module testing") — but these are scope enumeration rather than a list of several distinct concrete actions, matching the score-3 anchor rather than 4.

3 / 5

Completeness

It explicitly answers "what" ("Tests OrchardCore CMS features through browser automation") and "when" ("Use when the user needs to build, run, setup, or test OrchardCore functionality...") with concrete trigger verbs, matching the score-5 anchor.

5 / 5

Trigger Term Quality

"build, run, setup, or test OrchardCore functionality" plus "admin features, content management, media library" are natural phrases users would say, but common synonyms like "debug", "verify", or "CMS" are missing — good coverage with a few natural terms absent, matching the score-4 anchor.

4 / 5

Distinctiveness Conflict Risk

"OrchardCore" is a distinctive named product with triggers specific to this niche, so the description is clearly distinguishable from other skills with minimal conflict risk — the score-5 anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

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-tester/SKILL.md

Reviewed

Table of Contents

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.