Agent skill

Orchardcore Admin Edit Views

by OrchardCMS in OrchardCMS/OrchardCore

Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions.

BSD-3-ClauseAuto-check passed

Install Orchardcore Admin Edit Views

skills CLI
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-admin-edit-views -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OrchardCMS/OrchardCore orchardcore-admin-edit-views --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
orchardcore-admin-edit-views
GitHub stars
8.2k
Token cost
~3.7k tokens
SKILL.md length
619 words
Files
2 (incl. references)
Skills in repo
16
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions.

  • Works in 6 steps: Use ocat-wrapper for the default admin… → Use ocat-limited-wrapper when the field… → If the outer row also needs… → …
  • Modifying Edit view files (.Edit.cshtml
  • SKILL.md covers The ocat-* CSS Class System, Choosing the Right Wrapper, Field Type Templates and Display-Only Fields (Read-Only), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • Modifying Edit view files (.Edit.cshtml
  • .Fields.Edit.cshtml) to ensure correct layout and styling

Example prompts

  • “Use the orchardcore-admin-edit-views skill to create and updates OrchardCore admin edit views using the ocat- CSS class conventions”
  • “/orchardcore-admin-edit-views”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Use ocat-wrapper for the default admin edit-view row structure.
  2. Use ocat-limited-wrapper when the field should stay visually narrow instead of stretching the full editor width.
  3. If the outer row also needs Orchard-specific wrapper classes such as field-wrapper-* or content-part-wrapper-*, do not replace that outer…
  4. Do not use legacy helpers or Bootstrap-only layout classes like mb-3, form-group, form-label, @Orchard.GetWrapperClasses(), or…
  5. Alerts, notices, , and section headings that are part of the edit form but have no left-column label should use their own ocat-wrapper +…
  6. A single row should use either ocat-end or ocat-end-offset, never both.

What it can do on your machine

Read from SKILL.md and the folder at commit d6bb7b4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from OrchardCMS/OrchardCore at commit d6bb7b4, republished under its BSD-3-Clause licence (© OrchardCMS). 619 words, ~3,746 tokens.

Download SKILL.mdSave it as .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.
name
orchardcore-admin-edit-views
description
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.
status
completed

OrchardCore Admin Edit Views

This skill guides you through creating and updating admin edit view files using the ocat-* CSS class conventions required by the OrchardCore admin theme.

The ocat-* CSS Class System

The ocat-* CSS classes provide a standardized two-column layout for admin form fields. Every form field uses a consistent structure:

  • Left column – The field label (ocat-label)
  • Right column – The input, validation message, and hint (ocat-end)
Core Classes
ClassElementPurpose
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

Choosing the Right Wrapper

Use this decision guide when creating or updating admin edit views:

ScenarioPreferred Pattern
Standard full-width field rowocat-wrapper + ocat-label + ocat-end
Standalone checkbox/toggle row with no left labelocat-wrapper + ocat-end-offset
Standalone alert, notice, legend, or section headline in the form flowocat-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
Wrapper Selection Rules
  1. Use ocat-wrapper for the default admin edit-view row structure.
  2. Use ocat-limited-wrapper when the field should stay visually narrow instead of stretching the full editor width.
  3. If the outer row also needs Orchard-specific wrapper classes such as 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.
  4. Do not use legacy helpers or Bootstrap-only layout classes like mb-3, form-group, form-label, @Orchard.GetWrapperClasses(), or @Orchard.GetLimitedWidthWrapperClasses().
  5. Alerts, notices, <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.
  6. A single row should use either ocat-end or ocat-end-offset, never both.
Standard Field Structure
html
<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>

Field Type Templates

Text Input
html
<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>
Required Text Input
html
<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>
Code/Script Input
html
<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>
Textarea
html
<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>
Select / Dropdown
html
<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>
Show full SKILL.md (247 more words)Show less
Checkbox (No Left Label)

Use ocat-end-offset when there is no label in the left column (e.g., for checkboxes):

html
<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>
Headline / Alert Row (No Left Label)

Use this for standalone form guidance, warnings, legends, or section headers:

html
<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>
Input Group (with prefix/suffix)
html
<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>
Limited-Width Field Row

Use this when the whole row is a compact admin field, such as a page size, port, callback path, or select list:

html
<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>
Limited-Width Select Row
html
<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>
Limited-Width Control Inside a Field Wrapper

Use this when the editor already needs a content field or content part wrapper on the outer row:

html
<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>
Conditional Fields with JavaScript/Liquid Syntax Selector

For fields that support both JavaScript and Liquid syntax, use the syntax selector pattern with toggling d-none:

html
<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>

Display-Only Fields (Read-Only)

For displaying information without a form input:

html
<div class="ocat-wrapper">
    <label class="ocat-label">@T["Field Label"]</label>
    <div class="ocat-end">
        <span>@Model.FieldValue</span>
    </div>
</div>

Migration: Old to New Classes

When updating existing views, apply these replacements:

Old PatternNew 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 wrapperWrap in <div class="ocat-end">
Checkbox with label inside wrapperWrap in <div class="ocat-end-offset"><div class="form-check">
Standalone headline or alert directly in the form flowWrap in <div class="ocat-wrapper"><div class="ocat-end-offset">...</div></div>
Mixing ocat-end and ocat-end-offset in one rowChoose 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

Complete Edit View Example

html
@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

  • references/ocat-classes.md - Detailed class reference with CSS context
  • Admin theme source: src/OrchardCore.Themes/TheAdmin/
  • Example usage: src/OrchardCore.Modules/OrchardCore.Workflows/Views/Items/
  • AGENTS.md (repo root) - Coding conventions and build commands

© 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

Files

SKILL.md and 1 other file (references) in .agents/skills/orchardcore-admin-edit-views of OrchardCMS/OrchardCore.

  • SKILL.md
  • references/ocat-classes.md

Open the folder on GitHubat commit d6bb7b4

Compare with similar skills

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.

Orchardcore Admin Edit Views compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Orchardcore Admin Edit Views this skillOrchardCMS/OrchardCore8.2k—~3.7kAutomated safety check: PassBSD-3-Clause
Adminyc-software/qm15k—~3.1kAutomated safety check: PassMIT
CSS Minificationthedaviddias/Front-End-Checklist74k—~415Automated safety check: PassMIT
CSS Orderthedaviddias/Front-End-Checklist74k—~404Automated safety check: PassMIT
Unused CSSthedaviddias/Front-End-Checklist74k—~415Automated safety check: PassMIT
CSS Criticalthedaviddias/Front-End-Checklist74k—~441Automated safety check: PassMIT

Similar skills

  • 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)…

    15k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • CSS Minification

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Minify all CSS files.

    74k GitHub stars~415 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • CSS Order

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Order CSS files correctly.

    74k GitHub stars~404 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Unused CSS

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Remove unused CSS rules.

    74k GitHub stars~415 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • CSS Critical

    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.

    74k GitHub stars~441 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Reset CSS

    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.

    74k GitHub stars~415 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

