A skill your agent uses when adding, enabling, disabling, installing, configuring, or debugging a plugin, bundle, feature, page, panel, tool, or MCP connection in the current Harness profile…
$ npx skills add singula-ai/alego --skill cordis-plugin-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install singula-ai/alego cordis-plugin-development --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/singula-ai/alego.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/preset/agent-preset/skills/cordis-plugin-development .claude/skills/cordis-plugin-development && 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 "cordis-plugin-development" agent skill from https://github.com/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-development into .claude/skills/cordis-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cordis-plugin-development", 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/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-developmentType 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 singula-ai/alego --skill cordis-plugin-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install singula-ai/alego cordis-plugin-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/singula-ai/alego.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/preset/agent-preset/skills/cordis-plugin-development .agents/skills/cordis-plugin-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cordis-plugin-development" agent skill from https://github.com/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-development into .agents/skills/cordis-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cordis-plugin-development", 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 singula-ai/alego --skill cordis-plugin-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install singula-ai/alego cordis-plugin-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/singula-ai/alego.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/preset/agent-preset/skills/cordis-plugin-development .cursor/skills/cordis-plugin-development && 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 "cordis-plugin-development" agent skill from https://github.com/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-development into .cursor/skills/cordis-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cordis-plugin-development", 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/singula-ai/alego.git --path packages/preset/agent-preset/skills/cordis-plugin-development--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 singula-ai/alego --skill cordis-plugin-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install singula-ai/alego cordis-plugin-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/singula-ai/alego.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/preset/agent-preset/skills/cordis-plugin-development .gemini/skills/cordis-plugin-development && 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 "cordis-plugin-development" agent skill from https://github.com/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-development into .gemini/skills/cordis-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cordis-plugin-development", 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 singula-ai/alego cordis-plugin-developmentInstalls 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 singula-ai/alego --skill cordis-plugin-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/singula-ai/alego.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/preset/agent-preset/skills/cordis-plugin-development .github/skills/cordis-plugin-development && 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 "cordis-plugin-development" agent skill from https://github.com/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-development into .github/skills/cordis-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cordis-plugin-development", 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 singula-ai/alego --skill cordis-plugin-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install singula-ai/alego cordis-plugin-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/singula-ai/alego.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/preset/agent-preset/skills/cordis-plugin-development .opencode/skills/cordis-plugin-development && 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 "cordis-plugin-development" agent skill from https://github.com/singula-ai/alego/tree/main/packages/preset/agent-preset/skills/cordis-plugin-development into .opencode/skills/cordis-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cordis-plugin-development", 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.
cordis-plugin-developmentA skill your agent uses when adding, enabling, disabling, installing, configuring, or debugging a plugin, bundle, feature, page, panel, tool, or MCP connection in the current Harness profile…
Cordis Plugin Development is an agent skill from singula-ai/alego. Use when adding, enabling, disabling, installing, configuring, or debugging a plugin, bundle, feature, page, panel, tool, or MCP connection in the current Harness profile, including a shipped plugin that is disabled by default, and for any visual object, decoration, or widget request that names no other destination, which means an installed UI plugin rendered in the Harness Web UI.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including reference files (for example `references/host-plugin.md`, `references/mcp-bundle.md` and `references/practices.md`).
It sits in Agent Workflows, covering Hooks and plugins and Frontend development. It works with Model Context Protocol. The repository describes itself as: Build AI Agents like playing LEGOs. Everything is a Plugin. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit a79fe9a. 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.
Ships script files (JavaScript), which the agent can run.
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.
Cordis Plugin Development loads about 1.9k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 945 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 singula-ai/alego at commit a79fe9a, republished under its MIT licence (© singula-ai). 945 words, ~1,853 tokens.
.claude/skills/cordis-plugin-development/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.Use ordinary workspace files to author a bundle, then plugin_manager with action: install_bundle and the absolute package directory as target to install it in the current profile. Changes affect every session in that profile and survive restart. Load editing-cordis-compositions for agent preset changes.
Do not write the profile's package.json or cordis.patch.yml, create packages under $ALEGO_HOME, or run pnpm in the profile directory: install_bundle performs those steps, and each hand-made write outside the workspace needs its own approval. Every plugin_manager action, including list_plugins and list_bundles, also needs approval without Full access, so call it only when its result decides the next step.
A shipped bundle can resolve a plugin row and leave it disabled. The row id and its reason are in the shipped patch, packages/bundle/*/cordis.patch.yml in a source checkout. Write a workspace bundle whose patch overrides that row with disabled: false and inserts the Host rows it depends on; a source checkout's apps/cli/config/examples/<feature>/cordis.yml lists them for opt-in features. Packages shipped with alego resolve from the alego installation, so the bundle declares no dependencies on them. Install it with install_bundle.
cordis_inspect_list, then targeted cordis_inspect_query calls. For UI, query Client Slots.listSubTree and the selected slot's registration options and props. For anything beyond a static decoration, such as tool policy, agent context, session-derived state, or Chat rows, read references/practices.md before choosing the extension point. Once the chosen slot and registration API are known, write the plugin.templates/ with the file-read tool and write its copies into one workspace directory, or write the installable package, patch, and required Host/Client files there yourself. Check JavaScript syntax and the manifest, then install it. Before that first installation, do not create preview HTML, mock shells, design variants, screenshot scripts, or rasterizer tooling. Use the installed plugin itself as the first preview.application and warnings fields decide whether the change is live, not server logs, terminal output, process lists, or the page's boot payload. Confirm new rows with cordis_inspect_query, which needs no approval, rather than paging list_plugins. After application: applied, exercise the capability or inspect the live Client registration. Use the connected page for visual verification when browser control is available. For a page or panel, also verify design consistency: styles use only theme tokens, the plugin imports no Harness Client package such as @singula-ai/alego-client-ui-primitives, the console shows no slot entry crash, and the view reads correctly in light and dark themes beside a comparable host page. State any verification limitation explicitly; installation and slot registration alone do not establish what the user can see.cordis_inspect_query answers exact Service methods and Event modes (Service, Event), a mounted plugin's Config JSON Schema (Config.listConfigs: filter the paged directory by name, then query the entry id), the Tools this Agent can call (Tool), and live Client Slots and theme tokens (Slots, Theme).Config.listConfigs with name set to the package finds its entries; querying one entry returns its packageDir, the resolved package directory. Read <packageDir>/README.md. Bundled packages resolve from the alego installation and profile-installed bundles from the profile, so never guess the path from $ALEGO_PROFILE_DIR.lib/index.js and lib/types/**/*.d.ts with JSDoc under that same packageDir, not src/; a source checkout of ALEGO has packages/<group>/<name>/src. Read them when inspection and the README leave a question open, and start source-level diagnosis from a concrete installation or runtime failure.ALEGO_PROFILE (profile name) and ALEGO_PROFILE_DIR (its directory, whose node_modules holds only profile-installed bundles) are set in every shell call of a profile-launched Harness and absent when the Harness was booted without a profile. Bash reads them as $ALEGO_PROFILE; PowerShell, which the Windows preset uses, reads them as $env:ALEGO_PROFILE. With alego on the PATH, alego --profile "$ALEGO_PROFILE" --dump-config prints the composed profile.
The files below live in this skill's base directory, which the skill tool reported, and the table is the complete list: do not enumerate that directory. In every deployment, including a source checkout, read these files with the file-read tool, write copies into the workspace with the file-write tool, and verify a copy by reading it back. In Desktop the directory sits inside app.asar, which only the Host process's own file reads can open; shell commands (ls, cat, cp, cmp), the glob and search tools (they run a native ripgrep process), node, and pnpm all fail on it. Never install or syntax-check a template in place; copy its contents into the workspace first.
| Task | File |
|---|---|
| Bundle manifest, display metadata and icon, install and enable semantics, Host plugin export forms, Config | references/host-plugin.md |
| A UI plugin rendered in the Web page: Client manifest, module loader, slot registration | references/ui-plugin.md |
| Connecting an MCP server through a configuration-only bundle | references/mcp-bundle.md |
| Verification limits when no browser control is available | references/verification.md |
| UI plugin starting point, four files | templates/decoration/package.json, templates/decoration/cordis.patch.yml, templates/decoration/index.js, templates/decoration/client.js |
| MCP bundle starting point, two files | templates/mcp/package.json, templates/mcp/cordis.patch.yml |
| Loader patch dialect and the list of installable plugin packages | the cordis-composition-reference skill |
| Choosing extension points, contexts, and state mechanisms for upgrade stability and performance | references/practices.md |
© singula-ai, MIT. 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 11 other files (references) in packages/preset/agent-preset/skills/cordis-plugin-development of singula-ai/alego.
Open the folder on GitHubat commit a79fe9a
Cordis Plugin Development 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 |
|---|---|---|---|---|---|---|
| Cordis Plugin Development this skillsingula-ai/alego | 109 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Cordis Plugin DevelopmentZhou-Yujing114514/deepseek-harness-linux | 118 | — | ~2k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Agent Setup Health Audittw93/Waza | 7.2k | — | ~5.2k | Automated safety check: Notes | MIT | |
| Writing Pluginsnukeop/nuclear | 19k | — | ~825 | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Plugin Buildergetpaseo/paseo | 20k | — | ~9.4k | Automated safety check: Pass | Custom licence |
Zhou-Yujing114514/deepseek-harness-linux
A skill your agent uses when designing, reviewing, adding, enabling, disabling, installing, configuring, or debugging a plugin, bundle, feature, page, panel, tool, or MCP connection in the current…
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
nukeop/nuclear
A skill your agent uses when writing, scaffolding, or modifying Nuclear plugins.
getpaseo/paseo
Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers.
tractorjuice/arc-kit
This skill should be used when a new ArcKit command has been added and documentation needs updating across the repository.
singula-ai/alego
Record browser or Web UI interaction demos as optimized GIFs using the available browser-control workflow, optional Playwright Videos for higher capture frame rates, and deterministic encoding, then…
singula-ai/alego
A skill your agent uses when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in alego; checks every new note for superseded active records, deletes small UI and purely…
singula-ai/alego
A skill your agent uses when landing a stack of dependent GitHub PRs (A ← B ← C, where each bases on the one below) onto master, merging a PR whose base is another open PR's branch, or whenever a…
singula-ai/alego
A skill your agent uses when creating, changing, or validating an agent preset or other Cordis composition for this harness, including deciding host versus preset placement and checking that an…
singula-ai/alego
Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables.
singula-ai/alego
Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts.
Works with
A skill your agent uses when adding, enabling, disabling, installing, configuring, or debugging a plugin, bundle, feature, page, panel, tool, or MCP connection in the current Harness profile…. Cordis Plugin Development is an agent skill from singula-ai/alego. Use when adding, enabling, disabling, installing, configuring, or debugging a plugin, bundle, feature, page, panel, tool, or MCP connection in the current Harness profile, including a shipped plugin that is disabled by default, and for any visual object, decoration, or widget request that names no other destination, which means an installed UI plugin rendered in the Harness Web UI.
Cordis Plugin Development fits situations like: debugging a plugin; MCP connection in the current Harness profile; including a shipped plugin that is disabled by default; for any visual object.
Run `npx skills add singula-ai/alego --skill cordis-plugin-development -a claude-code`. Or copy the skill folder (packages/preset/agent-preset/skills/cordis-plugin-development in singula-ai/alego) into .claude/skills/cordis-plugin-development in your project. Claude Code loads it when a task matches its description.
Run `npx skills add singula-ai/alego --skill cordis-plugin-development -a codex`. Or copy the skill folder (packages/preset/agent-preset/skills/cordis-plugin-development in singula-ai/alego) into .agents/skills/cordis-plugin-development 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 singula-ai/alego --skill cordis-plugin-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cordis-plugin-development, .gemini/skills/cordis-plugin-development, .github/skills/cordis-plugin-development and .opencode/skills/cordis-plugin-development in your project.
Going by SKILL.md and its folder, Cordis Plugin Development needs JavaScript for the scripts in its folder. Our summary lists: Node.js.
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.
Cordis Plugin Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.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 3.7k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Cordis Plugin Development: Cordis Plugin Development (Zhou-Yujing114514/deepseek-harness-linux, 118 stars), Crush Configuration (charmbracelet/crush, 29k stars), Agent Setup Health Audit (tw93/Waza, 7.2k stars) and Writing Plugins (nukeop/nuclear, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
singula-ai (a GitHub organization) maintains it in singula-ai/alego, which has 109 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 28, 2026.
Source: singula-ai/alego on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
