Cordis Plugin Development
singula-ai/alego
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…
Agent skill
Cordis Plugin Development
by Zhou-Yujing114514 in 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…
Install Cordis Plugin Development
$ npx skills add Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Zhou-Yujing114514/deepseek-harness-linux 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/Zhou-Yujing114514/deepseek-harness-linux.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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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 Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Zhou-Yujing114514/deepseek-harness-linux cordis-plugin-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Zhou-Yujing114514/deepseek-harness-linux.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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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 Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Zhou-Yujing114514/deepseek-harness-linux cordis-plugin-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Zhou-Yujing114514/deepseek-harness-linux.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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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/Zhou-Yujing114514/deepseek-harness-linux.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 Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Zhou-Yujing114514/deepseek-harness-linux 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/Zhou-Yujing114514/deepseek-harness-linux.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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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 Zhou-Yujing114514/deepseek-harness-linux 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 Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Zhou-Yujing114514/deepseek-harness-linux.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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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 Zhou-Yujing114514/deepseek-harness-linux --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 Zhou-Yujing114514/deepseek-harness-linux cordis-plugin-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Zhou-Yujing114514/deepseek-harness-linux.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/Zhou-Yujing114514/deepseek-harness-linux/tree/master/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.
Facts
- Skill name
cordis-plugin-development- GitHub stars
- 120
- Token cost
- ~2k tokens
- SKILL.md length
- 1,001 words
- Files
- 18 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 5 steps: Resolve the requested result and… → Discover only the APIs needed for that… → Read and copy the matching template… → …
- Debugging a plugin
- SKILL.md covers Design or review, Enable a shipped plugin, Deliver a working plugin first and Knowledge sources, in order, plus 1 more section
- Runs JavaScript scripts from its folder
What it does
Cordis Plugin Development is an agent skill from Zhou-Yujing114514/deepseek-harness-linux. Use when designing, reviewing, 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 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 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: First-class Linux packaging for DeepSeek Harness desktop — AppImage, .deb, .tar.gz for x64/arm64, built by native CI. The licence is MIT.
When your agent uses it
- Debugging a plugin
- MCP connection in the current Harness profile
- Including a shipped plugin that is disabled by default
- For any visual object
Example prompts
- “/cordis-plugin-development”
Requirements
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Resolve the requested result and destination. An unspecified visual destination is the current Harness Web UI; a standalone image or HTML…
- Discover only the APIs needed for that version: cordis_inspect_list, then targeted cordis_inspect_query calls. For UI, query Client…
- Read and copy the matching template files into one workspace directory, or author the package, patch, and required Host/Client files…
- Read the installation result: application and warnings decide whether the change is live, not logs, process lists, or the page's boot…
- Fix observed defects in the same plugin. When the requested result works, finish with its location, verification status, and the reason…
What it can do on your machine
Read from SKILL.md and the folder at commit 35a829f. 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
Ships script files (JavaScript, from the files we listed), which the agent can run.
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
Cordis Plugin Development loads about 2k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 1,001 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.
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 Zhou-Yujing114514/deepseek-harness-linux at commit 35a829f, republished under its MIT licence (© Zhou-Yujing114514). 1,001 words, ~2,037 tokens.
Download SKILL.mdSave it as
.claude/skills/cordis-plugin-development/SKILL.md (or your agent's skills folder). This skill also uses 17 other files; get the full folder from GitHub.- name
- cordis-plugin-development
- description
- Use when designing, reviewing, 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.
Persistent Harness plugins
For implementation, 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 $DSH_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.
Design or review
Read the applicable references below and inspect the proposed or existing plugin against current APIs. Report design choices or findings instead of following the installation workflow. Do not write files, install bundles, or change profile state unless the user requests implementation.
Enable a shipped plugin
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 dsh resolve from the dsh installation, so the bundle declares no dependencies on them. Install it with install_bundle.
Deliver a working plugin first
- Resolve the requested result and destination. An unspecified visual destination is the current Harness Web UI; a standalone image or HTML file does not complete such a request. Choose reasonable visual details and implement a small first version; install it before visual refinement.
- Discover only the APIs needed for that version:
cordis_inspect_list, then targetedcordis_inspect_querycalls. For UI, query ClientSlots.listSubTreeand 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, readreferences/practices.mdbefore choosing the extension point; for a user action in plugin UI, also readreferences/user-actions.md. Once the chosen slot and registration API are known, write the plugin. - Read and copy the matching template files into one workspace directory, or author the package, patch, and required Host/Client files there. Before installing, complete the display checklist in
references/host-plugin.md: meaningful localized titles/descriptions, an original or licensed icon, and exported resources with distribution checks where applicable. This applies to Host-only and configuration-only bundles too; adapt template text and artwork to the request. Check JavaScript syntax and the manifest, then install. Use the installed plugin as the first preview; do not create preview HTML, mock shells, design variants, screenshot scripts, or rasterizer tooling first. - Read the installation result:
applicationandwarningsdecide whether the change is live, not logs, process lists, or the page's boot payload. Confirm new rows with approval-freecordis_inspect_query, notlist_plugins. Afterapplication: applied, exercise the capability or inspect the live Client registration. Verify installed display metadata and the icon usingreferences/host-plugin.md. Use the connected page when available; followreferences/verification.mdfor page/panel design checks and unavailable browser control, andreferences/user-actions.mdfor user actions. Restore user state changed during testing. Report verification limits; installation and slot registration alone do not establish what the user sees. - Fix observed defects in the same plugin. When the requested result works, finish with its location, verification status, and the reason for any display-resource exception; never silently accept default artwork. Do not continue speculative variants, optional features, or mock previews. Close any task list.
Show full SKILL.md (415 more words)Show less
Knowledge sources, in order
- Inspection:
cordis_inspect_queryanswers exact Service methods and Event modes (Service,Event), a mounted plugin's Config JSON Schema (Config.listConfigs: filter the paged directory byname, then query theentryid), the Tools this Agent can call (Tool), and live Client Slots and theme tokens (Slots,Theme). - Package documentation:
Config.listConfigswithnameset to the package finds its entries; querying oneentryreturns itspackageDir, the resolved package directory. Read<packageDir>/README.md. Bundled packages resolve from the dsh installation and profile-installed bundles from the profile, so never guess the path from$DSH_PROFILE_DIR. - Source: installed packages ship built
lib/index.jsandlib/types/**/*.d.tswith JSDoc under that samepackageDir, notsrc/; a source checkout of DSH haspackages/<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.
DSH_PROFILE (profile name) and DSH_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 $DSH_PROFILE; PowerShell, which the Windows preset uses, reads them as $env:DSH_PROFILE. With dsh on the PATH, dsh --profile "$DSH_PROFILE" --dump-config prints the composed profile.
Read next
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, locale resources, icons, installation, Host exports and Config | references/host-plugin.md |
| Web UI: Client manifest, module loader, slot registration | references/ui-plugin.md |
| Connecting an MCP server through a configuration-only bundle | references/mcp-bundle.md |
| Page/panel design checks and verification without browser control | references/verification.md |
| UI plugin template, including display resources | templates/decoration/package.json, templates/decoration/cordis.patch.yml, templates/decoration/index.js, templates/decoration/client.js, templates/decoration/locale/en.json, templates/decoration/icon.svg |
| MCP bundle template, including display resources | templates/mcp/package.json, templates/mcp/cordis.patch.yml, templates/mcp/locale/en.json, templates/mcp/icon.svg |
| 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 |
| Sharing application operations between UI actions and agent tools | references/user-actions.md |
© Zhou-Yujing114514, MIT. 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 17 other files (references) in packages/preset/agent-preset/skills/cordis-plugin-development of Zhou-Yujing114514/deepseek-harness-linux.
- SKILL.md
- references/host-plugin.md
- references/mcp-bundle.md
- references/practices.md
- references/ui-plugin.md
- references/user-actions.md
- references/verification.md
- templates/decoration/client.js
- templates/decoration/cordis.patch.yml
- templates/decoration/icon.svg
- templates/decoration/index.js
- templates/decoration/locale/en.json
- templates/decoration/package.json
- templates/mcp/cordis.patch.yml
- templates/mcp/icon.svg
- templates/mcp/locale
- … and 2 more
Open the folder on GitHubat commit 35a829f
Compare with similar skills
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 skillZhou-Yujing114514/deepseek-harness-linux | 120 | — | ~2k | Automated safety check: Pass | MIT | |
| Cordis Plugin Developmentsingula-ai/alego | 109 | — | ~1.9k | 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 |
Similar skills
Crush Configuration
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.
Agent Setup Health Audit
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
Writing Plugins
nukeop/nuclear
A skill your agent uses when writing, scaffolding, or modifying Nuclear plugins.
Paseo Plugin Builder
getpaseo/paseo
Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers.
New Command Docs
tractorjuice/arc-kit
This skill should be used when a new ArcKit command has been added and documentation needs updating across the repository.
More from Zhou-Yujing114514/deepseek-harness-linux
All 9 skills in this repoDiagnose Windows Sandbox Acl
Zhou-Yujing114514/deepseek-harness-linux
Use on Windows for unexpected DSH sandbox access denials: workspace writes or listing fail, or an ordinarily readable path cannot be read.
Dsh Create Upgrade Guide
Zhou-Yujing114514/deepseek-harness-linux
A skill your agent uses when a deepseek-harness change breaks an externally perceptible surface (CLI, profiles, cordis.yml or settings keys, persisted user data, SDK or wire APIs, published package…
Dsh CI Test Reliability
Zhou-Yujing114514/deepseek-harness-linux
Design, review, and diagnose DeepSeek Harness tests and fixtures that can fail nondeterministically under CI concurrency, shared host resources, clocks, process-global state, subprocesses, network…
Dsh Find Simplifications
Zhou-Yujing114514/deepseek-harness-linux
Find evidence-backed simplifications in DeepSeek Harness code, APIs, configuration, tests, and prose; write or consolidate proposals, identify small inline cleanups, or assess simplifications from…
Dsh Client UI UX
Zhou-Yujing114514/deepseek-harness-linux
Design and review DeepSeek Harness client UI changes — visual token discipline, reuse-before-adding, feedback surfaces (toast vs in-place notice vs empty state), overlay and menu safety, platform…
Dsh Code Review
Zhou-Yujing114514/deepseek-harness-linux
A skill your agent uses when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality…
Related
Works with
Questions about Cordis Plugin Development
What does Cordis Plugin Development do?
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…. Cordis Plugin Development is an agent skill from Zhou-Yujing114514/deepseek-harness-linux. Use when designing, reviewing, 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.
When should I use Cordis Plugin Development?
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.
How do I install Cordis Plugin Development in Claude Code?
Run `npx skills add Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a claude-code`. Or copy the skill folder (packages/preset/agent-preset/skills/cordis-plugin-development in Zhou-Yujing114514/deepseek-harness-linux) into .claude/skills/cordis-plugin-development in your project. Claude Code loads it when a task matches its description.
How do I install Cordis Plugin Development in Codex?
Run `npx skills add Zhou-Yujing114514/deepseek-harness-linux --skill cordis-plugin-development -a codex`. Or copy the skill folder (packages/preset/agent-preset/skills/cordis-plugin-development in Zhou-Yujing114514/deepseek-harness-linux) into .agents/skills/cordis-plugin-development in your project. Codex loads it when a task matches its description.
Can I use Cordis Plugin Development 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 Zhou-Yujing114514/deepseek-harness-linux --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.
What does Cordis Plugin Development need to run?
Going by SKILL.md and its folder, Cordis Plugin Development needs JavaScript for the scripts in its folder. Our summary lists: Node.js.
Does Cordis Plugin Development 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 Cordis Plugin Development 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 Cordis Plugin Development use?
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.
How many tokens does Cordis Plugin Development use?
About 2k tokens (SKILL.md is roughly 8.1k 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 4.6k tokens, read only when the agent opens those files.
What are the alternatives to Cordis Plugin Development?
Skills that share tags, products or a category with Cordis Plugin Development: Cordis Plugin Development (singula-ai/alego, 109 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.
Who maintains Cordis Plugin Development?
Zhou-Yujing114514 (a GitHub user) maintains it in Zhou-Yujing114514/deepseek-harness-linux, which has 120 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.
Source: Zhou-Yujing114514/deepseek-harness-linux on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.