Install on any agent.
Every route installs the same skill directory, so no two agents can drift apart. Pick yours.
Claude Code is the route verified end to end. The others follow each harness's documented convention for skills and extensions; if one has changed, open an issue and it gets fixed.
Two prompts in a session, then reload.
/plugin marketplace add mkabumattar/sysdesign
/plugin install sysdesign@sysdesign
/reload-plugins/sysdesign:help/plugin update sysdesign
/reload-plugins/plugin uninstall sysdesignThe manifest points at the canonical skills directory.
codex plugin marketplace add mkabumattar/sysdesign --ref main
codex plugin install sysdesign@sysdesigncodex plugin listcodex plugin marketplace update sysdesigncodex plugin uninstall sysdesignSkill and commands both load: the manifest declares ./skills/ and ./commands/.
/plugins install https://github.com/mkabumattar/sysdesign/plugins list
/sysdesign:help/plugins install https://github.com/mkabumattar/sysdesign
/plugins reload/plugins remove sysdesignInstalls as an extension with a context file that routes to the skill.
gemini extensions install https://github.com/mkabumattar/sysdesigngemini extensions listgemini extensions update sysdesigngemini extensions uninstall sysdesignReads agent skills natively. Installs per project or globally.
npx skills add mkabumattar/sysdesign -a github-copilot # this project
npx skills add mkabumattar/sysdesign -a github-copilot -g # all projectsnpx skills list
# or type / in the chat input and look for system-designnpx skills update system-designnpx skills remove system-designThe Agent Panel reads agent skills directly: import by URL or drop the folder in.
# Agent Panel → Skills manager → Create skill from URL, paste:
https://github.com/mkabumattar/sysdesign/blob/main/skills/system-design/SKILL.md
# or copy it in:
git clone https://github.com/mkabumattar/sysdesign
cp -R sysdesign/skills/system-design ~/.config/zed/skills/# Skills manager lists system-design, or type / in the Agent Panel# re-import the same URL, or git pull and re-copyrm -rf ~/.config/zed/skills/system-designInstalls the skill from the repository into your Hermes skills directory.
hermes skills install mkabumattar/sysdesign/skills/system-designhermes skills listhermes skills update system-designhermes skills uninstall system-designImplements the agent-skills standard; invoked as /skill:system-design once skill commands are enabled.
npx skills add mkabumattar/sysdesign -a pi -y
# settings.json: { "enableSkillCommands": true }npx skills list
# then type /skill:system-design in a new sessionnpx skills update system-designnpx skills remove system-designAny harness that reads agent skills. Start a new chat afterwards, since skills are indexed at session start.
npx skills add mkabumattar/sysdesign# start a new chat, then ask a system-design questionnpx skills update system-designrm -rf ~/.cursor/skills/system-designClone the repository; the root manifest points at the skill.
git clone https://github.com/mkabumattar/sysdesign.git# ask a system-design question and check the answer names its tradeoffgit pullrm -rf sysdesignPlain Markdown, no build step. Any agent that can read files can use it.
git clone https://github.com/mkabumattar/sysdesign.git
# point the agent at skills/system-design/SKILL.md# ask it to compare two options under a stated constraintgit pullrm -rf sysdesignHow activation works
The skill declares its trigger in its own frontmatter. Agents that auto-invoke skills load it when a prompt touches architecture, databases, caching, networking, security, payments, observability, cost, low-level design or interview prep. Agents without auto-invocation still work: name the skill in your prompt. The fourteen slash commands are a Claude Code convenience; elsewhere, phrase the intent instead.
Something not working?
Restart the agent first, since skill indexes are read at startup. The full guide has the rest.