dsh-skills-anywhere

dsh-skills-anywhere

Discover and load skills across your tools. Collect Agent Skills from local directories and configured Git sources into one catalog, available through a live DeepSeek Harness (dsh) provider or a local stdio MCP server.

English | 中文

Start with your workflow

Quick start

Requires Node.js 22.19+ or 24+. The CLI and local MCP server work independently; Git sources also require Git.

Inspect discovered skills:

npx dsh-skills-anywhere list

For an MCP client, use the local server configuration. For DeepSeek Harness, install into your chosen profile:

dsh plugin --profile web add dsh-skills-anywhere

Start dsh and load with its skill tool or /skill-name. To add a Git source, run npx dsh-skills-anywhere add anthropics/skills. Installation details cover release archives, source checkouts and dsh version requirements.

Try it in your browser

Try the interactive Hugging Face playground — explore an example workspace, resolve name clashes, and search beyond the catalog budget. No installation or model API needed. How it works.

Inspect skill instructions, compare directory manifests and share catalog views. Keyboard navigation preserves the selected row and catalog settings. Files opened for local review stay in the browser.

Bring your own SKILL.md. Compare the provider's strict and lenient parsing locally: inspect repairs, invocation settings and a downloadable check report. Your file stays in the browser. The same checks are available in the command line and CI, with file hashes and actionable exit codes. Reports enumerate recognized source URLs, full-commit address forms and author-declared tools. Referenced content, script behavior and client compatibility require separate verification.

How the catalog works

Clients can use different project, user and plugin directories for SKILL.md files. Skills Anywhere discovers configured sources in place and makes the resulting catalog available through dsh or an MCP client configured to connect to its local server. Directory definitions describe discovery paths; the compatibility matrix records tested protocol connections separately.

Inside dsh, it registers one extra provider on the built-in ctx.skills registry, so the model's normal skill tool and /name invocation simply see more skills:

