Unofficial Windows WebView2 diagnostics and automation for Tauri 2.12 development builds.
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y tauri-agent-kit
MCP client config
{
"mcpServers": {
"tauri-agent-kit": {
"command": "npx",
"args": [
"-y",
"tauri-agent-kit"
]
}
}
}Practical workflows for your coding agent: review a change, explore a design, investigate a question, or implement a scoped feature.
A skill is a folder of instructions, references, and optional helpers that your agent loads for a particular task. Start with one skill on a small project; you do not need to install the whole collection or replace your global instructions.
These are independent, community-maintained skills, not official vendor products.
Try a skill · Choose by task · Requirements · All skills · Contribute
You need a coding agent that supports skills, plus Node.js and npm for the installer.
Open a terminal in the project where you want to use the skill.
Install a focused review workflow:
npx skills add Firzus/agent-skills --skill code-review
Follow the installer's prompts to choose your agent and destination.
Installation defaults to project scope; use -g only if you want global installation.
Select code-review through your agent's skill picker or supported invocation syntax. If it is not discovered, check the installation location and restart the session.
Ask it to review a small, clearly identified change. Provide the intended behavior, the files or diff to review, and a read-only scope.
The result should be findings and verification limits, not automatic edits or a published pull request. This workflow uses independent reviewers, so check that your agent supports subagents before trying it.
# Browse the collection without installing it
npx skills add Firzus/agent-skills --list
# Choose skills interactively
npx skills add Firzus/agent-skills
# Manage installed skills
npx skills list
npx skills update code-review
npx skills remove code-review
See the skills CLI documentation for supported agents, installation modes, and troubleshooting.
| I want to… | Start with |
|---|---|
| Review an existing change without modifying it | code-review |
| Diagnose a bug or verify an authorized fix | debug |
| Compare interface ideas or test feasibility | prototype |
| Investigate a question across multiple sources | deep-research |
| Turn a new request into approved Linear work | triage |
| Execute a prepared Linear issue | implement |
| Audit security boundaries in a codebase | security-review |
Research, prototyping, preparation, and implementation are different entry points, not mandatory consecutive phases. Some workflows call other skills; install the ones referenced by the workflow you choose.
Installing instructions does not install every tool they describe or authorize every action they can perform. Check the selected skill's prerequisites first.
| Workflow | Additional requirements |
|---|---|
| Independent reviews and delegated research | An agent with subagent support |
| Figma or Linear workflows | The relevant integration, account access, and approval for external writes |
| Video reports | FFmpeg and access to the application being recorded |
| YouTube transcription | Available captions, or the audio/transcription tools required by the selected route |
| Image generation | An authenticated Codex CLI setup with the image-generation capability described by the skill |
Host support for installing skills does not guarantee identical behavior or tool availability. Explicit-invocation workflows such as triage, interview, implement, improve-architecture, and setup-harness should be selected deliberately.
setup-harness asks which harnesses and languages to configure, previews the complete changes, and waits for approval. It adds personal instructions without replacing the built-in system prompt and creates no backups. Existing unrelated instructions are preserved.
| Harness | Personal instruction destination |
|---|---|
| Codex (app and CLI) | One shared AGENTS.md per CODEX_HOME (default ~/.codex) |
| Cursor | User Rules in Customize > Rules; manual handoff if UI editing is unavailable |
| Claude Code | ~/.claude/CLAUDE.md |
Cursor's project AGENTS.md is not a global substitute. See the
native destinations
for loading limits, and review the
shared policy template
before choosing this skill.
The tauri skill remains the agent-facing entry point. Its optional Windows diagnostic application, tauri-agent-kit, is maintained in this repository but is not an installable skill. Installing the skill does not install the MCP server or Rust plugin: the skill proposes the integration when a compatible project lacks it, and installs it only after approval. Check the kit's compatibility and publication status before integrating it into an application.
| Skill | Purpose |
|---|---|
| code-review | Independent read-only review of a scoped change. |
| debug | Evidence-led diagnosis and verification of authorized bug fixes. |
| deep-research | Multi-source investigation with a reusable evidence dossier. |
| gamification | Engagement mechanics, motivation, and ethical design checks. |
| imagegen | Generate or edit raster images through Codex. |
| implement | Execute a published Linear issue by work type, with tests and documentation. |
| improve-architecture | Find architectural friction and publish approved refactors as Linear sub-issues. |
| interview | Resolve decisions through question rounds until the agreed scope and consequential edge cases are covered. |
| monorepo | Workspace structure, package boundaries, task graphs, caching, affected CI, and release verification. |
| prototype | Answer a design or feasibility question through an experiment. |
| setup-harness | Set up reviewed personal instructions for selected harnesses without backups or system-prompt replacement. |
| security-review | Investigate codebase security boundaries and report evidence-backed findings. |
| skills | Discover, install, maintain, and author agent skills. |
| triage | Turn a request into approved Linear issues or projects, clarified through interview, and continue a project goal by goal. |
| unslop | Propose evidenced dead-code and slop removals in the conversation, then apply the accepted ones. |
| video-report | Record video evidence of real application behavior. |
| writing-for-agents | Write useful skills and project instructions. |
| youtube-transcript | Turn video speech and visual evidence into a learning report. |
| Skill | Purpose |
|---|---|
| adsense | Publisher monetization, ad placement, policy, and performance. |
| astryx | Build interfaces with the Astryx design system. |
| dokploy-best-practices | Deploy and operate applications with Dokploy. |
| extract-theme | Extract a website's design tokens for Tailwind and shadcn/ui. |
| nextjs | Build and migrate Next.js applications. |
| payload-cms | Model content, access rules, and hooks with Payload CMS. |
| shaders | Add GPU-driven visual effects to React interfaces. |
| swr | Manage React data fetching, caching, and mutations. |
| tanstack-query | Manage asynchronous server state with TanStack Query. |
| tanstack-router | Build type-safe routes with TanStack Router. |
| tanstack-start | Build full-stack applications with TanStack Start. |
| tanstack-store | Manage reactive client state with TanStack Store. |
| tauri | Build and validate Tauri desktop and mobile applications. |
| vite-plus | Configure Vite+ tooling, checks, and workspace tasks. |
| web-assets-optimization | Optimize images, video, fonts, SVG, and asset delivery. |
| web-extension | Build and package browser extensions. |
| zod | Validate data and evolve schemas with Zod. |
| Skill | Purpose |
|---|---|
| figma-to-unity | Implement Figma designs in Unity UI Toolkit. |
| unity | Choose the appropriate tools for Unity development tasks. |
Found a problem? Open an issue with the skill name, agent and version, expected result, and actual result. Remove secrets and private project data from examples.
For repository changes, read AGENTS.md for contribution boundaries
and validation. A skill lives at skills/<section>/<name>/SKILL.md; supporting
references and helpers stay in its folder. Keep the README catalog and
marketplace manifest aligned with skill folders.
The documentary knowledge base contains source material, not installable skills. It is separate from the skill catalog.
Licensed under MIT.