Skip to content
TrustedSkillsbeta
Back to all skills

Configuring Tauri Csp

Checked
beshkenadze·vlatest·security

This skill automates Tauri CSP configuration, simplifying secure web app development and reducing potential security vulnerabilities.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add beshkenadze/claude-code-tauri-skills --skill configuring-tauri-csp -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

beshkenadze

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned beshkenadze/claude-code-tauri-skills at ef3ee24428.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
ef3ee24428
Manifest
tauri/tauri-csp/SKILL.md
Scanned
1 file, 363 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows you to configure Content Security Policy (CSP) for Tauri applications. CSP helps protect against cross-site scripting (XSS) attacks by defining a whitelist of sources that the browser is allowed to load resources from. The skill automates this process, ensuring your Tauri application adheres to secure coding practices and minimizes potential vulnerabilities.

When to use it

  • When building a new Tauri application and wanting to implement CSP from the start.
  • To harden an existing Tauri application against XSS attacks by adding or modifying CSP rules.
  • For developers who want to simplify the process of configuring CSP, avoiding manual configuration file edits.
  • During security audits to ensure proper CSP implementation in a Tauri project.

Key capabilities

  • Automated CSP configuration for Tauri applications.
  • Generation of tauri.conf.json files with appropriate CSP settings.
  • Support for various CSP directives (e.g., script-src, style-src, img-src).
  • Simplifies the process of defining allowed resource sources.

Example prompts

  • "Generate a tauri.conf.json file with CSP enabled, allowing scripts from localhost and the main domain."
  • "Configure my Tauri app to only allow images from the same origin."
  • "Add a non-executable script src directive to my tauri configuration."

Tips & gotchas

  • Requires familiarity with Content Security Policy concepts. Incorrect CSP configurations can break application functionality, so test thoroughly after implementation.