Velt Setup Best Practices
ListedHelps with setup and configuration, best practices as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add velt-js/agent-skills --skill velt-setup-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
velt-js
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.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.velt.dev.
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.
Hosts contacted
api.velt.devundeclaredWhat it found (3 of 12)
- skills/velt-setup-best-practices/AGENTS.full.md:729contacts api.velt.dev
const response = await fetch("https://api.velt.dev/v2/auth/token/get", { - skills/velt-setup-best-practices/AGENTS.full.md:774contacts api.velt.dev
const response = await fetch("https://api.velt.dev/v2/auth/token/get", { - skills/velt-setup-best-practices/AGENTS.full.md:842contacts api.velt.dev
const response = await fetch("https://api.velt.dev/v2/auth/token/get", {
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 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 velt-js/agent-skills at dcc5e5d192.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- dcc5e5d192
- Scanned
- 34 files, 6,817 lines
About this skill
What it does
This skill provides guidance and best practices for setting up Velt, a framework for building AI agents. It helps users configure their development environment correctly, ensuring smooth operation and efficient agent creation. The skill aims to streamline the initial setup process and avoid common pitfalls when working with Velt projects.
When to use it
- You're starting a new Velt project and need help configuring your environment.
- You’re encountering errors or unexpected behavior during Velt development.
- You want to ensure your Velt setup adheres to recommended practices for stability and performance.
- You are upgrading an existing Velt project and want to review your configuration.
Key capabilities
- Provides guidance on environment setup.
- Offers best practice recommendations for Velt projects.
- Helps troubleshoot common Velt configuration issues.
Example prompts
- "What's the recommended way to set up a new Velt project?"
- "I’m getting an error when running my Velt agent, can you help me troubleshoot it?"
- "What are some best practices for configuring my Velt development environment?"
Tips & gotchas
This skill assumes basic familiarity with command-line interfaces and software development concepts. While the skill aims to simplify setup, a foundational understanding of project dependencies is helpful.