• Predefined agent directories. Project and user paths for Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Kiro, Goose and other entries in the directory registry.
• Claude Code plugin marketplaces. The skills nested inside ~/.claude/plugins/marketplaces/*/plugins/*/skills/*, including the official Anthropic marketplace.
• Configured Git sources. Select a skill repository, subdirectory, branch, tag or commit. The provider maintains a local checkout and records its resolved commit in a lock file.
• Local files read in place. Existing skills are re-read when loaded, without copying them into each client's directory. Git sources use the managed cache described below.

The catalog budget controls how many skill summaries enter the model's session catalog: up to 50 by default. Other eligible skills remain searchable through find_skills and can be loaded on demand. /name invocation is unchanged.

The same pool is available outside dsh through dsh-skills-anywhere mcp. Configured MCP clients can discover and open skills through tools and skill:// resources. Client support for tool calls, resources and the skill's own instructions determines the available workflow.

The provider deduplicates symlinked and byte-identical entries, supports documented frontmatter repairs, and renames conflicting names such as discord/configure and telegram/configure. The CLI reports the published catalog, skipped entries and the reason for each change.

Inspect skill delivery

Successful MCP open_skill calls return a receipt identifying the delivered instruction body, original SKILL.md and optional bundle. Attach it to a tool span to review delivered versions alongside task results. The receipt records delivery; instruction following and permission enforcement are separate checks. Receipt contract · EvalArc Trace Workbench.

Example: review robot evidence

Load a Microduck frame-review skill through MCP, then have your agent verify its recorded joint facts with Robot Reel before writing a review. Interactive skill example (select 04 Review robot evidence) · Local walkthrough · Reusable skill. The browser shows the instructions; your agent's own execution tool runs the read-only verifier. No new simulation or GPU is needed.

Review once, load the same file

MCP open_skill returns the original file's SHA-256. Supply expected_sha256 from check --json or an earlier open to reject a changed SKILL.md before its instructions are returned. Fresh author opt-outs apply immediately, even while discovery is cached. Exact-file workflow.

MCP protocol support: the local stdio command negotiates legacy initialization and the 2026-07-28 protocol opening. Four SDK configurations and the installed npm archive are checked over real subprocess connections. Compatibility matrix and embedding migration.

Review the whole skill directory. Generate a file manifest with bundle /path/to/skill --json, compare added/removed/changed resources, and require expected_bundle_sha256 when opening through MCP. The interactive bundle comparison shows a script change behind unchanged instructions and compares your own manifests locally. Directory review and limits. The digest covers recorded paths and file contents within that directory. External dependencies and execution permissions need separate review; files can change after loading.

Installation details and discovery example

Published on npm with build provenance; each GitHub release also includes the same tarball.

Example discovery output is shown below. Paths and counts depend on the local installation and configured sources:

$ npx dsh-skills-anywhere list
NAME                 FROM                                                    PATH
discord-access       claude plugin discord @ claude-plugins-official         ~/.claude/plugins/marketplaces/.../discord/skills/access/SKILL.md
frontend-design      claude plugin frontend-design @ claude-plugins-official ~/.claude/plugins/marketplaces/.../frontend-design/skills/frontend-design/SKILL.md
skill-creator        claude plugin skill-creator @ claude-plugins-official   ~/.claude/plugins/marketplaces/.../skill-creator/skills/skill-creator/SKILL.md
...
31 skills, 6 renamed — run `dsh-skills-anywhere doctor` for details

dsh plugin --profile web add github:noteflowai/dsh-skills-anywhere

# $DSH_HOME/profiles/web/pnpm-workspace.yaml
allowBuilds:
  'dsh-skills-anywhere@https://codeload.github.com/noteflowai/dsh-skills-anywhere/tar.gz/<sha>': true

What gets discovered

Lower rank wins a duplicate name inside the dsh registry. The built-in dsh roots keep their ranks (.dsh/skills 100, .agents/skills 200, ~/.dsh/skills 400, ~/.agents/skills 500). Precedence follows these values across sources; for example, an agent's project entry at rank 250 precedes a dsh user entry at 400. The built-in .agents/skills and .dsh/skills roots are not scanned again.

Run npx dsh-skills-anywhere agents for the full agent table and which directories exist on your machine.

Skill format

The provider reads directories containing SKILL.md and dsh's flat <name>.md form, using the Agent Skills format. It parses name, description, disable-model-invocation and user-invocable, and retains license, compatibility, allowed-tools and metadata.

compatibility and allowed-tools carry the author's declarations; the client controls runtime requirements and tool permissions. Unknown fields, including argument-hint and context, are preserved under metadata.frontmatter. Preserving them does not implement the originating client's behavior. scripts/, references/ and assets/ are exposed through the skill's resource directory for the consuming client to use.

In the default lenient mode a missing name falls back to the directory, an invalid name is normalised to kebab-case, and a missing description is derived from the first paragraph. Each repair is recorded and shown by doctor. Set lenient: false to match the strict behaviour of the built-in provider.

Git sources

npx dsh-skills-anywhere add anthropics/skills                      # default branch
npx dsh-skills-anywhere add anthropics/skills@v1.0.0               # tag or branch
npx dsh-skills-anywhere add vercel-labs/agent-skills/skills        # sub-directory
npx dsh-skills-anywhere add https://github.com/o/r/tree/main/dir   # GitHub tree URL
npx dsh-skills-anywhere add git@gitlab.com:group/skills.git        # any git URL
npx dsh-skills-anywhere add ./local/skills-repo --project          # local repo, project-scoped
npx dsh-skills-anywhere add o/r --ref 3f2a9c1 --rank 300           # pin a commit, set precedence

Sources come from three places, merged in this order: the plugin config.sources, the user file ~/.dsh/skills-anywhere/sources.json, and the project file <project>/.dsh/skills-anywhere.json (commit it to share skills with your team). The CLI edits the last two.

Each repository uses a local checkout at ~/.dsh/skills-anywhere/cache/<host>/<owner>/<repo> (<repo>@<ref> when a branch, tag or commit is set). Background synchronization runs at startup, every syncIntervalMs (6 hours by default), and when source configuration changes. Resolved commits are recorded in ~/.dsh/skills-anywhere/lock.json. Discovery reads the available cache. A failed refresh retains an existing checkout; a source that has never synchronized contributes no cached skills. Successful changes invalidate the catalog without making discovery wait for network synchronization.

Catalog budget and the find_skills / open_skill tools

dsh publishes every model-invocable skill's name and description into the session, on every request. With marketplaces and a few git sources that is hundreds of lines of context. The provider therefore ranks its skills and marks only the first catalog.limit (default 50) as model-invocable; the remainder is published with model invocation off, which keeps it out of the catalog but still loadable by you with /name.

Two tools, registered by the dsh-skills-anywhere/tools row, make the hidden part reachable for the model:

• find_skills(query, limit?) searches every skill by keyword (name, description, whenToUse, origin), catalog or not, and says which matches are listed.
• open_skill(name) loads any skill by exact name, including ones the budget hid. Skills whose own frontmatter says disable-model-invocation: true are still refused, exactly as the built-in skill tool does.

- id: skills-anywhere
  config:
    catalog:
      limit: 30                       # 0 = unlimited (old behaviour)
      pin: [frontend-design]          # always listed
      hide: [example-skill]           # never listed, still searchable and /name-invocable
- id: skills-anywhere-tools
  config:
    findLimit: 10

Author-disabled skills never count against the budget. Which skills stay listed follows the precedence order below, so project-level skills win over user-level, which win over marketplaces and git sources. The tools row needs the tool runtime (ctx.tools); in a profile without one it stays pending and the provider works alone.

CLI

Check before committing. Run npx -y dsh-skills-anywhere@0.12.0 check skills/example/SKILL.md --fail-on-repair. The same parser used in the playground provides batch file checks, JSON reports with file hashes, and CI exit codes. Checks read only the named files. Commands, CI example and scope.

dsh-skills-anywhere list [--all] [--json]     Skills the provider publishes (--all shows hidden duplicates)
dsh-skills-anywhere agents [--json]           Agent directory definitions and paths found here
dsh-skills-anywhere sources [--json]          Configured git sources and their synced commits
dsh-skills-anywhere add <source> [--ref] [--path] [--rank] [--project]
dsh-skills-anywhere remove <source> [--project]
dsh-skills-anywhere sync [--force] [--json]   Clone or refresh every source now
dsh-skills-anywhere doctor [--json]           Repaired, skipped, renamed and duplicate skills, with reasons
dsh-skills-anywhere check <files...> [--json] Explicit local files; strict parser gate by default
dsh-skills-anywhere mcp                       Serve skills to configured clients over stdio MCP

All commands accept --cwd <dir>. For check, it resolves the named files; other commands use it to pick the project. check --lenient accepts provider repairs; --fail-on-repair rejects any reported repair in the selected mode. The CLI uses the same parsing code as the plugin and never needs dsh running.

Use as an MCP server

dsh-skills-anywhere mcp starts a local Model Context Protocol server over stdio. It exposes the same configured sources, deduplication and naming rules through the following tools. Connect a compatible client using its MCP configuration:

Skills are also exposed as skill://<name> resources with completion for clients that support resource references. The MCP tools and resources exclude skills whose frontmatter sets disable-model-invocation: true. The server runs independently of dsh.

The examples below show client configuration. Automated connection checks cover the four SDK configurations and installed package in the compatibility matrix; application-specific behavior depends on the client version and its support for tools and resources.

Claude Code (as a plugin; this repo doubles as a plugin marketplace)

claude plugin marketplace add noteflowai/dsh-skills-anywhere
claude plugin install dsh-skills-anywhere@noteflowai

Or register the bare server instead: claude mcp add skills-anywhere -- npx -y dsh-skills-anywhere mcp. Either way, restart Claude Code once so it connects.

Cursor (.cursor/mcp.json or ~/.cursor/mcp.json)

{ "mcpServers": { "skills-anywhere": { "command": "npx", "args": ["-y", "dsh-skills-anywhere", "mcp"] } } }

Codex (~/.codex/config.toml)

[mcp_servers.skills-anywhere]
command = "npx"
args = ["-y", "dsh-skills-anywhere", "mcp"]

The MCP registry identifier is io.github.noteflowai/dsh-skills-anywhere. The repository also includes Agent Plugin manifests (plugin.json and mcp.json) for clients that support that format. Follow your client's installation flow.

Add --cwd <dir> when the client starts the server outside your project. Configured Git sources sync in the background at startup. To embed the server, import { createSkillsAnywhereServer } from 'dsh-skills-anywhere/mcp' returns the McpServer and provider; see the transport and migration guide.

Browse and toggle skills in the dsh web UI

In dsh web, open Settings → Plugins → Plugin configuration. The Skills Anywhere card lists every skill the provider found, grouped by where it lives (agent directories, Claude Code plugins, git sources), with its catalog state — listed for the model, not listed (kept out by the budget or by you) or author disabled — and the name it was renamed to when it collided. Each row offers Pin (always listed), Hide (out of the model catalog, still /name- and find_skills-reachable) and Exclude (dropped from the provider); the catalog budget is editable in place, and a filter box searches names, descriptions and origins.

Edits are written to the profile's dsh settings document as the skills-anywhere namespace, layered over catalog and excludeSkills from cordis.patch.yml, and the model catalog follows immediately: no restart, no file editing. The card only appears in profiles that mount dsh's settings service and web server (the shipped web profile does); everywhere else the provider behaves exactly as composed.

Configuration

Override the row in your profile's cordis.patch.yml. A patch replaces the whole config block, so restate every key you care about:

- id: skills-anywhere
  config:
    agents: true
    excludeAgents: [openclaw]
    claudePlugins: true
    sources:
      - anthropics/skills
      - { repo: vercel-labs/agent-skills, path: skills, ref: main, rank: 650 }
    excludeSkills: [example-skill]

The dsh-skills-anywhere/tools row accepts findLimit (default 10), findMaxLimit (50), and find / open booleans to register only one tool.

How precedence and duplicates work

1. Roots are scanned in rank order. Within one rank, the agent table order, then path.
2. Entries pointing at the same file (symlinks) collapse to the first. Entries with the same name and byte-identical body collapse to the first. Both appear in doctor as hidden duplicates.
3. Entries that still share a name but differ are all kept. If one of them is yours (an agent directory) it keeps the bare name and the others are prefixed with their plugin, repository, or agent (telegram-configure). If every member comes from a marketplace or a git source, all of them are prefixed, so you get discord-access and telegram-access rather than a meaningless bare access. doctor lists the renames.
4. The dsh registry then merges this provider's candidates with the built-in ones by rank.

Integration examples and measured outcomes

Use the examples to connect delivery receipts with separately computed task checks. The reports retain instructions, tool results and every delivered program.

Review independent-source SWE tasks: a separate fixed cohort records 36 attempts on Astropy, pytest and SymPy across four workflow conditions. Direct and MCP preloads deliver identical guidance; an unrelated MCP control matches the prompt length. No attempt obtains native acceptance: 31 have assessable reports and five remain uncertain after upstream infrastructure flags. Eight attempts produce nonempty patches. Methods and offline records keep tool failures, native labels and incomplete usage visible.

Carry the reviewed skill into a new session: a separate six-attempt cohort reuses the predecessor's exact skill bytes through workflow MCP preloads. All six preloads succeed; the memory group retrieves six results. All six programs remain unchanged and no task passes full acceptance. The report connects original pins, delivery receipts, retrieved history and task checks.

Review runtime behavior with the isolated skill-composition fixtures. The report separates file acceptance, service completion and authorization across 32 authored controls and 12 model attempts. No model attempt completes the service task.

These small studies on public tasks evaluate specific workflows; general skill or memory benefits require separate evaluation. The research guide keeps methods, composition controls and separate cohorts together for reproduction.

Security notes

• The plugin reads skill files. It never writes to your agent directories.
• Git sources run git on your machine at plugin start and on the refresh interval. Pin a commit for anything you do not fully trust, and review lock.json.
• Loaded skills add instructions to the agent's context. Review instructions and referenced scripts before use; the client controls execution permissions, and loading does not ensure the model follows them.
• Skills are read with Node's filesystem API, not through dsh's sandboxed ctx.fs; the built-in provider does the same for its bundled root.

Development

pnpm install
pnpm run check        # typecheck + lint + tests + build
pnpm pack             # tarball for `dsh plugin --profile <name> add ./dsh-skills-anywhere-*.tgz`

Tests run against the real @deepseek-ai/dsh-skill registry and real git repositories in temp directories.

Contributing

Issues and pull requests are welcome. Add a discovery path in src/agents.ts, cite its source and test directory discovery. Client integration needs separate protocol and workflow checks. See CONTRIBUTING.md.

Community listings: Awesome DeepSeek Harness · Awesome Gemini CLI. Publication history and verification.

License

MIT © Note Flow AI