CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding

MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · skills/rust-tauri-apps/references/tauri-v2-rust-backend.md

MEDIUM — it fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.

Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted

excerptskills/rust-tauri-apps/references/tauri-v2-rust-backend.md· markdown

17- Keep field names stable and documented through TypeScript bindings or generated fixtures w

… (26 chars elided on L17)

18- Return structured errors instead of stringly catch-all failures when the frontend branches

… (15 chars elided on L18)

19- Do not leak internal paths, tokens, or raw subprocess output unless the UI explicitly need

… (7 chars elided on L19)

21## App State

Occurrences

1 occurrence · at L19

How to fix

Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.

Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-IMPERATIVE-01sha256838948ee08b3eb67…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/rust-tauri-apps/SKILL.md · 1 file

skills/rust-tauri-apps/SKILL.md2.6 KB · Markdown

name: rust-tauri-apps

description: Implicit Rust Tauri v2 skill. Use for Tauri apps, Rust commands, invoke contracts, app state, plugins, capabilities and permissions, secure IPC, filesystem and shell access, sidecars, updater, bundling, desktop and mobile distribution, and Rust frontend bridge design.

license: MIT

metadata:

category: rust

domains:

- tauri

- desktop-apps

- rust-backend

- secure-ipc

Rust Tauri Apps

Build Tauri v2 applications with small Rust command surfaces, secure capabilities, explicit IPC contracts, and maintainable distribution workflows.

Operating Model

Inspect the Tauri version and generated structure first: src-tauri, tauri.conf.json, capabilities, permissions, plugins, frontend invocation code, and CI/release scripts.
Treat every command as a public bridge contract. Validate input, return typed serializable results, and keep filesystem/shell/network capabilities narrow.
Prefer app-owned Rust services behind commands. Do not put large domain logic directly in #[tauri::command] functions.
Keep the capability model least-privilege by default. Avoid broad filesystem, shell, opener, and dialog permissions unless the user workflow truly needs them.
Coordinate with the general tauri-v2 skill when available for framework-specific current docs; use this skill for Rust architecture, security, testing, and command design.

Reference Map

references/tauri-v2-rust-backend.md for command/state/plugin architecture and typed IPC.
references/capabilities-security.md for permissions, filesystem/shell risk, secrets, updater, and secure defaults.
references/distribution-mobile.md for bundling, updater, sidecars, signing, desktop/mobile packaging, and release checks.

Defaults

Keep commands async only when they await I/O. Do CPU-heavy work off the main runtime.
Use serde DTOs at the IPC boundary and convert to domain types inside services.
Use tauri::State for shared app services with clear ownership; avoid global mutable statics.
Use plugin APIs instead of hand-rolled platform code when mature official plugins cover the use case.
Keep frontend-originated paths, URLs, and shell arguments untrusted until validated.

Verification

Use repo-native checks first, then add Tauri-specific validation:

cargo fmt --all --check
cargo test --manifest-path src-tauri/Cargo.toml --all-targets
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets --all-features -- -D warnings

For command changes, add Rust tests around service behavior and frontend tests or contract fixtures for IPC shapes when the app already has a frontend test lane.

rust-tauri-apps— agent skill

Is rust-tauri-apps safe to install?

Rust Tauri Apps

Operating Model

Reference Map

Defaults

Verification

Audit the pieces. Scan the whole. Decide.