Ecc Recipes
affaan-m/ECC
Map a described workflow to the right ECC command group with run-order and stop condition, or browse all command-group recipe families read live from the commands directory.
Creates OrchardCore setup recipes (.recipe.json) that provision a tenant on setup — enabling features, setting themes, defining content types, importing content, roles, and settings.
$ npx skills add OrchardCMS/OrchardCore --skill orchardcore-recipe-creator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-recipe-creator --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-recipe-creator .claude/skills/orchardcore-recipe-creator && 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-recipe-creator" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-recipe-creator into .claude/skills/orchardcore-recipe-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-recipe-creator", 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-recipe-creatorType 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-recipe-creator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-recipe-creator --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-recipe-creator .agents/skills/orchardcore-recipe-creator && 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-recipe-creator" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-recipe-creator into .agents/skills/orchardcore-recipe-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-recipe-creator", 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-recipe-creator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-recipe-creator --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-recipe-creator .cursor/skills/orchardcore-recipe-creator && 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-recipe-creator" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-recipe-creator into .cursor/skills/orchardcore-recipe-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-recipe-creator", 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-recipe-creator--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-recipe-creator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OrchardCMS/OrchardCore orchardcore-recipe-creator --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-recipe-creator .gemini/skills/orchardcore-recipe-creator && 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-recipe-creator" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-recipe-creator into .gemini/skills/orchardcore-recipe-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-recipe-creator", 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-recipe-creatorInstalls 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-recipe-creator -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-recipe-creator .github/skills/orchardcore-recipe-creator && 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-recipe-creator" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-recipe-creator into .github/skills/orchardcore-recipe-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-recipe-creator", 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-recipe-creator -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-recipe-creator --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-recipe-creator .opencode/skills/orchardcore-recipe-creator && 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-recipe-creator" agent skill from https://github.com/OrchardCMS/OrchardCore/tree/main/.agents/skills/orchardcore-recipe-creator into .opencode/skills/orchardcore-recipe-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchardcore-recipe-creator", 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-recipe-creatorCreates OrchardCore setup recipes (.recipe.json) that provision a tenant on setup — enabling features, setting themes, defining content types, importing content, roles, and settings.
Orchardcore Recipe Creator is an agent skill from OrchardCMS/OrchardCore. Creates OrchardCore setup recipes (.recipe.json) that provision a tenant on setup — enabling features, setting themes, defining content types, importing content, roles, and settings. Use when the user needs to create a setup recipe, a starter recipe, or automate tenant configuration.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/recipe-structure.md` and `references/steps.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 step headings in SKILL.md.
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:
dotnetFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
orchardcore.netFrom 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 Recipe Creator loads about 1.6k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 572 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). 572 words, ~1,608 tokens.
.claude/skills/orchardcore-recipe-creator/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.This skill guides you through creating a setup recipe for OrchardCore. A setup recipe is a .recipe.json file that runs when a tenant is created, provisioning everything the site needs: enabled features, active themes, content definitions, content items, roles, and settings.
Recipes/ folder)A setup recipe is a normal recipe with "issetuprecipe": true in its header. That flag makes it appear in the setup screen's recipe dropdown so a user can pick it when creating a tenant. Without it, the recipe is still executable from the admin (Configuration → Recipes) but won't show during setup.
Recipes are discovered from a Recipes/ folder inside any enabled module or theme:
mkdir src/OrchardCore.Themes/YourTheme/RecipesThe file name must end with .recipe.json:
src/OrchardCore.Themes/YourTheme/Recipes/yoursite.recipe.json{
"name": "YourSite",
"displayName": "Your Site",
"description": "Provisions a Your Site tenant with content and theme.",
"author": "The Orchard Core Team",
"website": "https://orchardcore.net",
"version": "1.0.0",
"issetuprecipe": true,
"categories": [ "default" ],
"tags": [ "yoursite" ],
"variables": {
"homeContentItemId": "[js:uuid()]"
},
"steps": []
}variables are evaluated on first access and reused across steps — use them for content item ids so steps can reference the same item. Recipe JSON may contain // comments.
Steps run top to bottom. A typical setup recipe order:
feature — enable the modules and theme features the site needs.themes — set the active site and admin themes.settings — site-wide settings (home route, culture, time zone).Roles — roles and their permissions.ContentDefinition — content types and parts.content — the actual content items (pages, menus, widgets).media, queries, layers, Templates, AdminMenu — as needed.Minimum viable setup recipe:
"steps": [
{
"name": "feature",
"enable": [
"OrchardCore.Admin",
"OrchardCore.Contents",
"OrchardCore.ContentTypes",
"OrchardCore.Title",
"OrchardCore.Autoroute",
"OrchardCore.Alias",
"OrchardCore.Themes",
"OrchardCore.HomeRoute",
"TheTheme",
"YourTheme"
]
},
{
"name": "themes",
"admin": "TheAdmin",
"site": "YourTheme"
}
]!!! warning
Always enable your own theme's feature in the feature step. If you set it as the site theme without enabling it, the layout won't render after setup.
For every built-in step (feature, themes, settings, ContentDefinition, content, media, Roles, layers, queries, Templates, AdminMenu, WorkflowType, deployment, custom-settings, recipes, search indexes), see references/steps.md.
Values can embed expressions with [helper:...] syntax:
| Helper | Example | Use |
|---|---|---|
js | "[js:variables('homeContentItemId')]" | Reference variables / JS expressions |
uuid | "[js:uuid()]" | Generate a new content item id |
file | "[file:text('Snippets/home.liquid')]" | Inline an external file's text |
env | "[env:MY_VAR]" | Read an environment variable |
appsettings | "[appsettings:OrchardCore:SiteName]" | Read appsettings config |
localization | "[localization:WelcomeTitle]" | Localized string |
base64 / gzip | "[js:base64('...')]" | Decode embedded binary/text |
# Build the host module/theme
dotnet build src/OrchardCore.Themes/YourTheme
# Run the application
cd src/OrchardCore.Cms.Web
dotnet run -f net10.0Then create a new tenant (or reset the default one) and pick Your Site in the setup screen's recipe list. Verify features, theme, and content provisioned correctly.
To re-run a non-setup recipe without a fresh tenant: Admin → Configuration → Recipes → Run.
| Property | Purpose |
|---|---|
name | Unique internal id (used by the recipes step to call it) |
displayName | Friendly name in setup/admin UI |
description | Short summary shown to the user |
issetuprecipe | true makes it selectable during tenant setup |
categories / tags | Grouping/filtering in the UI |
variables | Reusable values, evaluated once on first access |
steps | Ordered actions to execute |
| Area | Features |
|---|---|
| Core | OrchardCore.Admin, OrchardCore.HomeRoute, OrchardCore.Themes, OrchardCore.Settings, OrchardCore.Recipes |
| Content | OrchardCore.Contents, OrchardCore.ContentTypes, OrchardCore.ContentFields, OrchardCore.Title, OrchardCore.Autoroute, OrchardCore.Alias, OrchardCore.Html, OrchardCore.Flows, OrchardCore.Lists, OrchardCore.Widgets |
| Media/Menu | OrchardCore.Media, OrchardCore.Menu, OrchardCore.Layers |
| Security | OrchardCore.Users, OrchardCore.Roles, OrchardCore.Security |
| Item | Convention | Example |
|---|---|---|
| Recipe file | name.recipe.json (lowercase) | blog.recipe.json |
name property | PascalCase | Blog |
| Location | Recipes/ in a module or theme | Themes/TheBlogTheme/Recipes/ |
references/recipe-structure.md - File layout, header, variables, helpersreferences/steps.md - Every built-in recipe step with examplesreference/modules/Recipes/README.md (docs) - Full recipe documentationsrc/OrchardCore.Themes/*/Recipes/*.recipe.json© 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 2 other files (references) in .agents/skills/orchardcore-recipe-creator of OrchardCMS/OrchardCore.
Open the folder on GitHubat commit bfbe92f
Orchardcore Recipe Creator 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 Recipe Creator this skillOrchardCMS/OrchardCore | 8.2k | — | ~1.6k | Automated safety check: Pass | BSD-3-Clause | |
| Ecc Recipesaffaan-m/ECC | 277k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Skill Creatoropenclaw/openclaw | 392k | — | ~576 | Automated safety check: Pass | Apache-2.0 | |
| ESP32 CSI Node Provisioningruvnet/RuView | 97k | — | ~579 | Automated safety check: Pass | MIT | |
| Content Creatoralirezarezvani/claude-skills | 28k | 1 repos | ~713 | Automated safety check: Pass | MIT | |
| Company Creatorpaperclipai/paperclip | 100k | — | ~2.9k | Automated safety check: Pass | MIT |
affaan-m/ECC
Map a described workflow to the right ECC command group with run-order and stop condition, or browse all command-group recipe families read live from the commands directory.
openclaw/openclaw
Author or review AgentSkills: create, repair, validate, or restructure SKILL.md files and bundled resources.
ruvnet/RuView
Builds, flashes and provisions an ESP32-S3 or C6 CSI node for RuView, with checksum-verified flashing, WiFi settings and boot-log evidence that CSI is flowing.
alirezarezvani/claude-skills
Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist.
paperclipai/paperclip
Create agent company packages that conform to agentcompanies/v1.
google/adk-recipes
Creates a new Python recipe for the ADK recipes repository by running a scaffold script that copies template files, after confirming the output directory and recipe name.
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
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.
Creates OrchardCore setup recipes (.recipe.json) that provision a tenant on setup — enabling features, setting themes, defining content types, importing content, roles, and settings. Orchardcore Recipe Creator is an agent skill from OrchardCMS/OrchardCore.json) that provision a tenant on setup — enabling features, setting themes, defining content types, importing content, roles, and settings.
Orchardcore Recipe Creator fits situations like: the user needs to create a setup recipe; A starter recipe; automate tenant configuration.
Run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-recipe-creator -a claude-code`. Or copy the skill folder (.agents/skills/orchardcore-recipe-creator in OrchardCMS/OrchardCore) into .claude/skills/orchardcore-recipe-creator in your project. Claude Code loads it when a task matches its description.
Run `npx skills add OrchardCMS/OrchardCore --skill orchardcore-recipe-creator -a codex`. Or copy the skill folder (.agents/skills/orchardcore-recipe-creator in OrchardCMS/OrchardCore) into .agents/skills/orchardcore-recipe-creator 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-recipe-creator -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-recipe-creator, .gemini/skills/orchardcore-recipe-creator, .github/skills/orchardcore-recipe-creator and .opencode/skills/orchardcore-recipe-creator in your project.
Going by SKILL.md and its folder, Orchardcore Recipe Creator needs the command-line tools its instructions call (dotnet).
SKILL.md names 1 domain. In commands or code: orchardcore.net; the agent is likely to contact it when it follows the instructions. 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 Recipe Creator 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.6k tokens (SKILL.md is roughly 6.4k 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 2.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Orchardcore Recipe Creator: Ecc Recipes (affaan-m/ECC, 277k stars), Skill Creator (openclaw/openclaw, 392k stars), ESP32 CSI Node Provisioning (ruvnet/RuView, 97k stars) and Content Creator (alirezarezvani/claude-skills, 28k 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.