orchardcore-localization

Localizes OrchardCore apps — UI strings (IStringLocalizer/IViewLocalizer S, T, H), PO files and pluralization, content translation (LocalizationPart, culture picker), and supported-culture configuration. Use when the user needs to translate strings, add a culture, set up PO files, or make content items multilingual.

Quality

93%

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

93%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-organized, actionable, and token-efficient skill body that routes between three localization workflows with concrete code and delegates deep detail to a single real reference file. Adding explicit verify/validation steps in the workflows would lift workflow clarity to the top anchor.

Suggestions

Add explicit verification checkpoints to each workflow (e.g., 'Confirm the string now renders translated' after Step 3 of Workflow A, 'Verify the new culture appears in SupportedCultures before translating content into it') to reach the top workflow-clarity anchor.

Show the injection pattern for IContentLocalizationManager alongside the IStringLocalizer injection example so the content-localization code snippets are fully self-contained.

Consider moving the Quick Reference API tables into references/localization.md if the body grows, to keep SKILL.md purely an overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and reference-style — dense tables, copy-paste code blocks, and minimal prose — assuming Claude already knows PO files, Razor, Liquid, and IStringLocalizer, with no concept padding; every section earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready examples across all three workflows (localizer injection, S.Plural, PO entries, LocalizationPart, _contentLocalizationManager.LocalizeAsync, recipe JSON, Liquid filters) with quick-reference tables covering the common cases.	5 / 5
Workflow Clarity	Three clearly numbered workflows (A/B/C) with a routing table and a Gotchas checklist, but no explicit validation/verification checkpoints within the workflows; the operations are additive/config rather than destructive or batch, so the cap-at-3 does not apply.	4 / 5
Progressive Disclosure	A clear overview in SKILL.md with a single well-signaled one-level-deep reference (references/localization.md, verified present) linked inline and in a References section, with deep PO-discovery/startup detail appropriately split into the reference file.	5 / 5
	Total	19 / 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 names the platform and capability layers, gives an explicit 'Use when' trigger clause, and stays in third person. The only gap is missing natural synonyms and the .po extension in its trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities comprehensively across all three layers — 'UI strings (IStringLocalizer/IViewLocalizer S, T, H), PO files and pluralization, content translation (LocalizationPart, culture picker), and supported-culture configuration' — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly states both what ('Localizes OrchardCore apps — ...') and when ('Use when the user needs to translate strings, add a culture, set up PO files, or make content items multilingual') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural triggers ('translate strings, add a culture, set up PO files, or make content items multilingual') but missing synonyms ('localize', 'language') and the .po file extension, so it sits above 3 yet short of the comprehensive synonym/extension coverage at 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to the OrchardCore platform with localization-specific triggers, giving it a clear niche and 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-localization/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.