14 named · 70+ supported · one install
Where these skills run.
Every pack is an Agent Skills bundle — a SKILL.md with
its references beside it — so any agent that reads that standard reads these.
Two get a channel of their own; the rest share one directory.
The named agents
Reads is the path that agent actually looks in — the fact worth having when something does not show up.
| Agent | Channel | Reads | Worth knowing |
|---|---|---|---|
| Claude Code | plugin | ~/.claude/plugins | installed as plugins, never as a plain ~/.claude/skills copy — that copy shadows the plugin and serves its frozen version forever |
| DeepSeek Harness | reads the hub directly | ~/.agents/skills (rank 500) | no plugin to write: the skills subsystem is in the default web profile, and its local provider scans six roots nearest-first — a project-local .dsh/skills or .agents/skills outranks the installed one |
| Cursor | skills CLI | ~/.agents/skills | plus a Cursor rules file the launcher writes for routing |
| Codex | skills CLI | ~/.agents/skills | routing block goes to ~/.codex/AGENTS.md |
| Gemini CLI | skills CLI | ~/.agents/skills | routing block goes to ~/.gemini/GEMINI.md |
| OpenCode | skills CLI | ~/.agents/skills | — |
| Windsurf | skills CLI | ~/.agents/skills | — |
| Zed | skills CLI | ~/.agents/skills | — |
| Kilo Code | skills CLI | ~/.agents/skills | — |
| Kimi CLI | skills CLI | ~/.agents/skills | — |
| Hermes | skills CLI | ~/.agents/skills | — |
| OpenClaw | skills CLI | ~/.agents/skills | — |
| Kiro | skills CLI | ~/.agents/skills | — |
| Goose | skills CLI | ~/.agents/skills | — |
One channel per agent, always. A plain copy beside a plugin, or a project-local copy beside the installed one, wins — and then serves its frozen version forever. The launcher prunes the copies the skills CLI recreates; the project-local case is yours to avoid.
DeepSeek Harness, specifically
Nothing to install beyond the ordinary command, and no plugin to
write — in dsh a plugin is a Cordis module exporting
apply(ctx), and skills are loaded by one.
npx sshlg-skills install
Verified twice on 2026-08-25 rather than read off a page. The subsystem is in the default profile, not an add-on a reader has to enable:
npx @deepseek-ai/dsh --profile web --dump-default-config | grep skill
and the files are where that provider looks:
~/.agents/skills/<name>/SKILL.md, with its references/
and fixtures/ beside it.
Six roots, nearest wins
<projectRoot>/.dsh/skills— rank 100<projectRoot>/.agents/skills— rank 200customSkillDirs— rank 300<dshHome>/skills— rank 400<agentsHome>/skills— rank 500, which is~/.agents/skills- bundled — rank 600
A project-local copy overrides the installed one — the same shadowing trap Claude Code has, with the same remedy.
disable-model-invocation and user-invocable are the two
front-matter keys it reads, both defaulting to true. This family ships
neither, so every skill is model- and user-invocable there without a change.
Any other agent
The vercel skills CLI supports 70+ of them and installs into the
same hub directory. If yours reads SKILL.md, it reads these.
npx skills add ssheleg/sshlg-skills
Questions this page gets asked
Do these skills work in my agent?
If it reads the Agent Skills standard, yes. Every pack is a SKILL.md with its references beside it, and the table above names the path each agent actually reads.
Does DeepSeek Harness need a plugin for these?
No. dsh reads the Agent Skills standard directly and its skills subsystem is in the default profile — a plugin there is a Cordis module, and skills are loaded by one rather than being one.
Why did my skill not show up after installing?
Almost always a path question rather than an install one. A project-local copy outranks the installed one in every host that scans more than one root, and a plain copy beside a Claude Code plugin shadows the plugin and serves its frozen version. Keep one channel per skill.
Do I have to install all of them?
No — every pack installs standalone, as in npx skills add ssheleg/telegram-dev for one of them. The launcher exists because a member updated on its own leaves the set in a combination nobody tested.
Do they send anything anywhere?
No. They are documentation, validators and small standard-library scripts — no services, no telemetry and no API keys, which is checkable in the repository rather than promised here.
The 9 packs
Each one is an entry point an agent can be routed to. The full descriptions are on the front page.