Moximxxx/dsh-find-skill
dsh plugin bridging the vercel-labs/skills ecosystem: LLM-driven skill search, install, and lifecycle for temp
Bridges the vercel-labs/skills open agent-skill ecosystem into DeepSeek Harness. The LLM decides when a skill is needed: when the task exceeds existing tools and loaded skills, the model searches the skill ecosystem (skill_find), asks the user which skill + scope via the built-in ask_user_question, then loads it as temp (default, current session only), project (shared per workspace), or global (all sessions). Includes skill_install (isolated one-shot work/home environment, adopts only the target skill directory) and skill_remove (temp→project→global order). A /skill human command covers find/install/update/sync/remove/list; update re-pulls from the recorded source; sync scans project node_modules declarations via the official CLI. Lifecycle: temp skills are visible only to the installing agent's session, auto-unregistered on agent/session dispose; compactDisposePolicy: keep|dispose|ask controls compact behavior. Optional dsh-find-skill-client package renders dedicated session cards for the tool calls.
Install
dsh plugin --profile web add dsh-find-skilldsh plugin --profile web add dsh-find-skill (npm 0.2.1 registry-verified 2026-08-29). Source route (current develop branch): git clone https://github.com/Moximxxx/dsh-find-skill && cd dsh-find-skill && git checkout develop && pnpm install --config.minimumReleaseAge=0 && pnpm build && pnpm test, then dsh plugin --profile web add /abs/path/to/dsh-find-skill. English README: README_en.md.
Compatibility
dsh with web profile; uses official skills.sh API + npx -y skills@latest CLI; installs land in plugin-owned roots (temp/project/global) isolated from handwritten .dsh/skills and shared .agents/skills. Requires pnpm.
Details
- Repo: Moximxxx/dsh-find-skill
- Category: Agent Capabilities
- Stars: 2
- Version: npm 0.2.1 (registry-verified 2026-08-29)
- Last push: 2026-08-15
- First seen: 2026-08-13
Recent updates
LLM-driven skill search/install/remove; temp/project/global scopes; /skill command; official skills.sh API; isolated install roots; dispose-safe lifecycle.
FAQ
- How does the model decide to load a skill?
- The skill_find tool description is low-priority: the model should only use it when existing tools and loaded skills don't cover the task — then it searches and asks you to confirm scope.
- What scopes exist?
- temp (current session only, default), project (shared across the workspace), and global (all sessions). Scope defaults to temp unless configured otherwise.
- Does it touch my handwritten skills?
- No — installs land in plugin-owned roots (e.g. .dsh/skills-bridge per project), fully isolated from handwritten .dsh/skills and shared .agents/skills.
Alternatives
foryourhealth111-pixel/Vibe-Skills · linhay/harmony-next.skills · ben7am1n/dsh-claude-marketplace