More from OrchardCMS/OrchardCore

All 16 skills in this repo
  • Orchardcore Asset Manager

    OrchardCMS/OrchardCore

    Builds, watches, and manages frontend assets in OrchardCore.

    8.2k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Orchardcore Data Migration

    OrchardCMS/OrchardCore

    Creates and updates OrchardCore data migrations (DataMigration classes with CreateAsync/UpdateFromX).

    8.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Orchardcore Display Management

    OrchardCMS/OrchardCore

    Controls how OrchardCore renders content — placement.json rules, display drivers, shapes, zones, alternates, and editor groupings (tabs/cards/columns).

    8.2k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Orchardcore Docs Writer

    OrchardCMS/OrchardCore

    Authors OrchardCore documentation — MkDocs Material pages, module README docs, nav entries, admonitions, tabbed content, and redirects.

    8.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Orchardcore Localization

    OrchardCMS/OrchardCore

    Localizes OrchardCore apps — UI strings (IStringLocalizer/IViewLocalizer S, T, H), PO files and pluralization, content translation (LocalizationPart, culture picker), and supported-culture…

    8.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Orchardcore Module Creator

    OrchardCMS/OrchardCore

    Creates new OrchardCore modules with proper structure, manifest, startup, and patterns.

    8.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Questions about Orchardcore Admin Edit Views

What does Orchardcore Admin Edit Views do?

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.

When should I use Orchardcore Admin Edit Views?

Orchardcore Admin Edit Views fits situations like: modifying Edit view files (.Edit.cshtml; .Fields.Edit.cshtml) to ensure correct layout and styling.

How do I install Orchardcore Admin Edit Views in Claude Code?

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.

How do I install Orchardcore Admin Edit Views in Codex?

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.

Can I use Orchardcore Admin Edit Views in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Orchardcore Admin Edit Views need to run?

SKILL.md names no scripts, command-line tools or credentials: Orchardcore Admin Edit Views is instructions for the agent only.

Does Orchardcore Admin Edit Views access the network?

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.

Is Orchardcore Admin Edit Views safe to install?

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.

What licence does Orchardcore Admin Edit Views use?

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.

How many tokens does Orchardcore Admin Edit Views use?

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.

What are the alternatives to Orchardcore Admin Edit Views?

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.

Who maintains Orchardcore Admin Edit Views?

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.