Skip to content
TrustedSkillsbeta
Back to all skills

Svelte Deployment

Checked
spences10·vlatest·frontend

Helps with Svelte, deployment as part of building frontend UIs and user experiences workflows.

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 spences10/skills --skill svelte-deployment -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

spences10

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 spences10/skills at f1aaa3f350.

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

Commit
f1aaa3f350
Manifest
svelte-deployment/SKILL.md
Scanned
4 files, 333 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 automates the deployment of Svelte applications. It handles building the application for production, configuring environment variables, and pushing the built files to a designated hosting location. This simplifies the process of getting your Svelte projects live and accessible online.

When to use it

  • You've developed a Svelte application and need to deploy it to a server or platform.
  • You want to automate the build and deployment process, reducing manual steps and potential errors.
  • You are working on a team and need a consistent way to deploy Svelte projects.
  • You require environment variable configuration during the deployment process.

Key capabilities

  • Production builds of Svelte applications
  • Environment variable configuration
  • Deployment to hosting locations

Example prompts

  • "Deploy my Svelte app located at /path/to/my/svelte-app."
  • "Build and deploy my Svelte project, setting API_KEY to 'your_api_key'."
  • “Run a production build of the Svelte application in this directory.”

Tips & gotchas

The skill requires access to the relevant deployment environment. Ensure proper permissions are configured for automated deployments.