Screenpipe Tauri
Add or change Tauri commands and TypeScript bindings in the screenpipe desktop app. Use when editing #[tauri::command] handlers, lib/utils/tauri.ts, or Rust types exported to the frontend.
Install
npx skills add screenpipe/screenpipe --skill screenpipe-taurigit clone --depth 1 https://github.com/screenpipe/screenpipe.git /tmp/screenpipe
mkdir -p ~/.claude/skills
cp -r /tmp/screenpipe/.claude/skills/screenpipe-tauri ~/.claude/skills/screenpipe-tauriPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Screenpipe Tauri (desktop app)
Path: `apps/screenpipe-app-tauri/`
Command registration is automated via the `tauri-helper` crate. **Do not** edit manual invoke-handler or specta command lists in `main.rs`.
## Adding a command
1. Add **both** markers to the handler function in any `src-tauri/src/**/*.rs` module:
```rust
#[tauri::command]
#[specta::specta] // required — without this the command is skipped in tauri.ts
pub async fn your_command(...) { ... }
```
2. From `apps/screenpipe-app-tauri/`:
```bash
bun run bindings:generate # write lib/utils/tauri.ts
bun run bindings:check # verify no drift
bun run typecheck # verify frontend types
```
3. Commit Rust + `lib/utils/tauri.ts` together
## Scripts
| Command | Purpose |
|---------|---------|
| `bun run bindings:check` | Fail if checked-in `lib/utils/tauri.ts` does not match Rust |
| `bun run bindings:generate` | Regenerate `lib/utils/tauri.ts` after command/type changes |
| `bun run typecheck` | Frontend TypeScript check |
## Key files
- `src-tauri/build.rs` — `tauri_helper::generate_command_file` (build-time scan)
- `src-tauri/src/main.rs` — `specta_collect_commands!()` / `tauri_collect_commands!()`
- `src-tauri/src/specta_bindings.rs` — export helpers and drift tests
- `lib/utils/tauri.ts` — generated TypeScript bindings (checked in)
Debug builds also auto-export bindings on startup when content changes.Details
- Skill name
screenpipe-tauri- Repository
- screenpipe/screenpipe
- Path
.claude/skills/screenpipe-tauri/SKILL.md- Repo updated
- 17 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Screenpipe Tauri skill do?
Add or change Tauri commands and TypeScript bindings in the screenpipe desktop app. Use when editing #[tauri::command] handlers, lib/utils/tauri.ts, or Rust types exported to the frontend.
How do I install the Screenpipe Tauri skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add screenpipe/screenpipe --skill screenpipe-tauri. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Screenpipe Tauri popular?
It lives in screenpipe/screenpipe, which has 22,429 GitHub stars and 2,305 forks, and is included in 1 curated skill list.
Related skills
Develop Screenpipe Windows
22kscreenpipe/screenpipe
Develop and test Screenpipe Windows-native changes on a disposable Azure VM created from the prepared Screenpipe Windows dev image. Use for Windows compiler, process, service, local API, desktop, capture, installer, or permission behavior. Do not use for React-only work proved by the browser mock.
Release
22kscreenpipe/screenpipe
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
Render HTML Report
22kscreenpipe/screenpipe
Produce a human-facing visual report — a chart, dashboard, scorecard, or styled summary — that renders as a live page in the screenpipe viewer instead of plain text. Use when the task asks for a visual/graphical output rather than a plain note; do NOT use for plain text or raw data (prefer a markdown note for those).
Plannotator
13kbacknotprop/plannotator
Reference for using Plannotator (its `plannotator` tool when you have one, otherwise the CLI): plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, exporting or sharing Guided Reviews, and the Plannotator Inbox (messages and questions the person answers later, without blocking you). Invoke when asked to use Plannotator for anything not covered by a more specific plannotator-* skill, and before you leave the person a decision, a question or finished work in the Plannotator Inbox (if another ag
Screenpipe Logs
22kscreenpipe/screenpipe
Retrieve and analyze Screenpipe CLI backend logs and desktop app logs for debugging
Plannotator Setup Goal
13kbacknotprop/plannotator
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.