Vuetify Skilld
logue/vite-vuetify-ts-starter
Vue Material Component Framework. An agent skill from logue/vite-vuetify-ts-starter.
Builds, watches, and manages frontend assets in OrchardCore.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-asset-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-asset-manager --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-asset-manager .claude/skills/orchardcore-asset-manager && 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-asset-manager" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager into .claude/skills/orchardcore-asset-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-asset-manager", 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-asset-managerType 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-asset-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-asset-manager --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-asset-manager .agents/skills/orchardcore-asset-manager && 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-asset-manager" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager into .agents/skills/orchardcore-asset-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-asset-manager", 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-asset-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-asset-manager --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-asset-manager .cursor/skills/orchardcore-asset-manager && 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-asset-manager" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager into .cursor/skills/orchardcore-asset-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-asset-manager", 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-asset-manager--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-asset-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-asset-manager --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-asset-manager .gemini/skills/orchardcore-asset-manager && 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-asset-manager" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager into .gemini/skills/orchardcore-asset-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-asset-manager", 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-asset-managerInstalls 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-asset-manager -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-asset-manager .github/skills/orchardcore-asset-manager && 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-asset-manager" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager into .github/skills/orchardcore-asset-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-asset-manager", 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-asset-manager -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-asset-manager --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-asset-manager .opencode/skills/orchardcore-asset-manager && 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-asset-manager" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-asset-manager into .opencode/skills/orchardcore-asset-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-asset-manager", 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-asset-managerBuilds, watches, and manages frontend assets in OrchardCore.
Orchardcore Asset Manager is an agent skill from OrchardCMS/OrchardCore. Builds, watches, and manages frontend assets in OrchardCore. Use when modifying SCSS, JS, TS, or Vue files, adding new assets to a module/theme, or troubleshooting build failures. Covers all asset actions (vite, sass, min, copy, parcel, webpack, concat) and the three-tier package structure.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/actions.md`).
It sits in Frontend & Design, covering CSS and styling. It works with Vue.js, webpack, Node.js and npm. 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.
Read from SKILL.md and the folder at commit bfbe92f. 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.
Shell commands in SKILL.md call:
yarngitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use yarn and git, which can reach the network depending on how they are called.
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 Asset Manager loads about 1.5k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 476 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 bfbe92f, republished under its BSD-3-Clause licence (© OrchardCMS). 476 words, ~1,490 tokens.
.claude/skills/orchardcore-asset-manager/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Handles all frontend asset compilation for OrchardCore modules and themes. Assets are discovered via Assets.json files under src/{OrchardCore.Modules,OrchardCore.Themes}/*/.
The repo requires Node.js 24.x (pinned in .node-version). The build script auto-detects a mismatch and prompts:
1) Continue anyway
2) Abort
3) Install via fnm, Node.js 24.x and build
4) Install via Volta, Node.js 24.x and buildAlways select option 1 (continue) or option 3 (install via fnm). The allowed Bash commands for this project pre-approve both:
echo "1" | yarn build # continue with current Node.js
echo "3" | yarn build # install Node 24 via fnm and buildAll commands run from the repository root (/home/skrypt/repo/orchardcore).
# Build all assets
echo "1" | yarn build
# Build a specific asset by name
echo "1" | yarn build -n media-app
# Build multiple assets
echo "1" | yarn build -n media-app,media-field
# Build by tag
echo "1" | yarn build -t admin
# Watch a specific asset (dev mode, auto-rebuilds on save)
echo "1" | yarn watch -n media-app
# Host with bundler dev server (HMR)
echo "1" | yarn host -n media-app
# Clean all build output
echo "1" | yarn cleanThe -n name maps to the "name" field in Assets.json.
.claude/ is gitignored. To avoid being prompted on every build command, create .claude/settings.json locally with these pre-approved commands:
{
"permissions": {
"allow": [
"Bash(echo \"1\" | yarn build*)",
"Bash(echo \"3\" | yarn build*)",
"Bash(fnm exec --using 24.14.1 -- corepack yarn install*)",
"Bash(yarn check*)",
"Bash(yarn lint*)",
"Bash(echo \"1\" | yarn dry-run*)"
]
}
}Do not commit this file or add a .gitignore exception for it — it is intentionally kept local to avoid silently pre-approving commands on other developers' machines.
Before building, if packages are missing:
fnm exec --using 24.14.1 -- corepack yarn installAfter modifying any package.json (root, .scripts/assets-manager/, or a module's Assets/), re-run install.
Built files go to the module/theme's wwwroot/ folder and must be committed to the repo. After any asset change, commit both the source file and the generated wwwroot/ files.
| Location | Purpose |
|---|---|
Root package.json | Workspace orchestration, version resolutions |
.scripts/assets-manager/package.json | Build toolchain (Vite, Parcel, Sass, etc.) |
src/.../Assets/package.json | Runtime deps bundled into that module/theme |
To add a runtime dependency to a module:
# From the module's Assets/ folder
yarn add some-library@1.2.3
# Then rebuild
echo "1" | yarn build -n asset-nameTo add a build tool (affects all assets):
.scripts/assets-manager/package.jsonfnm exec --using 24.14.1 -- corepack yarn installEach module/theme with assets has an Assets.json at its root (e.g. src/OrchardCore.Modules/OrchardCore.Media/Assets.json). See references/actions.md for all supported actions.
Quick example:
[
{
"action": "vite",
"name": "media-app",
"source": "Assets/media-app/",
"tags": ["admin", "js"]
},
{
"action": "sass",
"name": "media-styles",
"source": "Assets/scss/media.scss",
"tags": ["admin", "css"]
}
]These do not go through the Node.js version prompt — run them directly.
# TypeScript type-check all Vue/TS files (vue-tsc --noEmit)
yarn check
# Lint all JS/TS/Vue files (ESLint)
yarn lint
# Preview which files would be built/copied without writing anything
echo "1" | yarn dry-run
echo "1" | yarn dry-run -n media-app # scoped to one assetyarn check — runs vue-tsc --noEmit; catches type errors across all Vue/TS source files. Run before committing TS/Vue changes. Does not support -n; to check a specific module, point it at that module's tsconfig directly: yarn vue-tsc --noEmit -p src/OrchardCore.Modules/OrchardCore.Media/Assets/media-app/tsconfig.jsonyarn lint — runs ESLint across the repo. Accepts a file or directory to scope it: yarn lint src/OrchardCore.Modules/OrchardCore.Media/Assets/. Fix any errors before committing.yarn dry-run — logs what the build would do (copy targets, output paths) without touching any files. Useful when adding a new Assets.json entry to verify paths before the first real build.| Problem | Fix |
|---|---|
Cannot find package '@tailwindcss/vite' | Run fnm exec --using 24.14.1 -- corepack yarn install |
| Parcel cache stale after deleting output | Run echo "1" | yarn clean then rebuild |
| Changes not reflected | Confirm the built wwwroot/ files changed; rebuild if not |
Ran a full-repo build by accident (wrong -n value, e.g. package.json name instead of Assets.json "name") | git status --short immediately; git checkout -- every changed path outside your target module/theme before committing |
| Edited source but bug still repros in the running app | You forgot to rebuild. stat -c '%y' <source>.ts vs stat -c '%y' wwwroot/Scripts/<bundle>.js — if the bundle is older, run yarn build -n <asset-name> |
references/actions.md — All Assets.json action types with examples</content>
</invoke>
© 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-asset-manager of OrchardCMS/OrchardCore.
Open the folder on GitHubat commit bfbe92f
Orchardcore Asset Manager 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 Asset Manager this skillOrchardCMS/OrchardCore | 8.2k | — | ~1.5k | Automated safety check: Pass | BSD-3-Clause | |
| Vuetify Skilldlogue/vite-vuetify-ts-starter | 181 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Quasar Skilldskilld-dev/vue-ecosystem-skills | 181 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Dokan Frontend Devgetdokan/dokan | 288 | — | ~1.9k | Automated safety check: Pass | None | |
| Light Frontend DesignLight0305/Light-skills | 640 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Frappe Ops Frontend BuildImpertio-Studio/Frappe_Claude_Skill_Package | 189 | — | ~2.7k | Automated safety check: Pass | MIT |
logue/vite-vuetify-ts-starter
Vue Material Component Framework. An agent skill from logue/vite-vuetify-ts-starter.
skilld-dev/vue-ecosystem-skills
Build, configure, and debug apps with the Quasar framework (quasar npm package, v2.33.1).
getdokan/dokan
Add or modify Dokan frontend code (React, TypeScript, Vue, Tailwind).
Light0305/Light-skills
Light 按需工程技能·前端设计:把模糊的「做个好看的界面」落成能跑的 React/Tailwind/shadcn 代码 + 设计决策说明—— 有视觉记忆点(signature element)、风格自洽(design tokens 一致)、适配场景(学术海报/数据大屏/管理后台/移动端/营销 landing 信息密度各不同)、反「一眼 AI」(紫蓝渐变/Inter/16px 圆角/巨型…
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when configuring frontend asset bundling, migrating from build.json (v14) to esbuild (v15+), or troubleshooting SCSS/CSS compilation.
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
OrchardCMS/OrchardCore
Produces narrated Orchard Core videos (feature walkthroughs, module overviews, pull request demos) with one unified look and specification - 1080p, Orchard Core logo, colors and fonts, the same…
OrchardCMS/OrchardCore
Creates and updates OrchardCore admin edit views using the ocat- CSS class conventions.
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…
Categories
Builds, watches, and manages frontend assets in OrchardCore. Orchardcore Asset Manager is an agent skill from OrchardCMS/OrchardCore. Builds, watches, and manages frontend assets in OrchardCore.
Orchardcore Asset Manager fits situations like: adding new assets to a module/theme; troubleshooting build failures.
Run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-asset-manager -a claude-code`. Or copy the skill folder (.agents/skills/orchardcore-asset-manager in OrchardCMS/OrchardCore) into .claude/skills/orchardcore-asset-manager in your project. Claude Code loads it when a task matches its description.
Run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-asset-manager -a codex`. Or copy the skill folder (.agents/skills/orchardcore-asset-manager in OrchardCMS/OrchardCore) into .agents/skills/orchardcore-asset-manager 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-asset-manager -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-asset-manager, .gemini/skills/orchardcore-asset-manager, .github/skills/orchardcore-asset-manager and .opencode/skills/orchardcore-asset-manager in your project.
Going by SKILL.md and its folder, Orchardcore Asset Manager needs the command-line tools its instructions call (yarn and git). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. 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 Asset Manager 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 1.5k tokens (SKILL.md is roughly 6k 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 977 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Orchardcore Asset Manager: Vuetify Skilld (logue/vite-vuetify-ts-starter, 181 stars), Quasar Skilld (skilld-dev/vue-ecosystem-skills, 181 stars), Dokan Frontend Dev (getdokan/dokan, 288 stars) and Light Frontend Design (Light0305/Light-skills, 640 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,193 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 10, 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.