Admin
yc-software/qm
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress)…
Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-views --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OrchardCMS/OrchardCore.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/orchardcore-admin-edit-views .claude/skills/orchardcore-admin-edit-views && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "orchardcore-admin-edit-views" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-views into .claude/skills/orchardcore-admin-edit-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-admin-edit-views", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-viewsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-views --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchardCMS/OrchardCore.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/orchardcore-admin-edit-views .agents/skills/orchardcore-admin-edit-views && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchardcore-admin-edit-views" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-views into .agents/skills/orchardcore-admin-edit-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-admin-edit-views", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-views --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchardCMS/OrchardCore.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/orchardcore-admin-edit-views .cursor/skills/orchardcore-admin-edit-views && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orchardcore-admin-edit-views" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-views into .cursor/skills/orchardcore-admin-edit-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-admin-edit-views", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OrchardCMS/OrchardCore.git --path .agents/skills/orchardcore-admin-edit-views--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-views --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchardCMS/OrchardCore.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/orchardcore-admin-edit-views .gemini/skills/orchardcore-admin-edit-views && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orchardcore-admin-edit-views" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-views into .gemini/skills/orchardcore-admin-edit-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-admin-edit-views", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-viewsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OrchardCMS/OrchardCore.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/orchardcore-admin-edit-views .github/skills/orchardcore-admin-edit-views && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orchardcore-admin-edit-views" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-views into .github/skills/orchardcore-admin-edit-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-admin-edit-views", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-views --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OrchardCMS/OrchardCore.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/orchardcore-admin-edit-views .opencode/skills/orchardcore-admin-edit-views && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orchardcore-admin-edit-views" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-admin-edit-views into .opencode/skills/orchardcore-admin-edit-views/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-admin-edit-views", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
orchardcore-admin-edit-viewsCreates and updates OrchardCore admin edit views using the ocat- CSS class conventions.
Orchardcore Admin Edit Views is an agent skill from OrchardCMS/OrchardCore. Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions. Use when creating or modifying Edit view files (.Edit.cshtml, .Fields.Edit.cshtml) to ensure correct layout and styling.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/ocat-classes.md`).
The repository describes itself as: Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework. The licence is BSD-3-Clause.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d6bb7b4. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are html).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Orchardcore Admin Edit Views loads about 3.7k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 619 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from OrchardCMS/OrchardCore at commit d6bb7b4, republished under its BSD-3-Clause licence (© OrchardCMS). 619 words, ~3,746 tokens.
.claude/skills/orchardcore-admin-edit-views/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.This skill guides you through creating and updating admin edit view files using the ocat-* CSS class conventions required by the OrchardCore admin theme.
ocat-* CSS Class SystemThe ocat-* CSS classes provide a standardized two-column layout for admin form fields. Every form field uses a consistent structure:
ocat-label)ocat-end)| Class | Element | Purpose |
|---|---|---|
ocat-wrapper | <div> | Outer container for a form field row (replaces mb-3/form-group) |
ocat-label | <label> | Styles the field label in the left column (replaces form-label) |
ocat-label-required | <label> | Add alongside ocat-label to mark a field as required |
ocat-end | <div> | Wraps the input, validation, and hint in the right column |
ocat-end-offset | <div> | Right-column content with no left label (e.g., checkboxes) |
ocat-limited-wrapper | <div> | Outer row for limited-width controls such as short text, numbers, selects, or small settings inputs |
ocat-limited | <div> | Constrains the control width inside ocat-limited-wrapper |
Use this decision guide when creating or updating admin edit views:
| Scenario | Preferred Pattern |
|---|---|
| Standard full-width field row | ocat-wrapper + ocat-label + ocat-end |
| Standalone checkbox/toggle row with no left label | ocat-wrapper + ocat-end-offset |
| Standalone alert, notice, legend, or section headline in the form flow | ocat-wrapper + ocat-end-offset |
| Top-level limited-width field row (small text, number, select, token, path, port, etc.) | ocat-limited-wrapper + ocat-label + ocat-limited |
Content part / content field editor that already needs wrapper classes like field-wrapper-* or content-part-wrapper-* | Keep the outer ocat-wrapper, then place ocat-limited-wrapper inside ocat-end |
ocat-wrapper for the default admin edit-view row structure.ocat-limited-wrapper when the field should stay visually narrow instead of stretching the full editor width.field-wrapper-* or content-part-wrapper-*, do not replace that outer row with ocat-limited-wrapper; keep the outer ocat-wrapper and nest ocat-limited-wrapper inside ocat-end.mb-3, form-group, form-label, @Orchard.GetWrapperClasses(), or @Orchard.GetLimitedWidthWrapperClasses().<legend>, and section headings that are part of the edit form but have no left-column label should use their own ocat-wrapper + ocat-end-offset row.ocat-end or ocat-end-offset, never both.<div class="ocat-wrapper" asp-validation-class-for="FieldName">
<label asp-for="FieldName" class="ocat-label">@T["Label Text"]</label>
<div class="ocat-end">
<input asp-for="FieldName" class="form-control" />
<span asp-validation-for="FieldName"></span>
<span class="hint">@T["Descriptive hint text."]</span>
</div>
</div><div class="ocat-wrapper" asp-validation-class-for="FieldName">
<label asp-for="FieldName" class="ocat-label">@T["Label"]</label>
<div class="ocat-end">
<input asp-for="FieldName" class="form-control" />
<span asp-validation-for="FieldName"></span>
<span class="hint">@T["Hint text."]</span>
</div>
</div><div class="ocat-wrapper" asp-validation-class-for="FieldName">
<label asp-for="FieldName" class="ocat-label ocat-label-required">@T["Label"]</label>
<div class="ocat-end">
<input asp-for="FieldName" class="form-control" />
<span asp-validation-for="FieldName"></span>
<span class="hint">@T["Hint text."]</span>
</div>
</div><div class="ocat-wrapper" asp-validation-class-for="Expression">
<label asp-for="Expression" class="ocat-label">@T["Expression"]</label>
<div class="ocat-end">
<input type="text" asp-for="Expression" class="form-control code" />
<span asp-validation-for="Expression"></span>
<span class="hint">@T["A JavaScript expression. Example: {0}", "input(\"Count\") > 0"]</span>
</div>
</div><div class="ocat-wrapper" asp-validation-class-for="Content">
<label asp-for="Content" class="ocat-label">@T["Content"]</label>
<div class="ocat-end">
<textarea asp-for="Content" class="form-control" rows="5"></textarea>
<span asp-validation-for="Content"></span>
<span class="hint">@T["Hint text."]</span>
</div>
</div><div class="ocat-wrapper" asp-validation-class-for="FieldName">
<label asp-for="FieldName" class="ocat-label">@T["Label"]</label>
<div class="ocat-end">
<select asp-for="FieldName" class="form-select">
<option value="Option1">@T["Option 1"]</option>
<option value="Option2">@T["Option 2"]</option>
</select>
<span asp-validation-for="FieldName"></span>
<span class="hint">@T["Hint text."]</span>
</div>
</div>Use ocat-end-offset when there is no label in the left column (e.g., for checkboxes):
<div class="ocat-wrapper" asp-validation-class-for="IsEnabled">
<div class="ocat-end-offset">
<div class="form-check">
<input type="checkbox" class="form-check-input" asp-for="IsEnabled" />
<label asp-for="IsEnabled" class="form-check-label">@T["Enable feature"]</label>
</div>
<span class="hint dashed">@T["Check to enable this feature."]</span>
</div>
</div>Use this for standalone form guidance, warnings, legends, or section headers:
<div class="ocat-wrapper">
<div class="ocat-end-offset">
<h5>@T["Section heading"]</h5>
<div class="alert alert-warning" role="alert">
@T["Important information for editors."]
</div>
</div>
</div><div class="ocat-wrapper" asp-validation-class-for="Url">
<label asp-for="Url" class="ocat-label">@T["URL"]</label>
<div class="ocat-end">
<div class="input-group">
<span class="input-group-text">https://</span>
<input asp-for="Url" type="text" class="form-control" />
</div>
<span asp-validation-for="Url"></span>
<span class="hint">@T["The full URL."]</span>
</div>
</div>Use this when the whole row is a compact admin field, such as a page size, port, callback path, or select list:
<div class="ocat-limited-wrapper" asp-validation-class-for="PageSize">
<label asp-for="PageSize" class="ocat-label">@T["Page size"]</label>
<div class="ocat-limited">
<input asp-for="PageSize" type="number" class="form-control" />
<span asp-validation-for="PageSize"></span>
<span class="hint">@T["The default page size."]</span>
</div>
</div><div class="ocat-limited-wrapper" asp-validation-class-for="TimeZone">
<label asp-for="TimeZone" class="ocat-label">@T["Default Time Zone"]</label>
<div class="ocat-limited">
<select asp-for="TimeZone" class="form-select">
<option value="">@T["Local to server"]</option>
</select>
<span asp-validation-for="TimeZone"></span>
<span class="hint">@T["Determines the default time zone."]</span>
</div>
</div>Use this when the editor already needs a content field or content part wrapper on the outer row:
<div class="@($"ocat-wrapper field-wrapper field-wrapper-{Model.PartFieldDefinition.PartDefinition.Name.HtmlClassify()}-{Model.PartFieldDefinition.Name.HtmlClassify()}")">
<label asp-for="Value" class="ocat-label">@T["Value"]</label>
<div class="ocat-end">
<div class="ocat-limited-wrapper">
<div class="ocat-limited">
<input asp-for="Value" class="form-control" />
<span asp-validation-for="Value"></span>
</div>
</div>
<span class="hint">@T["Use a compact editor width while preserving the field wrapper row."]</span>
</div>
</div>For fields that support both JavaScript and Liquid syntax, use the syntax selector pattern with toggling d-none:
<div class="ocat-wrapper" asp-validation-class-for="Syntax">
<label asp-for="Syntax" class="ocat-label">@T["Syntax"]</label>
<div class="ocat-end">
<select asp-for="Syntax" class="form-select">
<option value="@nameof(WorkflowScriptSyntax.JavaScript)">@T["JavaScript"]</option>
<option value="@nameof(WorkflowScriptSyntax.Liquid)">@T["Liquid"]</option>
</select>
<span asp-validation-for="Syntax"></span>
</div>
</div>
<div id="@(Html.IdFor(m => m.Expression))_group" class="ocat-wrapper @(Model.Syntax == WorkflowScriptSyntax.JavaScript ? "" : "d-none")" asp-validation-class-for="Expression">
<label asp-for="Expression" class="ocat-label">@T["Expression"]</label>
<div class="ocat-end">
<input type="text" asp-for="Expression" class="form-control code" />
<span asp-validation-for="Expression"></span>
<span class="hint">@T["A JavaScript expression. Example: {0}", "input(\"Count\") > 0"]</span>
</div>
</div>
<div id="@(Html.IdFor(m => m.LiquidExpression))_group" class="ocat-wrapper @(Model.Syntax == WorkflowScriptSyntax.Liquid ? "" : "d-none")" asp-validation-class-for="LiquidExpression">
<label asp-for="LiquidExpression" class="ocat-label">@T["Expression"]</label>
<div class="ocat-end">
<input type="text" asp-for="LiquidExpression" class="form-control code" />
<span asp-validation-for="LiquidExpression"></span>
<span class="hint">@T["A Liquid expression. Example: {0}", "{{ Workflow.Properties.Value }}"]</span>
</div>
</div>
<script at="Foot">
document.addEventListener('DOMContentLoaded', () => {
const syntaxElement = document.getElementById('@Html.IdFor(m => m.Syntax)');
const javaScriptGroup = document.getElementById('@($"{Html.IdFor(m => m.Expression)}_group")');
const liquidGroup = document.getElementById('@($"{Html.IdFor(m => m.LiquidExpression)}_group")');
const toggleEditors = () => {
const useLiquid = syntaxElement.value === '@nameof(WorkflowScriptSyntax.Liquid)';
javaScriptGroup.classList.toggle('d-none', useLiquid);
liquidGroup.classList.toggle('d-none', !useLiquid);
};
syntaxElement.addEventListener('change', toggleEditors);
toggleEditors();
});
</script>For displaying information without a form input:
<div class="ocat-wrapper">
<label class="ocat-label">@T["Field Label"]</label>
<div class="ocat-end">
<span>@Model.FieldValue</span>
</div>
</div>When updating existing views, apply these replacements:
| Old Pattern | New Pattern |
|---|---|
<div class="mb-3" ...> | <div class="ocat-wrapper" ...> |
<div class="form-group" ...> | <div class="ocat-wrapper" ...> |
<label ... class="form-label"> | <label ... class="ocat-label"> |
| Input/select/textarea directly inside wrapper | Wrap in <div class="ocat-end"> |
| Checkbox with label inside wrapper | Wrap in <div class="ocat-end-offset"><div class="form-check"> |
| Standalone headline or alert directly in the form flow | Wrap in <div class="ocat-wrapper"><div class="ocat-end-offset">...</div></div> |
Mixing ocat-end and ocat-end-offset in one row | Choose one wrapper based on whether there is a left-column label |
@Orchard.GetLimitedWidthWrapperClasses() | ocat-limited-wrapper |
@Orchard.GetLimitedWidthClasses() | ocat-limited |
Limited-width content field row using field-wrapper-* | Keep outer ocat-wrapper field-wrapper-*, nest ocat-limited-wrapper inside ocat-end |
@model MyModuleViewModel
<div class="ocat-wrapper" asp-validation-class-for="Title">
<label asp-for="Title" class="ocat-label ocat-label-required">@T["Title"]</label>
<div class="ocat-end">
<input asp-for="Title" class="form-control" autofocus="autofocus" />
<span asp-validation-for="Title"></span>
<span class="hint">@T["The title of the item."]</span>
</div>
</div>
<div class="ocat-wrapper" asp-validation-class-for="Description">
<label asp-for="Description" class="ocat-label">@T["Description"]</label>
<div class="ocat-end">
<textarea asp-for="Description" class="form-control" rows="4"></textarea>
<span asp-validation-for="Description"></span>
<span class="hint">@T["A brief description."]</span>
</div>
</div>
<div class="ocat-wrapper" asp-validation-class-for="Category">
<label asp-for="Category" class="ocat-label">@T["Category"]</label>
<div class="ocat-end">
<select asp-for="Category" class="form-select">
<option value="">@T["-- Select --"]</option>
<option value="A">@T["Category A"]</option>
<option value="B">@T["Category B"]</option>
</select>
<span asp-validation-for="Category"></span>
</div>
</div>
<div class="ocat-wrapper" asp-validation-class-for="IsPublished">
<div class="ocat-end-offset">
<div class="form-check">
<input type="checkbox" class="form-check-input" asp-for="IsPublished" />
<label asp-for="IsPublished" class="form-check-label">@T["Published"]</label>
</div>
<span class="hint dashed">@T["Check to publish this item."]</span>
</div>
</div>references/ocat-classes.md - Detailed class reference with CSS contextsrc/OrchardCore.Themes/TheAdmin/src/OrchardCore.Modules/OrchardCore.Workflows/Views/Items/© OrchardCMS, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in .agents/skills/orchardcore-admin-edit-views of OrchardCMS/OrchardCore.
Open the folder on GitHubat commit d6bb7b4
Orchardcore Admin Edit Views next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orchardcore Admin Edit Views this skillOrchardCMS/OrchardCore | 8.2k | — | ~3.7k | Automated safety check: Pass | BSD-3-Clause | |
| Adminyc-software/qm | 15k | — | ~3.1k | Automated safety check: Pass | MIT | |
| CSS Minificationthedaviddias/Front-End-Checklist | 74k | — | ~415 | Automated safety check: Pass | MIT | |
| CSS Orderthedaviddias/Front-End-Checklist | 74k | — | ~404 | Automated safety check: Pass | MIT | |
| Unused CSSthedaviddias/Front-End-Checklist | 74k | — | ~415 | Automated safety check: Pass | MIT | |
| CSS Criticalthedaviddias/Front-End-Checklist | 74k | — | ~441 | Automated safety check: Pass | MIT |
yc-software/qm
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress)…
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Minify all CSS files.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Order CSS files correctly.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Remove unused CSS rules.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Inline critical CSS for faster rendering.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use a CSS reset or normalize stylesheet.
OrchardCMS/OrchardCore
Builds, watches, and manages frontend assets in OrchardCore.
OrchardCMS/OrchardCore
Creates and updates OrchardCore data migrations (DataMigration classes with CreateAsync/UpdateFromX).
OrchardCMS/OrchardCore
Controls how OrchardCore renders content — placement.json rules, display drivers, shapes, zones, alternates, and editor groupings (tabs/cards/columns).
OrchardCMS/OrchardCore
Authors OrchardCore documentation — MkDocs Material pages, module README docs, nav entries, admonitions, tabbed content, and redirects.
OrchardCMS/OrchardCore
Localizes OrchardCore apps — UI strings (IStringLocalizer/IViewLocalizer S, T, H), PO files and pluralization, content translation (LocalizationPart, culture picker), and supported-culture…
OrchardCMS/OrchardCore
Creates new OrchardCore modules with proper structure, manifest, startup, and patterns.
Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions. Orchardcore Admin Edit Views is an agent skill from OrchardCMS/OrchardCore. Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions.
Orchardcore Admin Edit Views fits situations like: modifying Edit view files (.Edit.cshtml; .Fields.Edit.cshtml) to ensure correct layout and styling.
Run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a claude-code`. Or copy the skill folder (.agents/skills/orchardcore-admin-edit-views in OrchardCMS/OrchardCore) into .claude/skills/orchardcore-admin-edit-views in your project. Claude Code loads it when a task matches its description.
Run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a codex`. Or copy the skill folder (.agents/skills/orchardcore-admin-edit-views in OrchardCMS/OrchardCore) into .agents/skills/orchardcore-admin-edit-views in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchardcore-admin-edit-views, .gemini/skills/orchardcore-admin-edit-views, .github/skills/orchardcore-admin-edit-views and .opencode/skills/orchardcore-admin-edit-views in your project.
SKILL.md names no scripts, command-line tools or credentials: Orchardcore Admin Edit Views is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Orchardcore Admin Edit Views is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Orchardcore Admin Edit Views: Admin (yc-software/qm, 15k stars), CSS Minification (thedaviddias/Front-End-Checklist, 74k stars), CSS Order (thedaviddias/Front-End-Checklist, 74k stars) and Unused CSS (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
OrchardCMS (a GitHub organization) maintains it in OrchardCMS/OrchardCore, which has 8,195 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 8, 2026.
Source: OrchardCMS/OrchardCore on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.