What
These Tauri skills are excellent, but right now the repo is a bare tauri/ folder of SKILL.md files. That means the only way to use them is to hand-copy folders into ~/.claude/skills, where they load unconditionally in every session and can't be scoped to a project or profile.
Two small additions would make this repo a first-class, installable Claude Code plugin:
1. Add a plugin manifest — .claude-plugin/plugin.json
{
"name": "tauri-skills",
"version": "1.0.0",
"description": "Topic-scoped Tauri desktop/mobile development skills.",
"author": { "name": "dchuk", "url": "https://github.com/dchuk" }
}Claude Code plugins auto-discover a skills/ directory, so moving the current
tauri/* skill folders under skills/ (or pointing the plugin at them) exposes
all of them as gateable skills.
2. Add a marketplace manifest — .claude-plugin/marketplace.json
{
"name": "dchuk-tauri",
"owner": { "name": "dchuk" },
"plugins": [
{ "name": "tauri-skills", "source": "./" }
]
}This lets people install directly:
/plugin marketplace add dchuk/claude-code-tauri-skills
/plugin install tauri-skills@dchuk-tauri
...and reference it from profile/stack tooling as tauri-skills@dchuk-tauri,
instead of copying files around.
3. Add a LICENSE
There's currently no LICENSE file, which under default copyright means the
content can't be redistributed or repackaged. A permissive license (MIT is
common for skill/plugin repos) would let people install, fork, and bundle these
skills. Without it, even a well-intentioned mirror/marketplace isn't allowed.
Why
- Scoping: as a plugin, the skills can be enabled per-project/profile instead of loading globally.
- Distribution: one-command install; no manual folder copying.
- Reuse: stack/profile tools can list
tauri-skills@… as a normal dependency.
Happy to open a PR for (1) and (2) if you're open to it — just let me know your
preferred plugin/marketplace names and license. Thanks for putting these together!
What
These Tauri skills are excellent, but right now the repo is a bare
tauri/folder ofSKILL.mdfiles. That means the only way to use them is to hand-copy folders into~/.claude/skills, where they load unconditionally in every session and can't be scoped to a project or profile.Two small additions would make this repo a first-class, installable Claude Code plugin:
1. Add a plugin manifest —
.claude-plugin/plugin.json{ "name": "tauri-skills", "version": "1.0.0", "description": "Topic-scoped Tauri desktop/mobile development skills.", "author": { "name": "dchuk", "url": "https://github.com/dchuk" } }Claude Code plugins auto-discover a
skills/directory, so moving the currenttauri/*skill folders underskills/(or pointing the plugin at them) exposesall of them as gateable skills.
2. Add a marketplace manifest —
.claude-plugin/marketplace.json{ "name": "dchuk-tauri", "owner": { "name": "dchuk" }, "plugins": [ { "name": "tauri-skills", "source": "./" } ] }This lets people install directly:
...and reference it from profile/stack tooling as
tauri-skills@dchuk-tauri,instead of copying files around.
3. Add a LICENSE
There's currently no LICENSE file, which under default copyright means the
content can't be redistributed or repackaged. A permissive license (MIT is
common for skill/plugin repos) would let people install, fork, and bundle these
skills. Without it, even a well-intentioned mirror/marketplace isn't allowed.
Why
tauri-skills@…as a normal dependency.Happy to open a PR for (1) and (2) if you're open to it — just let me know your
preferred plugin/marketplace names and license. Thanks for putting these together!